I have some interesting behaviour with ssh. its not working for some reason and i am trying to get to the root cause behind it-usually it is fairly simple job, but for some reason its giving me a hard time at this instance.
on the router on which i am trying to ssh on, i see the following error message:
Connection closed by x.x.x.x
Then I tried using option -I
ssh -I admin x.x.x.x
no support for PKCS#11.
Connection closed by x.x.x.x
I also could not understand what is the error PKCS#11 error??
Just a quick update here, i was trying incorrect parameter while using the option with ssh giving me the error PKCS#11.
Actually i should have used -l (ie small L) and i thought it to be -I (capital I, for India).
However, the strange thing is it works only if use the -l option and specify the username. Why cannot i do it directly like "ssh x.x.x.x". It is asking me for password when i do this way, but never accepts that password.
where are you attempting SSH from when you try simply ssh x.x.x.x? And how are you initiating the SSH? Is it at a command line, or in a terminal emulator (such as SecureCRT or TeraTerm, or Hyperterm)? I know that sometimes if I initiate SSH from a command prompt on a device where I am already authenticated it will supply the user name in the connection request and I just get a prompt for password, which is what you describe. So the question might be whether this is happening and if so is the device supplying the user name admin (which is what you have configured on the router).
Thanks for the update and telling us that it is working now. I am a bit puzzled about what it would have been that prevented your SSH attempts and then started working when the SSH was initiated from the mac. I guess the important thing is that now it is working for you
I just had a similar issue with this. But something caught my eye, so let me ask you something..
Have you had connectivity via SSH before? Was something changed?
The reason I ask is I see the following statement:
line vty 0 4
privilege level 15
transport input telnet ssh
It appears that the vty 0 4 is wanting a local username/password. Which, btw, you may want to change that username from what it is...
Does the device you are SSH'ing from have transport output ssh configured?
Also, one of the problems I encountered was that I could connect to the device. I got the warning banner, and it asked for my password. But after three times, it booted me like yours is. Turns out my default gateway was set incorrectly on the device I was attempting to SSH from.
Just a couple things to help troubleshoot...
Oh, and I take it you're not using aaa at all? I saw the no aaa new-model. That points to a possible incorrect password as well, stored locally on the device. I've found that in the past..someone forgot a device during password change time
I had set the ssh for the first time on the device but surely i had changed the username & password myself and made sure it showed up on the sho run.
I was initiating ssh from an apple laptop using its terminal window (shell) so there was no way I could do something like "transport output" settings (unless it is done internally somewhere on the mac pc)
locally I could login without any problem. and once i logged in using the mac pc, it went all smoothly ever since.
That is really weird that having reached the router login page and not making through after 3 -4 password attempts issue was resolved by fixing the default gateway on the initiating device. I would have thought reaching the router login would eliminate any routing related concern.
Thanks for sharing your experience and i am glad things are working now.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.