similar to: Samba issues with Win 10

Wells, Roger K. wrote: > On 06/28/2018 10:35 AM, mark wrote: >> >> Just ran into a problem: someone with a new laptop, running Win 10, >> version 1709, tried to map their home directory (served from a CentOS 6.9 >> box, and it fails, with Windows complaining that it no longer supports >> SMBv1, and if you go to their site, you can install support >> for that

Walter H. wrote: > On 28.06.2018 16:30, mark wrote: > >> Just ran into a problem: someone with a new laptop, running Win 10, >> version 1709, tried to map their home directory (served from a CentOS 6.9 >> box, and it fails, with Windows complaining that it no longer supports >> SMBv1, and if you go to their site, you can install support >> for that manually....

On 06/28/2018 10:35 AM, mark wrote: > Hi, folks, > > Just ran into a problem: someone with a new laptop, running Win 10, > version 1709, tried to map their home directory (served from a CentOS > 6.9 box, and it fails, with Windows complaining that it no longer > supports SMBv1, and if you go to their site, you can install support > for that manually.... > > The

Louis, Did not mean to confuse. Before I upgraded to Mint 19.1 I could go to the network, click on windows network, click on workgroup, then office and the windows pc (office) would mount. No problems. THe folders on the windows machine would be accessed. Now in Mint 19.1 I get the error "Unable to mount location....". We traced this behavior to the UFW firewall blocking the

Hi , I just need some clarification ; We currently use ntlm_auth + winbind for AD auth on Freeradius, will disabling SMBv1 break authentication for ntlm_auth + Freeradius ? Many Thanks Arnab

Le 13/10/2017 à 01:46, Jeremy Allison via samba a écrit : > On Thu, Oct 12, 2017 at 03:58:58PM +0200, Hadrien Grasland via samba wrote: >> Hi, >> >> We're slowly deprecating SMBv1 support at work, so I'm trying to >> mount our Samba network shares using SMBv2.0. This should in >> principle be supported by the server, and seems works well enough >> for

On Thu, Jun 28, 2018 at 12:50:06PM -0400, mark wrote: > Wells, Roger K. wrote: > > On 06/28/2018 10:35 AM, mark wrote: > >> > >> Just ran into a problem: someone with a new laptop, running Win 10, > >> version 1709, tried to map their home directory (served from a CentOS 6.9 > >> box, and it fails, with Windows complaining that it no longer supports

hai,   Please keep it mailing to the list, this way is shows up of others also. A workaround for disabling SMBv1, you can make your server less secure but thats not what i would do. Setting these to enable NTLM v1 again. lanman auth = yes ntlm auth = yes raw NTLMv2 auth = yes I think also this is more a question for the free raduis list, but i would to for a ldap(s) setup. just dont mixup

Hi, We're slowly deprecating SMBv1 support at work, so I'm trying to mount our Samba network shares using SMBv2.0. This should in principle be supported by the server, and seems works well enough for the Windows clients. But it fails for me with some errors which I do not understand. Can you help me figure out what's going on? Here's my system configuration and a quick

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Hadrien Grasland via samba > Verzonden: vrijdag 13 oktober 2017 15:34 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Share mounts in SMBv1 mode, but fails > weirdly in SMBv2 mode > > Hi Louis, > > Thanks for your reply! > > > This might be a

Dear Rowland, Thanks a lot for your anwswer ! Le 2017-10-17 20:16, Rowland Penny via samba a écrit : > On Tue, 17 Oct 2017 19:31:17 +0200 > "Denis BUCHER via samba" <samba at lists.samba.org> wrote: >> Le 07.09.2015 à 15:52, soonerdave a écrit : >> > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet >> > support except in the

On 11/2/18 5:43 AM, L.P.H. van Belle via samba wrote: > Its a headless server so in this case im unable to test from within kodi, atm. > But Michael count try to to adjust the maxprotocol from within kodi and see if that helps. Kodi is a GUI app. There is no "shell" or "exit to shell" feature. It calls library functions and does not call the "smbclient"

I update centos's samba to 4.8.3-6. My windows 10 is professional, whose version is 1803. I still can't access samba. Do I need update my windows 10 to 1903? andrew At 2019-09-12 17:45:10, "anax" <anax at ayni.com> wrote: > > >On 12/09/2019 11.09, qw wrote: >> Hi, >> >> >> I can access centos's samba via windows 7, but fail

Hello, Thanks for your responses. I have attached a file containing the responses to ufw.log, syslog, ufw status numbered and ufw status verbose (Best use Word/Wordpad to open it). The OS is Linux Mint 19.1. Samba version 4.7.6 - Ubuntu. Samba runs on boot up. I connect using the file explorer Go -> Network menu selections. Hope this information will be of help. Regards, Marty

me at tdiehl.org wrote: > On Thu, 28 Jun 2018, mark wrote: >> Walter H. wrote: >>> On 28.06.2018 16:30, mark wrote: >>> >>>> Just ran into a problem: someone with a new laptop, running Win 10, >>>> version 1709, tried to map their home directory (served from a >>>> CentOS 6.9 >>>> box, and it fails, with Windows

On 9/27/19 12:48 PM, Rowland penny via samba wrote: > On 27/09/2019 18:33, Christopher Cox via samba wrote: >> >> I understand the "Function Discovery" side and wsdd (which is fine for >> local same network discovery somewhat similar to Network >> Neighborhood). I'm saying that even without that if I browse to just a >> computer in Windows

Dear Samba-Team, we set up a Samba AD with a dedicated fileserver in a heterogeneous Windows/Linux environment and face a problem right now: we have a few additional servers used by everyone for doing "heavy" computations. There, we'd like to mount a folder for sharing between a special group of users; so it should be mounted permanently. My questions are: - How can we achieve

Hi, we have updated our samba AD domain from 4.4.x to 4.5.x. The release notes for 4.5.0 included  "NTLMv1 authentication disabled by default". So we had to enable it to get our radius (freeradius) server working (for 802.1x). What would be the best way to change the freeradius configuration in such a way, that we can disable NTLMv1 again. The radius server is used for WLAN

El 3 de junio de 2020 10:28:19 GMT-04:00, Rowland penny via samba <samba at lists.samba.org> escribi?: >On 03/06/2020 15:08, Rommel Rodriguez Toirac via samba wrote: >> The operating systems used as clients in our network range mainly >from Windows XP to Windows 10. >> >> With Windows XP operating systems is happening that when it comes >time for a user to change

Hallo, We are using centos 7 and samba in combination with Win10 1903. The problem: Some systems are able to map a share and some can t. Any ideas and hints? Thanks Ralf