Comtrol SCO OpenServer - Manual (Page 33)

Troubleshooting 33
SCO OpenServer
Modem-Related Error Messages
The following list describes some of the more common error messages
seen while performing the exercises in this manual, and their causes.
For additional assistance, see the “Troubleshooting Modems” section
in the SCO OpenServer Handbook.
Message: Connect failed: SYSTEM NOT IN Systems FILE
Cause: Missing or incorrect entry in /usr/lib/uucp/Devices.
Message: Connect failed: NO DEVICES AVAILABLE
Cause: Missing or incorrect entry in /usr/lib/uucp/Devices.
Message: Connect failed: CAN’T ACCESS DEVICE
Cause: Owner or permissions incorrect on /dev/ttyrXX
Message: Connect failed: DEVICE LOCKED
Cause: There is a lock file on this device.
Message: cu:dir permission denied
Cause: You do not have write permission on the
/usr/lib/uucp/Devices file.
Solving Modem-related Problems
If you have problems connecting to a modem-equipped port,
disconnect the cable to the modem or turn off the modem. Use the cu
command to test a port with no modem present. After connecting to
the port, reconnect or power on the modem and set the modem
parameters.
The most useful tool for diagnosing dial-out problems is the -x9 option
to cu. Using this option causes cu to display diagnostic output. To do so,
follow this syntax:
cu -x9 -l devicename phonenumber
Where devicename is the port you are trying to use and phonenumber
is the number you are trying to dial.
If you get a “connected” message when you test the modem with cu but
no response to an at command, follow these steps:
1. Move the modem to a standard serial port and try it there. If it
works on a standard port but not on a RocketPort port, the problem
lies in the RocketPort board or port configuration.
2. Move the modem back to the RocketPort port.
3. Verify that the modem switch and software settings are correct.
4. Check the modem cable to make sure it is attached at both ends.