Table of Contents
Advertisement
Testing the port
Modem problems
B.4 Server Still
Does Not
Communicate
Kill the port
Power cycling
The first thing to ascertain is that you can talk to the modem.
Check this by telneting to the port and attempting to obtain a
response from the modem. The command sequence is:
telnet elroy 10006 (port 6 on Terminal Server elroy)
If the modem is Hayes compatible, type the AT command
and press the return key. The modem should respond with
OK if the echo settings are correct at the modem. If you are
unable to telnet to the port ensure that the port is set up
correctly and has been killed to save the changes in
configuration. Pay particular attention to flow control,
monitor DSR, monitor DCD, and access field.
Once you have a response from the modem, dial-out to a
known site and check that the correct responses are
returned. Remember that modems can change their bps rate
dynamically having made a connection but the Terminal
Server is unable to do this. Make sure you've configured the
AT string in the Remote Site Devices - Modem Configuration
field. Then kill the port.
A situation may occur which causes the Terminal Server to
completely not function. Here are possible problems:
Try killing the port as it may be locked due to some situation
that is no longer obvious. Also, killing the port ensures that
any changes in the configuration will be acted upon.
Power cycle the device connected (if this is possible) as it
may be that it has locked, or the set-up within the device is
in error. Also try power cycling the Terminal Server itself.
Troubleshooting & Maintenance
123
Advertisement
Table of Contents
