Samba and Windows 10 -- Sept. 2019

hooperre

Sorry for bringing up a much maligned topic. A "Windows 10 Samba" search yields 50 pages of results. Seems like the newest Windows update has brought some unintended consequences.

Recently, my Windows 10 Pro PC and RetroPie will not connect over the same network with either //RETROPIE or //[ip address].

Is there a working/stable fix for the fact that SMB 1.0 is disabled on Windows after updating? I tried setting min_protocol=SMB3under [global] to no avail in SMB.conf. I tried turning SMB 1.0 back on my Windows device to no avail.

Any thoughts? Thanks.

ETA: Also have the RPi user and password saved in my windows credentials.

mitu

Samba knows SMB2 and SMB3, so disabling SMB1 on Win10 wouldn't have this effect. Maybe Win10 has disabled guest browsing over SMB sometime ago for the Enterprise/Education versions has anything to do with it ?
What version of Win10 are you using ?

SolemnSpirit

I'm using Windows 10 Home with the latest update and //RETROPIE works fine for me and needs no credentials to access, never has.

Thorr69

If one is wireless and the other is wired, you may have issues. Mine can't see each other unless I have them both wired. I've done verythign o make sure that wireless isolation is not present on my router, but in the end it still didn't matter. One I used wired connections on both, they always see each other properly.

hooperre

@mitu said in Samba and Windows 10 -- Sept. 2019:

What version of Win10 are you using ?

Windows 10 Pro ver 18362

@SolemnSpirit Weird. I'm on Pro (oops) and I haven't needed credentials or anything in the past, but now I can't get it to work. Same network and everything. Spinning my wheels.

@Thorr69 Both wireless, but definitely good to know. Thanks.

Starting to think it's a connectivity / router issue, but I can SSH in which always makes the answer more convoluted.

mitu

@hooperre said in Samba and Windows 10 -- Sept. 2019:

Starting to think it's a connectivity / router issue, but I can SSH in which always makes the answer more convoluted.

If SSH (or WinSCP) works, then there's no connectivity problem. I'll give it a test with the latest updates.

What you can try is to disable the guest browsing on the Pi, by editing /etc/samba/smb.conf and removing the guest ok = yes from each RetroPie share.
For the record, guest browsing doesn't work for me also, I get prompted for user/password and using the pi user works. I have saved the user/pass in the Credentials vault and I'm not prompted for it.

I'll try to install the Sept. updates and see what happens afterwards.

hooperre

@mitu I commented them out, but it still isn't working. I removed all the Windows Credentials I made thinking maybe that was a cause of the problem somehow. Still a no go.

BJRetro

@hooperre who knows if this is it for you but I find sometimes with Samba I have to be in the retropie setup menu on the pi for it to connect to Samba with my Windows 10 cpu, no idea why.

KN4THX

@hooperre just out out curiosity are you using \\ or //?

hooperre

@KN4THX I’ve tried both but //.

mitu

@hooperre said in Samba and Windows 10 -- Sept. 2019:

@mitu I commented them out, but it still isn't working. I removed all the Windows Credentials I made thinking maybe that was a cause of the problem somehow. Still a no go.

I installed the Sept. updates and I can connect as before (prompted for user/pass since I removed the credentials from the vault). Once the connection is established, I can see (via sudo smbstatus), that Windows uses SMB3 for the connection.
What release is your Win 10 ? I have mine at 1809, maybe the newer 1904 has different defaults. Is your system part of a AD domain or it's just your home computer ?

hooperre

@mitu Home computer. 1904.

Thorr69

@hooperre said in Samba and Windows 10 -- Sept. 2019:

@KN4THX I’ve tried both but //.

You definitely need to use \\

hooperre

@Thorr69 Okay ya that's what I had been using. It was hard to imagine it without actually entering it in windows explorer. The other way will open an internet browser.

mitu

@hooperre said in Samba and Windows 10 -- Sept. 2019:

Home computer. 1904.

The only difference I see is the release - I have mine on 1809 (OS Build 17763.737).

hooperre

@mitu I tried with my Pi 4 running Lakka and having the same issues. Can SSH in but not use samba. Samba has always been weird on my surface pro 3 tbh like if there was an existing quick access (recents) link I could get right in, but otherwise I’d have to try a bunch of times to get in. It would usually work eventually. Now it isn’t. Very frustrating. I’m about to say oh well and go back to just doing things on my usb.

hooperre

@mitu So I found a suggested fix that worked.

open run (win + R)
gpedit.msc
With local group policy editor open navigate to the following
Computer Configuration > Administrative Templates > Network > Lanman Workstation
Enable insecure guest logins

This allowed me right into my pi (4) running a source build of RetroPie. Tagged you because I'm not 100% positive how big a risk this is to my CPU and thought you may know.

mitu

@hooperre Thanks for the solution - that's basically the same fix applied to Education/Enterprise SKUs back when this settings was enabled about 2 years ago. I guess it tricked down to newer releases.
I guess I'll have to upgrade to the latest version (1903/1904 ?) to give it a test.

hooperre

@mitu said in Samba and Windows 10 -- Sept. 2019:

@hooperre Thanks for the solution - that's basically the same fix applied to Education/Enterprise SKUs back when this settings was enabled about 2 years ago. I guess it tricked down to newer releases.
I guess I'll have to upgrade to the latest version (1903/1904 ?) to give it a test.

Do you happen to know the security implications of leaving this enabled?

mitu

@hooperre Well, Microsofts considers it's insecure, so they must have a reason. I guess is mitigates the risk that someone inadvertently opens a guest only share and mistakenly runs something from it.

https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser