48
11.4 RARP Troubleshooting
11.5 Modem Configuration Checklist
Most modem problems are caused by cabling mistakes or incorrect modem configuration.
However, the following items should be verified after any modem configuration, and
rechecked when there is modem trouble.
The modem must disconnect immediately when DTR is de-asserted.
The modem must assert CD (or DSR, if connected) when connected to another mo-
dem. It must not assert CD when disconnected. The modem may optionally assert
CD during outbound dialing.
The modem and Terminal Server must agree on the flow control method and baud
rate scheme.
The modem must not send result codes or messages to the Terminal Server except
optionally during outgoing calls.
The modem should be set to restore its configuration from non-volatile memory
when DTR is dropped.
The modem should be configured to answer the phone if incoming connections are
to be supported. Generally this is done with the
ats0=1
command.
The modem should not be configured to answer the phone unless the Terminal Serv-
er asserts DTR.
Table 11-4:
RARP Troubleshooting
Area to Check
Explanation
The Terminal Server name and hard-
ware address in the host’s
/etc/ethers
file
The Terminal Server name and hardware address
must be in this file for the host to answer a RARP
request.
The Terminal Server name and IP
address in the
/etc/hosts
file
The Terminal Server name and IP address must be in
this file for the host to answer a RARP request.
The operating system
Many operating systems do not start a RARP server
at boot time. Check the host’s RARPD documenta-
tion for details, or use the
ps
command to see if there
is a RARPD process running.
Summary of Contents for 16-Port Rackmount 10/100
Page 90: ......
