Hi, We have been using for years the option "netbios aliases" with 9 aliases (+ 1 main host). Each one has it's own shares. Since recently, we faced problems with some Windows 10 who fails to connect to any of those hosts. Windows XP, 7, Linux or MacOSX clients are fine. We can fix Windows 10 clients by commenting the "smb ports = 139", but with this configuration Windows7 and MacOSX clients see the sames shares for all hosts. Our server is running Debian Jessie with Samba 4.2.14-Debian. Few weeks ago we were using Samba 3.5.6. I don't know if the issue started after a Windows 10 update or the Samba update. Is there a simple workaround for this ? Thank you in advance. Guillaume Duteil
Hi Guillaume, Am 22.05.2017 um 18:27 schrieb Guillaume Duteil via samba:> We have been using for years the option "netbios aliases" with 9 aliases > (+ 1 main host). > Each one has it's own shares.Can you show me your smb.conf? Regards, Marc
try to set smb ports = 139 max protocol = NT1 Le 22/05/2017 à 19:56, Marc Muehlfeld via samba a écrit :> Hi Guillaume, > > Am 22.05.2017 um 18:27 schrieb Guillaume Duteil via samba: >> We have been using for years the option "netbios aliases" with 9 >> aliases (+ 1 main host). >> Each one has it's own shares. > > Can you show me your smb.conf? > > > Regards, > Marc >-- Arnaud FLORENT IRIS Technologies phone: (33) 03 20 65 85 80 fax: (33) 03 20 65 85 81 mailto:aflorent at iris-tech.fr