GPi SSH/PuTTY issues

cyperghost

@tmshll do You see an IP if you go to RETROPIE --> WiFi?
Furthermore how did you enable SSH service and entered WiFi credentials?
Is there a Proxy or Firewall in your network?

tmshll

@mitu Hi, just tried a few pings, got the following:

Ping: transmit failed. General failure

mitu

How are you typing the command ? This error happens when your PC is not connected to the network or has limited connectivity.

tmshll

@cyperghost Hi,

I created an SSH file (blank txt file and then deleted the extension) I also made sure SSH was enabled via interfacing options through Retropie.

As for setting up the WiFi I created a wpa_supplicant.conf file on my SD, and input my details (am I right in thinking my SSID is the same as my WiFi network name on my router?) I think this worked as I tested the WiFi by downloading extra splash screens via the GPi case.

tmshll

@mitu okay, just reset my WiFi and got a response from my GPi (Reply from 192.168.1.7: bytes=32 time=48ms TTL=64)

Should I try PuTTY again?

tmshll

@tmshll @mitu just tried putty and got the message:

Remote side unexpectedly closed network connection

mitu

Are you sure you don't have a firewall on your router/Wifi AP ?

tmshll

@mitu how could I check if there's one in place? Ty

mitu

Check on your Router/AP web management page - see if any firewall is configured in their settings.

cyperghost

@tmshll said in GPi SSH/PuTTY issues:

@cyperghost Hi,

I created an SSH file (blank txt file and then deleted the extension) I also made sure SSH was enabled via interfacing options through Retropie.

As for setting up the WiFi I created a wpa_supplicant.conf file on my SD, and input my details (am I right in thinking my SSID is the same as my WiFi network name on my router?) I think this worked as I tested the WiFi by downloading extra splash screens via the GPi case.

Yes ... that seems correct.

192.168.1.7

Yes, that's your IP ....

@mitu
Windows is very weak in handling ports ;)
You can use pping and a command like PPing retropie 22 to determine if port 22 is open.

@tmshll In your example the call would be PPing 192.168.1.7 22 to check connection to SSH port 22