Win 10 upgrade and Samba issue - [Solved]

[arcenciel]

I'm posting this here as this is the only forum I'm allowed to post in...
After a recent Win 10 upgrade, I noticed that my working Samba shares and folders have disappeared from my Win 10 file explorer.
While the Samba is working properly in my new Mint install, Win 10 will no longer find the shared drive.
After a bit of research, I discovered that MS has implemented a new " feature" in that they no longer allow valid Win 10 users to access guest services.
Fortunately, I can open the shared folders as long as I explicitly access them from the "network mode" of file explorer.
Bizarrely, the shared Server/drives show up in file explorer of the previously created shortcut to the saved folders. I would show them here but I can't insert any images in this post.
My Samba status shows no open folders or files but Win 10 can create, edit and delete in the folder.
Some users have changed their firewall rules to allow access to a UDP port above 5500 ( I've lost the actual port number ) and others have made the following change to their registry:
https://techjourney.net/cannot-connect- ... indows-10/

Has anyone else seen this? Is there something wrong with my smb.conf parts of which follows:

<snip>
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
# djb
# workgroup = WORKGROUP
workgroup = HOMEGROUP

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
wins support = yes
<snip>
#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
interfaces = enp33s0
; interfaces = 127.0.0.0/8 eth0

<snip>
#
usershare owner only = false
#
<snip>

# added Nov 18/17
#
[oldpics]
path = /oldpics/
browseable = yes
read only = no
writeable = yes
[olddata]
path = /olddata/
browseable = yes
read only = no
writeable = yes

Any feedback would be really appreciated.

[martyfender]

If my memory serves me correctly Microsoft enabled SMB 2. plus with a recent update. if you re-enable SMB 1.0, your guest account, I believe, will work. You will have to do some research in how to do that as I don't have a Window 10 box to try it on.
I saw this posted on an Android forum thread on xda developers. I have to use SMB 1.0 on my Android tablet to access my Linux Live, persistent USB shares through the guest account.

Here is a link to the xda post that tells how to do it for the Window 10 Fall Creators Edition:

https://forum.xda-developers.com/showpo ... ount=21938
which has this link relevant to you:

https://support.microsoft.com/en-us/hel ... rsion-1709

Code: Select all

Windows 8.1 and Windows 10: Powershell method with Administrator access
SMB v1 Protocol
Detect: 	Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol
Disable: 	Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
Enable: 	Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
SMB v2/v3 Protocol
Detect: 	Get-SmbServerConfiguration | Select EnableSMB2Protocol
Disable: 	Set-SmbServerConfiguration –EnableSMB2Protocol $false
Enable: 	Set-SmbServerConfiguration –EnableSMB2Protocol $true

Note: A change to or from Enabled to Disabled requires a reboot.

https://support.microsoft.com/en-us/hel ... indows-and

I hope that this may help you.

[altair4]

Please post the output of the following commands:

Code: Select all

testparm -s

Code: Select all

net usershare info --long

And ,,, you can name your workgroup HOMEGROUP I suppose just be aware that there is no such thing as a Windows Homegroup in Linux.

[arcenciel]

here's the ouput from testparm requested:

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Processing section "[shared_drive]"
Processing section "[oldpics]"
Processing section "[olddata]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
workgroup = HOMEGROUP
server string = %h server (Samba, Ubuntu)
interfaces = enp33s0
bind interfaces only = Yes
server role = standalone server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
wins support = Yes
usershare allow guests = Yes
usershare owner only = No
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb


[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
browseable = No


[print$]
comment = Printer Drivers
path = /var/lib/samba/printers


[shared_drive]
path = /home/dave/shared/
read only = No
guest ok = Yes


[oldpics]
path = /oldpics/
read only = No


[olddata]
path = /olddata/
read only = No

dave@dave-MS-7A34 /etc/samba $ net usershare info --long
[shared]
path=/home/dave/shared
comment=
usershare_acl=S-1-1-0:R,S-1-5-21-986546555-2132667109-3166389256-1000:F,
guest_ok=n

I enabled smb 1.0 using the command described above and it didn't seem to make any difference...

[altair4]

I've run out of time today but:

I would get rid of the share you defined in whatever file manager you are using:

Code: Select all

dave@dave-MS-7A34 /etc/samba $ net usershare info --long
[shared]
path=/home/dave/shared
comment=
usershare_acl=S-1-1-0:R,S-1-5-21-986546555-2132667109-3166389256-1000:F,
guest_ok=n

It's already defined in smb.conf. It won't fix this particular issue but it just shouldn’t be defined twice.

Is there a reason you are doing this:

interfaces = enp33s0
bind interfaces only = Yes

Do you have multiple network cards and you only want samba access through one of them?

If this is purely a problem where Win10 cannot "discover" by browsing the Samba server you can add a few things to your smb.conf file. Right under the workgroup = WORKGROUP line add: name resolve order = bcast host lmhosts wins
Then restart samba:

Code: Select all

sudo service smbd restart

Code: Select all

sudo service nmbd restart

There was an issue back when Win10 was initially released concerning host discovery and other issues but that was all resolved a long time ago. The only issue now is the reverse of yours - discovering a Win10 machine from Linux now that Win10 disabled SMB1. What version of Win10 are you using: Open Run Win Key + R and type winver

[arcenciel]

I specified the interface as it was working fine on eth0 which was a wifi card that wasn't working properly but wouldn't work on the wired network device enp33s0.
After making the changes you suggested. Neither the share nor Samba is discovered. A step backwards...
I'm on Win 10 1709 release...
is it possible this is a firewall issue???

[altair4]

After making the changes you suggested. Neither the share nor Samba is discovered. A step backwards...

They never were discovered based on your initial post:

After a recent Win 10 upgrade, I noticed that my working Samba shares and folders have disappeared from my Win 10 file explorer.
While the Samba is working properly in my new Mint install, Win 10 will no longer find the shared drive.

On your Win10 machine open Run WinKey + R and enter:

Code: Select all

\\dave-MS-7A34.local

Don't forget the .local at the end.
Does it list all of your shares and can you access them?

If not disable the Mint firewall and try it again:

Code: Select all

sudo ufw disable

[arcenciel]

YES... after opening powershell (admin) and [win key] + r the shares are all there and can be opened. Now I'm really confused. Why aren't they accessible from the normal windows file manager??? Windows is pure black magic. All I had to type is // and they were there to choose from...
I guess it was my bad.
As long as I use the "Add a Network Location Wizard" I can get them and open them and they reappear in my file Explorer. Stupid me...