What you're seeing is your SSH client asking for login name the first time; usually the ssh client negotiates the username with the ssh server (in this case the PowerConnect). But the PowerConnect ignores the username that was supplied in negotiation, and asks for the username after the ssh connection goes up. The first username doesn't really matter.
Long story short, Dell has a cheezy ssh daemon; it may have been kludge'd onto a telnet daemon in order to add ssh support at the last minute.
It is working the way Dell thinks it should work :) . So no, there is nothing you need to do to "fix" it, other than to tweak your scripts to give the username twice.
Zitibake
68 Posts
1
January 12th, 2009 13:00
What you're seeing is your SSH client asking for login name the first time; usually the ssh client negotiates the username with the ssh server (in this case the PowerConnect). But the PowerConnect ignores the username that was supplied in negotiation, and asks for the username after the ssh connection goes up. The first username doesn't really matter.
Long story short, Dell has a cheezy ssh daemon; it may have been kludge'd onto a telnet daemon in order to add ssh support at the last minute.
Zitibake
68 Posts
1
January 12th, 2009 15:00
It is working the way Dell thinks it should work :) . So no, there is nothing you need to do to "fix" it, other than to tweak your scripts to give the username twice.
jatsdoit
6 Posts
0
January 7th, 2009 08:00
Anyone has any ideas???
Zitibake
68 Posts
0
January 10th, 2009 08:00
Are you trying to script Putty? I use tcl/expect under Unix.
jatsdoit
6 Posts
0
January 12th, 2009 06:00
I am trying to script Tera Term in windows.
jatsdoit
6 Posts
0
January 12th, 2009 06:00
But let's not even bother about that. I am just wondering why does the ssh server ask for the credentials twice?
jatsdoit
6 Posts
0
January 12th, 2009 14:00
So what I am experiencing is the way the ssh connection is supposed to work?
jatsdoit
6 Posts
0
January 13th, 2009 06:00
Thanks! making sure that I am not going nuts..