Testing automatic dialup connectivity

Verify host-to-host connectivity on the link as follows:

1. Turn on the PPP driver, PPP daemon, and UUCP logging. See ``Logging PPP information''.

2. Execute the following command:
   
   ping remote_host_IP_address

   ping send: Network is unreachable

Another possible message is:

   ping send: No route to host

If ping hangs with no response, make sure that the IP address is really that of the remote machine. If the IP address appears to be correct, look in the logfile where the PPP driver and PPP daemon log information has been collected. By default, this file is /usr/adm/syslog. The following example logfile and the description below the example show the steps PPP uses to achieve host-to-host connectivity. You can view the logfile to see if these steps have been successful.

  1 Mar 14 09:40:40 pppd[396]: ppp_add_inf: 132.147.246.6 --> 132.147.246.7
  2 Mar 14 09:44:27 pppd[396]: accept on socket 6
  3 Mar 14 09:44:27 pppd[409]: dial process sent pppd m_type=18, m_pid=409,
  4 m_tty='/dev/tty1A'
  5 Mar 14 09:44:27 pppd[396]: pppd_sockread s=7
  6 Mar 14 09:44:27 pppd[396]: Connected to remote system: tty=/dev/tty1A,
  7 pid=409,addr=132.147.54.54
  8 Mar 14 09:44:27 pppd[396]: ppp_add_conn
  9 Mar 14 09:44:27 pppd[396]: Assigned link id for outgoing link (132.147.
 10 246.6->132.147.246.7) is 1

line 1

The PPP daemon (shown as ``pppd'' in the logfile) builds the PPP network interface for the link.

UUCP connection made

Not shown in this logfile is pppd's contacting of the UUCP facility to request a UUCP connection. This information is logged at the local host console.

If the modem does not connect, check the /etc/ppphosts file to verify that the uucp parameter has the correct value for the remote host and that the value has an entry in the /usr/lib/uucp/Systems file. Verify that the entries in the /usr/lib/uucp/Devices and /usr/lib/uucp/Dialers files are correct for supporting the Systems file entry.

If the modem does connect but then disconnects, you can also use the UUCP error codes and PPP debugging information to troubleshoot this problem. For example, if the UUCP error code says something like chat script failed, you can view the chat script dialogue between the local and remote hosts at the console.

If you find that the modem connects but then disconnects after a short time, the problem probably lies with the PPP link parameter negotiation. To debug this type of problem, see ``Troubleshooting PPP negotiation''.

lines 3,4

If the UUCP facility successfully connects with the remote host, pppd receives this information along with the tty of the connection.

lines 6,7

pppd links the tty of that connection under the PPP driver.

lines 9-10

The PPP daemon assigns an ID number (1) to the outgoing link.

If ping is successful when using the IP address of the remote host, you may wish to test whether one can reach the remote host using the host names by which it should be reachable. See ``Using ping to test reachability using host names'' for the command, possible error message, and resolutions.

Home Notes Home MCSE MCSE MCITP + Security CCNA MCITP 2008  Boot Camp Schedule Register Frequently Asked Questions Course Fees Contact US Boot Camp Location Compare us to our competitors Testimonials Sitemap   Testimonials  Join MCSE MCITP Boot Camp & CCNA Boot Camp Back to Back Certification Today. links  270  290    291  293    294  298  299   Security  640-801  routing 811  821   831  Resources MCSE MCITP + CCNA  Training  Card pay  Papal  MCSE MCITP Notes  CCNA Notes    index main   root   link  resources home    Ref1 Ref2

Vibrant offers MCSE certification training boot camp for $5400 all inclusive, instructor led at California and Baltimore.

Vibrant Bootcamp Participants come from All Around the World. Vibrant has trained students from more than 15 countries like USA, UK, (Scotland, Ireland, Wales), Switzerland, Germany, Australia, Canada, France, Holland, Japan, Belgium, Bahrain, New Zealand, Tanzania, Turkey, Kenya and more.