Samba Shares stopped working after recent Windows 10 update

[PhilboBaggins]

Pi Model or other hardware: Raspberry Pi 3b+
Power Supply used: 5V/2.5A DC power input
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.7.1
Built From: retropie-buster-4.7.1-rpi2_3.img.gz
USB Devices connected: I’m running ROMs off a Corsair 128GB USB drive
Controller used: SNES USB gamepad (I think it’s 8bitdo but I’ve had it for a while). ROHS Mini Keyboard
Error messages received: Windows cannot access \\RETROPIE

Hi there,

Samba Shares was working fine for quite a while, but stopped working after a recent Windows 10 update. I confirmed that "Enable insecure guest logons" is still Enabled for my Lanman Workstation config. If anyone has insight on what settings might have changed as a result of the update I'd really appreciate it.

[mitu]

Try accessing the shares directly, e.g. via \\retropie\roms.
You can also try to map the roms folder as a drive and provide the user - pi - and password during the creation of the mapping.

[PhilboBaggins]

@mitu I tried mapping the romsfolder to a drive using \\[my Raspi IP]\romsbut the folder can't be found. I double checked that my raspi's IP is the same as before and it's still connected to my Wifi network like before. In addition to Windows updating recently, I also updated my raspi's password not too long before that. Could that be the issue? I changed the password for the \\RETROPIE drive I created just to see if that was the issue, but it didn't seem to work for that drive.

Is it also possible certain Windows permission were switched after the update? Off the top of my head I don't know which permissions should be config'd.

[mitu]

If you changed pi user's password, then check in Windows credentials manager if you have a credential for the \\retropie system associated. If yes, then delete it and try mapping again the folder.

[PhilboBaggins]

@mitu I deleted and created new credentials for \\retropie and \\retropie\romsbut I'm still not connecting to the raspi. I tried adding a network location for \\[myRaspiIP]\roms but it also gave me the message The folder you entered does not appear to be valid. Please choose another. It's as if my raspi's IP is not recognized, even though I know it's correct.

[mitu]

@philbobaggins You screenshot doesn't show the path you're trying to add. Make sure you're using 2 backslashes when entering the location \\retropie_ip\roms.

[PhilboBaggins]

@mitu I used two backslashes for the location.

I'm also able to ping my retropie from my PC.

[mitu]

Then I have no idea. I can't reproduce this and not sure what causes it - I have the latest updates on Win10 and the mapping or browsing still works.

What Windows edition do you have and which release ?

[PhilboBaggins]

@mitu

[mitu]

Windows Education Edition has - by default - disabled guest browsing, this may be the issue here, though this isn't a recent change and I'm surprised you've been able to access \\retropie before any recent updates (or re-installation?).

Try using SFTP to access RetroPie with WinSCP, instead of file shares.

[PhilboBaggins]

@mitu I enabled guest browsing initially and got samba shares working (until recently). I have constant connection issues when using SFTP with WinSCP. It keeps trying to connect, and then only connects for 5-10 seconds before it disconnects and tries several times before reconnecting again for 5-10 seconds. This is the reason samba shares has been preferable to me. Is this an experience you've heard of with other users?

[mitu]

@philbobaggins said in Samba Shares stopped working after recent Windows 10 update:

Is this an experience you've heard of with other users?

Honestly, here in the forums at least, your issue seems more prevalent than any SSH/SFTP problems when used to tranfer roms.

[gmsinger8808]

@philbobaggins If you go into the RetroPie-Setup Script and access the Samba Share settings under Configuration / tools, then samba, if you click restart Samba Shares, do you get a message about samba.service not found? I'm having the same issue with Samba and I noticed that message. I am running 4.7.7 currently.

[PhilboBaggins]

@gmsinger8808 I tried restarting the Samba service and it looks like I'm getting the same error as you are.

@mitu Do you have any thoughts on what might have changed recently that would cause the service to not be found? I've never tried removing and re-installing Samba shares but do you think it would be worth giving it a try?

[mitu]

@philbobaggins said in Samba Shares stopped working after recent Windows 10 update:

I've never tried removing and re-installing Samba shares but do you think it would be worth giving it a try?

No, I don't think that will make a difference. The restart error is a bug in the config script, the service is not called samba anymore.
You can check that it's running with

systemctl status smbd
systemctl status nmbd

[PhilboBaggins]

@mitu I don't understand the entire output but it looks like Samba is running fine.

[mitu]

Yes, it works fine (as expected), the issue is on the Windows side.

EDIT: can you try installing wsdd and see if it changes anything on the Windows side ? It's a simple script which you can run from the command line to test if retropie is visible again on the network from Windows.

[JenGun]

@philbobaggins Please open the command prompt in Windows 10 and run:

net use r: \\retropie\roms

[gmsinger8808]

@mitu Could this have to do with the disabling of SMBV1? Would forcing SMB3 on the Pi help with Win 10 communication?

[PhilboBaggins]

@jengun said in Samba Shares stopped working after recent Windows 10 update:

net use r: \retropie\roms

Interesting. I thought enabling "Enable insecure guest logons" for my Lanman Workstation config would have allowed guest access. Apparently not (see below). I don't suppose you have a solution?