New Pi (3 B) suddenly can't be accessed by PC file explorer but can be by WinSCP?

mitu

@moltke44 This looks more like a problem on the PC, than on the RetroPie system. What is the error message you get when you type \\retropie in Windows Explorer ?

moltke44

Thanks, @mitu

A generic popup window "Network Error: Windows cannot access \RETROPIE , try try and identify and resolve the problem click diagnose'. Which is frustrating because, again there were no problems until today (I can only assume after the latest Windows update). I've turned the fire wall off to check, allowed a rule for specifically the pi IP, without result. WinSCP connects just fine.

Is there any kind of sharing or open access I can set within the pi?

mitu

@moltke44 said in New Pi (3 B) suddenly can't be accessed by PC file explorer but can be by WinSCP?:

Is there any kind of sharing or open access I can set within the pi?

The system that enables file sharing on the Pi is calles Samba. You can check if the services are running by executing

systemctl status smbd
ststemctl status nmbd

The output should be something similar to this

● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd)
   Active: active (running) since Sun 2017-12-10 23:46:13; 21h ago
  Process: 730 ExecStart=/etc/init.d/smbd start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/smbd.service
           ├─740 /usr/sbin/smbd -D
           └─746 /usr/sbin/smbd -D

pi@retropie:~ $ systemctl status nmbd
● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd)
   Loaded: loaded (/etc/init.d/nmbd)
   Active: active (running) since Sun 2017-12-10 23:46:12 ; 21h ago
  Process: 542 ExecStart=/etc/init.d/nmbd start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/nmbd.service
           └─729 /usr/sbin/nmbd -D

How is your PI connected to the network ? Cable/Ethernet, Wifi ? Do you have a router where both systems are connected ?

moltke44

@mitu

I enabled SAMBA from the retropie menus I think but I will check the command line and see what the output says. Yeah, both are connected to a router, just single home network. Nothing changed there. I see the pi come up on the network share, and can ping it fine as well.

moltke44

@mitu

And checked to see if the command results matched. They seem too.

/home/pi/RetroPie/roms$ systemctl status smbd
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
Loaded: loaded (/etc/init.d/smbd)
Active: active (running) since Sun 2017-12-17 03:30:32 UTC; 3h 56min ago
Process: 1459 ExecReload=/etc/init.d/smbd reload (code=exited, status=0/SUCCESS)
CGroup: /system.slice/smbd.service
├─22253 /usr/sbin/smbd -D
└─22256 /usr/sbin/smbd -D

/home/pi/RetroPie/roms$ systemctl status nmbd
● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd)
Loaded: loaded (/etc/init.d/nmbd)
Active: active (running) since Sun 2017-12-17 03:30:34 UTC; 3h 57min ago
CGroup: /system.slice/nmbd.service
└─22327 /usr/sbin/nmbd -D

I've searched and searched ... reinstalled the samba package, and nothing. XML scraper configured to auto find the roms and is blocked too .. but I guess just because the mapped drive is blocked as well. I attempted a net session dos command to look at \retropie and got 'access denied' which leads me to think maybe something on the pi?

mitu

@moltke44 Less likely to be something related to the user on the PI, since it allows guest access with full rights via the file shares (Samba). It really looks something related to your Win 10 installation.
I found something related to this at https://tech.nicolonsky.ch/windows-10-1709-cannot-access-smb2-share-guest-access/ - it seems that a recent feature update in Windows disable guest access via SMB2.
If you're running the 1709 build of Win 10, you could try the workarounds in the article.

moltke44

@mitu

That's it! Thank you! I can't believe this isn't effecting more people and generating more discussion ... but maybe I'm one of the few who prefer to transfer that way over sftp. Either way, much appreciated.

mitu

@moltke44 Ugh, that's going to bite a lot of people in the future and I get the same feeling w.r.t. generating a lot more discussion.
Just to confirm, can you remove the workaround and test again ? If you'll get the same error, then the problem is clearly on the Windows site.

moltke44

Sorry for the delayed response and unneeded bump, @mitu but I did confirm this. Actually on an entirely different machine had the same issue with Windows 10 updates. Made the change and again back in business.

mitu

@moltke44 What version of Win 10 are you using ? Pro/Home/Ent/Education ?