RetroPie is not displayed in the Windows network environment

Xabib2302

Good time of day. There is one problem. The fact is that RetroPie is not displayed in the Windows network environment although RetroPie is connected to WI-Fi and SSH is enabled.

mitu

@xabib2302 SSH has nothing with retropie not showing on the network, it's all about Windows File Shares. Try connecting from Windows Explorer with the IP address (\\192.168.100.5) or using \\retropie.local.

herb_fargus

@mitu to be fair though I do see my pi through my router page on the network (which is what his pic looks like) whereas sometimes I don't see retropie in the network page of windows explorer even though it's connected. At least not til I connect to the ip like you mentioned.

Xabib2302

@mitu Still.

mitu

@xabib2302 Are you able to ping the ip address ? Open a command line (cmd) on your PC and then type

ping 182.168.100.5

Are getting a reply ?

Xabib2302

@mitu

mitu

@xabib2302 From the screenshot (although I don't understand what language is), it looks like your RetroPie is not reachable from your PC. You either have a firewall between the 2 devices or the Router has AP Isolation enabled and the devices are not able to communicate with each other. Either way, you need to find out what's preventing the communication and fix it outside RetroPie.

Thorr69

I don't think it will show up unless the Samba shares are enabled. Once I set up the samba shares, I can usually get to the Pi by IP address. After I connect to it once, it can be accessed by name.

I have had lots of trouble with this very problem. I've still never been able to get my Pi 3 to work on WiFi. It only works when wired. I have an OrangePi as well and that worked for a while then went haywire on WiFi. Eventually I reset all device addresses on the Router and they started working again.

cyperghost

@Xabib2302

Please ping 192.168.100.5
alternatively you can ping retropie

You pinged wrong adress. Come on you were born on the "Day of the Army" ;)

mitu

Yeah, @cyperghost is right, didn't even notice I put the wrong address in the ping command.

Clyde

@mitu It's nice to observe synergy at work. :)

Xabib2302

@cyperghost The communication check failed to detect the retropie node.
Check the host name and try again.

Xabib2302

@mitu AP Isolation disabled

mitu

@xabib2302 If pinging 192.168.100.5 still doesn't work (i.e. you get host not found) then the same comment as before applies - your RetroPie device at 192.168.100.5 is not reachable from your PC, so there's nothing RetroPie can do. Check if you have any firewall/Antivirus(?) installed on your PC and maybe temporarily disable them while repeating the ping test to see if they interfere.

Xabib2302

@mitu The SmartScreen and firewall disabled and still the result is zero

Clyde

@xabib2302 Can you access the console of Retropie? (i.e. connect a keyboard to your Pi and press F4 in Emulation Station)

Then, you could check how it looks from Retropie's side with the command

ifconfig     # NOT ipconfig like in Windows

or you could try to ping your router or Windows from the Pi:

ping 192.168.100.1    # or whatever your router's IP is
ping 192.168.100.2    # or whatever your PC's IP is

As a desperate measure, you could even test if your Pi responds to pings by pinging itself:

ping localhost

Remember, all commands are to be issued on the Pi's own console you land in after pressing F4 in Emulation Station.

Unfortunately, my knowledge about solving network issues is very limited. The above commands are meant to provide further information an to rule out some unexpected problems on the Pi's side.

ByteThis

@Xabib2302 I found if you have Windows 7 or higher, you may have to turn on network discovery if it isn't enabled by default : Windows Network Discovery

micro-bee

Not sure your having ssh or samba issues.
For ssh (you can do a reinstall):

sudo apt-get -y purge openssh-server
sudo apt-get -y install openssh-server

For Samba:

sudo nano etc/samba/smb.conf
Just change the workgroup (and should be find in Windows)

grant2258

mine never showed up on a static ip for some reason but worked with dchp(on the windows machine)