Information Technology Reference
In-Depth Information
Table17-1
Modem Cannot Send or Receive Data (continued)
Possible Causes
Suggested Actions
dialer map
commands are
misconfigured
(continued)
•
dial-string
—The remote site's phone number. Any access
codes (for example, 9 to get out of an office; international
dialing codes; and area codes) must be included.
3.
Make sure that
dialer map
commands specify the correct
next-hop addresses.
4.
If the next-hop address is incorrect, change it using the
dialer map
command.
5.
Make sure that all other options in
dialer map
commands
are correctly specified for the protocol that you are using.
For detailed information on configuring dialer maps, refer to the
Cisco IOS
Wide-Area Networking Configuration Guide
and
Wide-Area Networking Command Reference
.
A problem has
occurred with the
dialing modem
Make sure that the dialing modem is operational and is securely
connected to the correct port. See whether another modem works
when connected to the same port.
Debugging an incoming exec session generally falls into a few main categories. Possible causes and
suggested actions can be found in Tables 17-2 through 17-5.
Dialup client receives no exec prompt
•
Dialup session sees “garbage”
•
Dialup session ends up in an existing session
•
Dialup receiving modem does not disconnect properly
•
Table17-2
Dialup Client Receives No exec Prompt
Possible Causes
Suggested Actions
Autoselect is
enabled on the
line
Attempt to access exec mode by issuing a carriage return.
Line is
configured with
the
no exec
command
1.
Use the
show line
exec command to view the status of the
appropriate line.
Check the Capabilities field to see whether it include “exec
suppressed.” If this is the case, the
no exec
line configuration
command is enabled.
2.
Configure the
exec
line configuration command on the line to
allow exec sessions to be initiated. This command has no
arguments or keywords.
Example:
The following example turns on the exec on line 7:
line 7
exec
