SAMBA shares not visible on Windows Network

SUSE Product Topics SLES Configure-Administer
1

Hi experts, I seem to be running into problems with samba shares not being visible from windows machines in an Azure environment.

I have two SLES boxes one 11 SP4 and the other 12 SP2 the latter has shares that once enabled for guest access are visible from windows machines via their ip address. However the 11 SP4 machine’s shares enabled in Yast the exact same way are not visible at all.

I’ve read this might be due to windows server 2016 having smbv1.1 switched off as default and that SLES 12 isn’t affected as it has a later SAMBA release.

Can anyone shed any light on this?

Cheers,

Matt.

2

That seems likely to me, though I do not have any windows servers for
testing. You should be able to see the packets on the wire and determine
if they are limited to 1.x or 2.x (or later) which would answer that.

You may also find this useful:
https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

3

OK, used the powershell commands to re-enable smb1 and disable smb2, rebooted the windows servers and the samba shares are visible.

Hooray!

Thanks.

4

Thank-you for sharing your results.

As a note, I would not disable SMBv2; re-enabling SMBv1 is probably
enough, and having the other around means you get MUCH better performance
on the wire with things like SLES 12 (SMBv1 is a terrible protocol).

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.