|
|
You can see all of the steps described in the procedure in the previous section using the connection server cs in debug mode, as described in ``Using the connection server in debug mode''.
If you are able to talk to your modem using the troubleshooting procedures in ``Testing basic modem connectivity'' or ``Testing basic direct line connectivity'', but cu or uucp is still not working, put cs into debug mode and observe the cs log.
You can see symptoms of many things that can go wrong in the cs log. For example, the cs log reports basic problems such as an incorrect modem type, speed mismatches between the remote and local modems or lines, similar mismatches in character size, parity, and line speed settings. For uucp only, the cs log reports an incorrect login sequence.
For more information on these types of problems, see ``Speed, character size and parity settings'' and ``Using expect/send strings to troubleshoot uucp''. Also see ``Known problems and workarounds'' for additional help in identifying problems in the cs debug output.