All of the sudden Problem with SSH...

[edmaul69]

@nestor1924 can you get into the routers settings and edit it to use a specific ip address for the pi. Like a high number? A lot if times if you have an IP address of something say 192.168.1.5 if something else is the 5th device connected (technically 4th because the router is always device 1) it can steal that ip address. So setting the pi to use a static IP address between 100-254 can resolve that issue.

[nestor1924]

@edmaul69 sorry for the late response i wrote it just before went to sleep, sorry my lack if knowledge but how do i do that?

[Clyde]

@nestor1924 Do you know how you change the settings of your router? If not, do you have a manual for it? What brand and model is your router?

[Alturis]

I was having this problem too (especially as I was having to power it off and on frequently in the early stages of setup).

Until I realized you can just use "raspberrypi" as the address instead. This didnt work at first but then later started working for me.

ssh pi@raspberrypi

That way it just connects to it the same regardless of what rolling IP the router assigns it.

Or to access files via windows File Explorer

\\RETROPIE

[nestor1924]

@alturis so even if winsco doesnt work somethimes, if i use \RETROPIE on the windows file network will it work? Im at work at the moment, but as soon as i get there ill try that, and is "ssh pi@raspberrypi" is a command i have to put somewhere?

[Alturis]

@nestor1924 I am at work as well so I cannot check myself but I think you just use the address "pi@raspberrypi" instead of the IP address.

And yes \\RETROPIE will work from windows explorer but it limits you to only accessing files in the BIOS, configs, and roms folders.

[Alturis]

Actually you just use "retropie" instead of the IP address.

This is how I have my FileZilla server info setup.

[nestor1924]

@edmaul69 i still need help on how to do this, i maanaged to get into my router setting and dont know what to do next, i do see an option to edit the ip adress of the pi whats next???

[edmaul69]

@nestor1924 look for connected devices while your pi is connected and when you find it you should be able to set a static ip address to it.

[Clyde]

@nestor1924 It would really help if you told us the brand and model of your router, as each has its own kind of setup.

[edmaul69]

@alturis i use ip address on winscp to connect to it

[edmaul69]

@nestor1924 on the retropie can you go into retropie menu and then show ip and verify that the ip address matches the one on your winscp?

[Sano]

You may also try to ping retropie.local
On some systems the .local domain of zeroconf is not searchable, so you have to use fqdn (so retropie.localinstead of simply retropie).

[nestor1924]

@clyde i have a technicolor model: TC8715D

[nestor1924]

@edmaul69 i can connect to winscp using the ip adress of the pi instead of the username?, everytime i cant connect to winscp it says username does not exist and thats when i have to unplug and plug back the router to get it to work again, when im connected to my wiscp it says pi@RETROPIE

[edmaul69]

@nestor1924 instead of host name as retropie or whatever use the ip address. user name is still pi

[Clyde]

@nestor1924 Does @Alturis' screenshot match your Winscp window? Instead of "retropie" in the "Host:" field, you would simply enter the IP that Retropie shows you. Beware that the IP might change if you reboot the pi or after losing the connection.

Alternatively, you could give your Pi a static ip address in your router. This site tells you how to find your router's address and log into its web interface (or "Admin Tool" as Technicolor calls it). You can also download the TC8715D's manual there. On page 64, it tells you how to give a "reserved" (i.e. static) IP address to a connected device, such as your Pi. You should use one of the IPs your Pi had before, as the chances are good that those IPs are not used by other devices. To be sure, look at the list of connected devices in the router's web interface to check their IPs.

However, static IPs should be the last resort in an otherwise dynamic network. If looking up your Pi's IP in Emulation Station does the job for you, stay with it.

[creativename]

@clyde said in All of the sudden Problem with SSH...:

However, static IPs should be the last resort in an otherwise dynamic network. If looking up your Pi's IP in Emulation Station does the job for you, stay with it.

Care to explain why? I've never heard anyone else say that. I'm also having some networking issues on my RP setup. But I do use dhcp reservation on my wndr4500 to get static IPs, so your comment has me thinking maybe that is my problem.

[Clyde]

@creativename You got me there, thanks. I muddled static with reserved ips, although they're different things. (Someone may correct me if I err again.) To my knowledge, static ips are configured on the devices themselves, whereas reserved ips are part of the dynamic DHCP process, just reserved for particular devices.

I heard many times that static ips in an otherwise dynamic ip address space may collide with dynamic ips given by the DHCP server, thus they should be avoided or the whole network should be set to static ips. In @nestor1924's case, this doesn't apply, as the ip would be reserved, not static.

edit: The method of assigning ips doesn't affect ssh on your system, so DHCP reservation shouldn't matter at all for your ssh problem. I can't say anything about your Windows problem because I don't use Windows.

[Sano]

@clyde
Actually, duplicate IP are bad, but you can set a DHCP range on a subnet to mix static and dynamic IP.
For example, on 192.168.0.0/24, you can set your DHCP range to 192.168.0.100-192.168.0.200 and use the rest of the subnet for static IP.
But this require minimal network knowledge and some strictness in network management.

That's why generally advised solutions are to avoid this, either by not mixing static/dynamic, or by using dynamic with reserved IP.
My 2 cents.