Troubleshooting dynamic outgoing SLIP links

To troubleshoot a dynamic outgoing SLIP link:

1. Verify that the local host can establish a UUCP connection to the remote host without SLIP. Dynamic outgoing SLIP links use UUCP to establish a physical connection with the remote host. (For more information, see ``Configuring UUCP for dynamic outgoing links''.)

   
   a.

   Enable getty at the remote host by executing the following command there:
   
   enable tty_number

   
   b.

   Use the cu(C) command to try to connect to the remote system. For example, for a SLIP connection on tty1A running at 1200 baud and calling a modem at extension 5555, enter the following command on the local machine:
   
   cu -ltty1A -s1200 5555

   The modem should dial, connect, and present a login prompt. If you do not see a login prompt after many seconds, type ~%B to make sure that the remote modem did not accidentally cycle past the correct baud rate. Try ~%B three times, waiting several seconds in between each try.

   
   c.

   If you still do not get a login prompt, make sure that the entries in your Devices file are correct, and that the remote tty setup is correct.

   
   d.

   Enter the following command on the local machine:
   
   cu remote_hostname

   You should get the same results as when you specify the extension number. If not, make sure that your /usr/lib/uucp/Systems file includes an entry for the remote_hostname.

   
   e.

   If you are still unable to establish a UUCP link, see ``Connecting to other computers with UUCP''.

   
   

2. Retry the slattach command with the +v flag in addition to your other parameters. This turns on verbose mode, which causes slattach to display at the console the UUCP chat script execution. Using this, you will be able to detect if problems are occurring with the UUCP connection.

3. If you have still not located the source of the problem, see ``Using ping to troubleshoot SLIP link problems''.