Problems WinSCP to Arista Router

Advertisement

gil_happy
Joined:
Posts:
4

Problems WinSCP to Arista Router

Hello, I seem to be having an issue when trying to WinSCP from my Window 10 PC to an Arista router.

When I attempt to connect using the correct username, password, and port number, I receive 2 error messages:

1) Host is not communicating for more than 15 seconds. Still waiting... Note: If the problem repeats, try turning off 'Optimize connection buffer size'.

2) Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended).

The Arista router has a bash prompt and I believe the 'scp' binary is installed and executable.

Does anyone have any suggestions?

Thanks in advance!

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
41,285
Location:
Prague, Czechia

Re: Problems WinSCP to Arista Router

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

gil_happy
Joined:
Posts:
4

Hi, thank you for the response... The router does indeed have a Linux like shell. If I go into bash, then do a search for 'scp', I see it under:

-rwxr-xr-x 1 root root 82420 Apr 12 2018 scp

Just as an FYI, I have a different machine (a Linux server) where I can successfully WinSCP to it and scp attributes are:

-rwxr-xr-x 1 root root 79880 Sep 12 09:46 scp

Reply with quote

Advertisement

gil_happy

Good question.... once I ssh using port 22 to the Arista router, I enter the user / pass. Then from the terminal prompt, I put it into 'enable' mode (similar to a Cisco router), and then I type 'bash'. At that point I'm in the bash shell.

That first part of the login could be the problem.

Reply with quote

Advertisement

You can post new topics in this forum