After a successfully telnet I always can only write short commands

After a successfully telnet I always can only write short commands

NewsGroups | Search | Tools
 comp.dcom.sys.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
After a successfully telnet I always can only write short commands maxxot2004 08-07-2004
Posted by maxxot2004 on August 7, 2004, 3:14 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Hi.

I have a cisco 1721 which is part of a network of many others cisco
1721. Suddenly I was unable to telnet it and a router replacement
didn't help. I can only telnet into it only by using vty 4. If I use
all the vty the telnet doesn't work. Then I have a couple of others
strange problems: I configured a password for the vty access, but when
I telnet successfully I immediately get access into the router and no
password is asked to me. Then, I can only write short commands. If I
write for example a general "show int" or a "show running-config", the
scroll of the data stops and never goes on after the first scroll.
I tried from different PC and I always got the same behaviour.

Follow a cut and paste of the vty line configuration and the
access-list 14 configuration:

line vty 0 3
access-class 14 in
exec-timeout 3 0
password xxx
logging synchronous
no login
escape-character 27
line vty 4
access-class 14 in
exec-timeout 3 0
timeout login response 60
password xxx
logging synchronous
login
escape-character 27

access-list 14 remark Controlled access via VTY Lines - Inbound
access-list 14 permit 10.252.240.0 0.0.3.255
access-list 14 permit 192.92.77.0 0.0.0.255
access-list 14 permit 192.92.22.0 0.0.0.255
access-list 14 permit 143.159.0.0 0.0.255.255
access-list 14 permit 146.198.0.0 0.1.255.255
access-list 14 permit 165.120.0.0 0.0.255.255
access-list 14 permit 213.31.20.0 0.0.3.255
access-list 14 permit 10.28.91.0 0.0.0.255
access-list 14 permit 10.28.110.0 0.0.0.255
access-list 14 permit 10.252.169.0 0.0.0.31
access-list 14 permit 10.252.169.64 0.0.0.31
access-list 14 permit 192.168.0.0 0.0.255.255
access-list 14 permit 204.231.0.0 0.0.255.255
access-list 14 permit 10.252.168.0 0.0.3.255
access-list 14 permit 10.252.232.0 0.0.3.255
access-list 14 permit 10.252.241.0 0.0.0.255

Thanks for your help,
Max


NMFall 20%
Posted by Thomas Braun on August 11, 2004, 9:58 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Hi,
>
> Follow a cut and paste of the vty line configuration and the
> access-list 14 configuration:
>
> line vty 0 3
> access-class 14 in
> exec-timeout 3 0
> password xxx
> logging synchronous
> no login
remove this, than you can login to all vty's.



> escape-character 27
> line vty 4
> access-class 14 in
> exec-timeout 3 0
> timeout login response 60
> password xxx
> logging synchronous
> login
> escape-character 27
>
> access-list 14 remark Controlled access via VTY Lines - Inbound
> access-list 14 permit 10.252.240.0 0.0.3.255
> access-list 14 permit 192.92.77.0 0.0.0.255
> access-list 14 permit 192.92.22.0 0.0.0.255
> access-list 14 permit 143.159.0.0 0.0.255.255
> access-list 14 permit 146.198.0.0 0.1.255.255
> access-list 14 permit 165.120.0.0 0.0.255.255
> access-list 14 permit 213.31.20.0 0.0.3.255
> access-list 14 permit 10.28.91.0 0.0.0.255
> access-list 14 permit 10.28.110.0 0.0.0.255
> access-list 14 permit 10.252.169.0 0.0.0.31
> access-list 14 permit 10.252.169.64 0.0.0.31
> access-list 14 permit 192.168.0.0 0.0.255.255
> access-list 14 permit 204.231.0.0 0.0.255.255
> access-list 14 permit 10.252.168.0 0.0.3.255
> access-list 14 permit 10.252.232.0 0.0.3.255
> access-list 14 permit 10.252.241.0 0.0.0.255
>
> Thanks for your help,
> Max



Posted by Hansang Bae on August 12, 2004, 3:17 am
If you were  Registered and logged in, you could reply and use other advanced thread options

> > line vty 0 3
> > access-class 14 in
> > exec-timeout 3 0
> > password xxx
> > logging synchronous
> > no login

> remove this, than you can login to all vty's.


Why? That just says a password is not required.


--

hsb

"Somehow I imagined this experience would be more rewarding" Calvin
*************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
********************************************************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************


Similar ThreadsPosted
Looking for Short List of DSL Broadband Aggregators April 7, 2006, 3:09 pm
IPSEC: disconnect after short idle period October 13, 2005, 12:32 am
CISCO 7690 short keys -> part of a number September 1, 2005, 1:47 am
I can't write ACLs June 26, 2008, 7:12 pm
RANCID show run or write net? October 20, 2006, 4:04 pm
How to write on syslog which users access via RAS. January 5, 2006, 11:12 am
How to write on syslog which users access via RAS. January 5, 2006, 11:46 am
FLASH Write Error #5 on Aironet 350 November 20, 2006, 8:12 pm
I require a UK company / Individual to write me a config. - Willing to pay! December 4, 2006, 4:14 am
Typical Read/Write times for a TCAM February 15, 2007, 4:55 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map