Logging into Pi from WinSCP on new PC

SpudsMcToole

Anyone know what's going wrong here? I just got a new PC and fired up WinSCP on it, having imported all the old configs and site info, but when I try to connect to the Pi it says "Host 'Retropie' does not exist".

Nothing but the PC has changed, it's still running on a hardwired Ethernet connection from the computer to the Pi, from the same router. I went to the Pi and ran "Show IP" and entered that as the host instead (192.168.x.x) and it says "Network connection timed out". What am I missing?

mitu

@SpudsMcToole Is your new PC in the same network as the PI ? If you run from a command line (on the PC)

ping 192.168.x.y

where 192.168.x.y is the Pi's IP, does it work ? Do you have some antivirus/firewall installed on the PC that might intercept the connections and filter them ?

SpudsMcToole

@mitu Ah, that's probably it - I get "host unreachable" from the ping. I've installed AVG antivirus (the same antivirus as the old PC had) but it hasn't popped up any window asking me if I want to allow the connection. I'll see if I can figure how to get it to butt out, ta.

SpudsMcToole

Hmm, no, I've added an exception to Windows Firewall to allow WinSCP.exe through, but no difference.

SpudsMcToole

This is weird. The Pi tells me its IP is 192.168.0.8. If I ping that address from the PC, it actually tries to ping 192.168.0.15 and returns "Destination unreachable".

But if I try to ping 192.168.0.15 from the PC directly, the pings work fine . Entering that IP into WinSCP, though, gets this:

"Connection refused.

The server rejected SFTP connection, but it listens for FTP connections.

Did you want to use FTP protocol instead of SFTP? Prefer using encryption."

mitu

@SpudsMcToole That's because 192.168.0.15 is the PC's address, so it's normal ping would work. Whatever it is, your network connection to the PI is not going through. Are both systems wired ? Do you have any router ACL in place (MAC filtering, firewall, etc.) ?

SpudsMcToole

Not sure what you mean by any of that.

The PC is connected to the Pi by an Ethernet cable. I don't know what "router ACL" means, but there's nothing there that wasn't there before when everything worked, so it seems like this must be some kind of software issue on the PC somewhere.

mitu

@SpudsMcToole What router are you using ? Does it have web page your can look at the settings/configuration ? I suppose the internet works from the PC (most likely your posting here from it).

SpudsMcToole

A Netgear DGND3700. I can log in to its admin page, yes.

cyperghost

@SpudsMcToole
Did you activate SSH server within your RetroPie setup? This is also a common mistake as this service is not activated by default ;)

SpudsMcToole

@cyperghost Yes, I did that again a few hours ago, even though as I said I've been using it for months and months with WinSCP already.

ByteThis

@SpudsMcToole Is the version of WinSCP your currently using the same version as your old PC ? I had read somewhere that the newer versions of WinSCP have problems connecting to Retropie. I can't remember where I saw this info to guide you but maybe try an older version ?

SpudsMcToole

@ByteThis I've tried the old version too. Exactly the same.

I just tried connecting through FileZilla, though, and it worked fine. Which is weird.

SpudsMcToole

Won't connect in FTP Voyager either. Or SFTP Net Drive. This is really bizarre.

ByteThis

@SpudsMcToole Did you try to turn on Network Discovery in your Windows ? If I remember..WinSCP is fussy.. Just trying ..I use WinSCP and it rocks..I hate changing software..lol.

ByteThis

@SpudsMcToole said in Logging into Pi from WinSCP on new PC:

Won't connect in FTP Voyager either. Or SFTP Net Drive. This is really bizarre.

Try exiting all instances in AVG via task manager then try again maybe.

EDIT: Can you access via PUTTY ?

SpudsMcToole

@ByteThis I uninstalled AVG (it was messing up other stuff) and installed Bit Defender instead, which made no difference, then replaced Bit Defender (it was screwing up Steam) with Kaspersky, which also made no difference.

And yes, I checked and Network Discovery is on. (Presumably if it wasn't FileZilla wouldn't be able to connect, which is what also kinda rules out most other possible explanations. It can't really be the PC or the Pi or an anti-virus blocking it if FileZilla can get in.)

Really want to get this sorted, because accessing the Pi via FileZilla is a complete PITA, and I know my way around WinSCP.

SpudsMcToole

@SpudsMcToole SOLVED! I checked my router admin page, and for some reason the Pi was lying about its IP address. Put the one showing on the router page into WinSCP and bingo :)

ByteThis

@SpudsMcToole Glad you finally got it working !