Filter
Top Products
Chapter 1 FAQs and Troubleshooting
General FAQs and Troubleshooting
1-10
FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine
Symptom Cannot connect to system with Telnet or Telnet interaction is slow.
Possible Cause
–
Telnet is disabled or configured incorrectly.
–
The WLSE cannot recognize host names.
If you are not using name recognition, slow or non-existent telnet
interaction is an expected problem.
Note Telnet is disabled by default. SSH is enabled by default.
Recommended Action
If the problem is not the network, perform the following steps. Connect to the
console port if you cannot Telnet to the WLSE.
1. Check the Telnet settings to be sure Telnet is enabled and configured
correctly. For more information, see the following
To check the Telnet settings, or to enable or disable Telnet on specific
domains or IP addresses, use the telnetenable CLI command. For more
information on this command, see the User Guide for the CiscoWorks
Wireless LAN Solution Engine, Release 2.5. You can access a PDF
version of this guide by clicking View PDF in the WLSE’s online help
To enable or disable Telnet on individual ports, use the firewall CLI
command. For more information on this command, see the User Guide
for the CiscoWorks Wireless LAN Solution Engine, Release 2.5. You can
access a PDF version of this guide by clicking View PDF in the WLSE’s
online help
2. If you have specified hosts using the telnetenable CLI command, make
sure the host from which you are attempting to Telnet is on the list.
3. If you are using a DNS server, perform the following step:
Configure the system to use a functioning DNS server by entering:
# ip name-server
ip-address
where ip-address is the IP address of the DNS server.
If you are using the import CLI command, proceed to the next step.