Testing remote access

Establishing an incoming link to a remote access endpoint requires the following:

• A successful login to the local host from the remote host.

• The startup of a PPP shell on the local host.

  1 Feb 22 17:15:36 127.0.0.1 -ppp[350]: login on '/dev/tty1A'
  2 Feb 22 17:15:36 127.0.0.1 pppd[207]: accept on socket 5
  3 Feb 22 17:15:36 127.0.0.1 -ppp[350]: sent pppd m_type=16, m_pid=350,
  4 m_tty='/dev/tty1A'
  5 Feb 22 17:15:36 127.0.0.1 pppd[207]: pppd_sockread s=6
  6 Feb 22 17:15:36 127.0.0.1 pppd[207]: read m_type=16
  7 Feb 22 17:15:36 127.0.0.1 pppd[207]: Incoming call on '/dev/tty1A',
  8 pid=350, name=nppp
  9 Feb 22 17:15:37 127.0.0.1 pppd[207]: Connecting '/dev/tty1A' under PPP
 10 Feb 22 17:15:37 127.0.0.1 pppd[207]: Assigned link id for incoming
 11 link(login:nppp pid:350) is 80

remote host login

The remote host must perform a successful login to the local host before any PPP activity occurs. To troubleshoot these steps you should see the logging of information at the console.

line 1

The PPP shell (as represented by ``-ppp'') starts and informs the PPP daemon that a PPP login exists on /dev/tty1A.

line 2

The PPP daemon (represented by ``pppd'') acknowledges the login.

lines 3,4

The PPP shell passes additional information to the daemon.

lines 7-11

The PPP daemon acknowledges receipt of an incoming call, connects the tty under the PPP driver, and assigns an ID number to the incoming link.

If the PPP shell starts, it is most likely that the above activities will be successful. At this stage, most incoming link failures occur because the remote host is unable to login to the local host or because the login does not start a PPP shell because of incorrect configuration information. For a description of the required information, see ``Configuring an endpoint for remote access''.

If you find that pppd has successfully assigned a link ID for the PPP link you are troubleshooting, go to ``Troubleshooting PPP negotiation'' to continue troubleshooting.

Home Notes   Home   MCSE   MCSE + Security   CCNA   CCNP   Schedule   Register   Frequently Asked Questions   Course Fees   Contact US   Boot Camp Location   Compare us to our competitors   Testimonials   Sitemap

Testimonials

Join MCSE 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 + CCNA  Training  Card pay  Papal  MCSE 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.