|
|
For direct lines you can try the same low-level connection you used to test your modem in the previous procedure. As in the modem testing procedure, you use the modem utility.
Perform the following
The easiest way to test a direct line is to use a dumb terminal (with a dumb terminal, for example, you only need to configure the terminal settings correctly). If you use another UnixWare 7 system to test the line, make sure to use the procedure in this section to set up a bidirectional port on the remote system.
Once you get the connected
message
from the modem utility,
any characters you type should appear
on the terminal screen,
together with any system responses.
If you do not get a connected
message,
then the problem is probably
due to the modem's failure
to receive the Carrier Detect (CD) signal
over the cable
(which is the only thing cu
and the modem utility
look for before returning the connected
message).
All connection types look for Carrier Detect (CD); this is a cable signal that must be high for cu or uucp to continue. In a direct connection, this usually occurs because the other side raises the Data Terminal Ready (DTR) signal. Note that these two signals are swapped in a null modem.
Check your cable, or buy an RS232 mini tester or a breakout box and see that the CD light (on the side right before it goes into your machine) is high. If the cable is all right, then there may be a problem with your hardware.