|
|
Actually, we've found that when attempting to SSH to a Cisco server, you
can add the following lines to your SSH2_DIR:SSH2_CONFIG (note, the config
for the client, not server):
SendKEXGuess NO
allowagentforwarding no
allowx11forwarding no
These should allow you to talk to the router properly using our client
(which, of course, is used by the SFTP client).
At 02:43 PM 12/3/2007, you wrote:
Hi,
>We tried to backup the configuration of our new Cisco VoIP system. We then
>get "invalid password" messages on the console although the correct password
>is provided. Now as we looked a bit deeper into it, the problem seems to be
>on Cisco's side.
We found that even trying to SSH to the Cisco router (for console access)
produced something similar. It seems their SSH server code is broken -- and
SFTP relies on SSH to set up the secure TCP session.
Regards,
Jeremy Begg
------
+-------------------------------+----------------------------------------+
| Dan O'Reilly | "There are 10 types of people in this |
| Principal Engineer | world: those who understand binary |
| Process Software | and those who don't." |
| http://www.process.com | |
+-------------------------------+----------------------------------------+
|
|