Blank window upon establishing a telnet or SSH session to the ASA5510

[em]

I am getting a blank window with a flashing cursor after establishing a telnet or ssh session to the ASA. I am tempted to reboot the device but want to know if anyone has sees before and what was their fix?

Regards,

[varrao]

What is the subnet your are trying it?

On whihc interface are you doing it?

Can you share the output of show run ssh and show run telnet?

also show run aaa?

This would help resolving it.

-Varun

[em]

I am trying it from the inside and outside...Because I can't connect to it right now, I can't do sh run...but below is the backup configuration of the ASA. This was working fine till two days ago. I can connect to it via ASDM.

telnet 10.64.148.0 255.255.255.0 inside

telnet 10.200.31.0 255.255.255.0 inside

telnet 10.210.21.0 255.255.255.0 inside

telnet 10.210.98.0 255.255.255.0 inside

telnet timeout 40

ssh 10.64.148.0 255.255.255.0 inside

ssh 10.200.31.0 255.255.255.0 inside

ssh 10.210.21.0 255.255.255.0 inside

ssh 10.210.98.0 255.255.255.0 inside

ssh timeout 40

ssh version 2

aaa authentication telnet console LOCAL

aaa authentication enable console LOCAL

aaa authentication ssh console LOCAL

aaa authorization command LOCAL

[varrao · Accepted solution]

What code arer you running? I though this is the first time you are configuring it.

-Varun

[em]

8.2(3)

[varrao · Accepted solution]

Yes, then definitely what you can do is, remove the ssh config and re-apply it from the ASDM, or reload the ASA. There are quite a few bugs for management access in version 8.2.3 and thats why I was interested in knowing the code.

Let me know how it goes.

Thanks,

Varun

[em]

That did it. I removed both telnet and ssh and then i added them back and it is working. Thanks indeed

[varrao]

Hey thats great, but you might be hitting this bug in version 8.2.3:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCti72411

You might consider upgrading to version 8.2.3.5 or 8.2.4 to rersolve the issue once and for all

Thanks,

Varun