WinSCP Stored Session - Host does not exist
I'm running 5.8.1.1 (beta) right now, but I believe this is in the 5.8.1.0 final as well.
If you choose "Session" (ie: stored session) for a WinSCP connection, the stored session will not connect through RDM -- UNLESS -- the stored session name is the same as the host.
For example: Session name "Server 1 FTP" will not connect and gives "Host does not exist" error....whereas using a stored session name of "10.1.2.3" will connect to that server.
It looks like RDM is treating the stored session name as the actual host name, instead of reading that host information from the stored session.
TEMPORARY WORKAROUND #1 - Put the stored session name in double quotes (")
-or-
TEMPORARY WORKAROUND #2 - Make sure stored session name in WinSCP is the same as the Host you're trying to connect to (IP works, haven't tried DNS or FQDN).
Thanks!
P.S. - Would really love to see the ability to designate a private key from within RDM for WinSCP, instead of using stored sessions. That way I can share the connection, but other people can use their own keys.
edited by sinclaj1 on 7/27/2010
All Comments (6)
Hi,
I added a feature request for the global WinSCP parameter (private key). Also, I verified for the bug about the session, can you do a test for me (I don't have WinSCP anymore installed). Try to put the session name in quote and let me know if it fixing the problem.
David Hervieux
That works, yes (using double quotes).
Excellent, I will add this fix for the next version.
Thank you for your help
David Hervieux
Update -
Using version 5.8.2.1. Putting the session in quotes only works when the session name is just an IP address or Host Name. Sessions like "Test Server + key" does not work (with or without quotes).
Hi,
Do you know how to make it works from command line ? Maybe it's a bug in WinSCP ?
David Hervieux
Found the problem, but this is how you run a stored session from command line:
For GUI --- winscp.exe <storedsessionname>
For no GUI --- winscp.com <storedsessionname>
The problem I ran into...my stored session had a "+" in the name. It didn't work from command line or RDM...so that was due to a limitation in WinSCP's command line interpreter.
Sorry to pin that on you as a bug.
Would still love to be able to designate a file location (central location) for a private key that could be used instead of having to use saved sessions stored within WinSCP.
I think the command line for that would be something like winscp.exe [mysession] [/privatekey=<key_file>] [/hostkey=<fingerprint>]