This document can help you troubleshoot a Cisco LocalDirector that does
not accept Telnet connections.
There are no specific requirements for this document.
The information in this document is based on the following software and
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
For more information on document conventions, refer to the
Cisco Technical Tips
LocalDirector must have an IP address assigned to it.
Go into configuration mode.
localdirector# configure terminal
Assign an IP address to the LocalDirector.
localdirector(config)# ip address 10.1.1.1 255.255.255.0
Specify the default gateway or route for the LocalDirector to
ensure a return path to the Telnet client.
localdirector(config)# route 0.0.0.0 0.0.0.0 10.1.1.250
Identify which clients can make a Telnet connection into the
The following example shows how to allow Telnet access to the
LocalDirector for the
network, the 192.168.x.x network, and
the 172.17.63.2 client.
localdirector(config)# telnet 10.0.0.0 255.0.0.0
localdirector(config)# telnet 192.168.0.0 255.255.0.0
localdirector(config)# telnet 172.17.63.2 255.255.255.255
Assign LocalDirector a Telnet password.
localdirector(config)# password *******
Note: The enable password will not allow you to make a Telnet
connection into the LocalDirector. The LocalDirector allows only the standard
password to initiate a Telnet connection.
If you cannot connect via Telnet after you have configured
LocalDirector, try the following tests:
Ping the Telnet client from LocalDirector.
If the ping is successful, go to Step 2. If not, verify that the
routing statement on the LocalDirector is correct and check that you can ping
the default gateway from the LocalDirector. Issue the show
arp command and check that the LocalDirector has an ARP entry for
the default gateway.
Issue the who command in LocalDirector
to verify that no more than three users are logged in.
LocalDirector allows four users to Telnet in at one time.
If you complete Steps 1 and 2 and you still cannot achieve Telnet
access to the LocalDirector, check if a firewall or a device is preventing
Telnet (Port 23) traffic to the LocalDirector.
If you can reach the LocalDirector but your password is refused,
verify that you are using the non-enabled password.
Please note the two following caveats.
(registered customers only)
After five unanswered syn to LocalDirector, you can no longer
use Telnet to access LocalDirector.
(registered customers only)
LocalDirector stops accepting Telnet and dumps when commands
are issued through the console.