Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Reverse Telnet Problem!

We are using Cisco 2610XM and NM-16A (16 Port Aysnchronous Module) and 2 sets of 8 lead ocatl cables to make a terminal server. This is going to be used for reverse telnet purpose.

The configuration file is as follows:

TerminalSrvr#show run

Building configuration...

Current configuration : 931 bytes

!

version 12.2

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname TerminalSrvr

!

logging queue-limit 100

no logging console

enable secret xxxx

enable password xxxx

!

username xxx privilege 15 password xxxx

ip subnet-zero

no ip routing

!

!

ip host test1 2001 10.10.10.10

!

!

!

!

!

interface Loopback1

ip address 10.10.10.10 255.255.255.0

!

interface FastEthernet0/0

ip address 192.168.1.1 255.255.255.0

no ip route-cache

no ip mroute-cache

speed 100

full-duplex

no cdp enable

!

ip http server

ip classless

!

!

!

!

line con 0

exec-timeout 0 0

line 33 40

exec-timeout 0 0

password cisco

flush-at-activation

login local

no exec

transport input all

flowcontrol hardware

line 41 48

exec-timeout 0 0

password cisco

flush-at-activation

no exec

transport input all

line aux 0

line vty 0 4

password cisco

login

!

!

end

When I try to telnet to the console port of a Cisco Switch attached asynch module, i recieve:

TerminalSrvr#telnet 10.10.10.10 2001

Trying 10.10.10.10, 2001 ...

% Connection refused by remote host

Any idea?

3 REPLIES
VIP Purple

Re: Reverse Telnet Problem!

Hello,

can you issue the command:

show line

and check if there might be noise on your line ?

If you see noise, according to a previous post, the noise on the console could be caused by a number of things bad cable, emi, you can try toggling the flow control between software and hardware to see if this clears up the noise issue, one additional thought , I have had instances when there is noise on a console line that the router beleives that this noise is an exec request and opens up an exec session, so perhaps this noise is creating a session on the console and this is why you can not access it on your first try, removing the cable clears the session allowing you to connect after this.

Also, you could try to configure the command "no exec" under your line configuration on your Access Server. It could prevent unwanted signals from the the line initiating exec sessions and keeping the line unavailable for genuine ones.

And last but not least, I see that you have configured lines 33 thru 48, while you are trying to connect to a host on line 1. Just make sure that your host is actually connected to port 1, otherwise change the statement:

ip host test1 2001 10.10.10.10

to

ip host test1 2033 10.10.10.10

Then again I might be way off here...

Regards,

Georg

Silver

Re: Reverse Telnet Problem!

Anonymous
N/A

Re: Reverse Telnet Problem!

It looks like you're telneting to the wrong port. Above, you are going to port 2001. I noticed in your config that your port numbers start with 2033. Line 33 40, means ports 2033-2040. Line 41 48 means 2041-2048 So, telnet to 10.10.10.10 2033, and it should work. I hope this helps!

224
Views
5
Helpful
3
Replies
CreatePlease to create content