Scenario 2: Authentication Time OutsPart II

An end user calls up and states that the connection hangs during the verifying username and password stage of the connection. This time, the problem seems to be widespread. Again, the command # debug ppp negotiation is used to log the connection while the client tries to dial in. After debugging, you see the LCP information in Example 8-3 repeat itself.

Example 8-3. Output from debug ppp negotiation for Authentication Time OutsPart II

  Mar 2 19:58:19.768: As1 LCP: O CONFREQ [REQsent] id 74 len 25  Mar 2 19:58:19.768: As1 LCP: ACCM 0x000A0000 (0x0206000A0000) Mar 2 19:58:19.768: As1 LCP: AuthProto PAP (0x0304C023) Mar 2 19:58:19.768: As1 LCP: MagicNumber 0x5779D9D2 (0x05065779D9D2) Mar 2 19:58:19.768: As1 LCP: PFC (0x0702) Mar 2 19:58:19.768: As1 LCP: ACFC (0x0802)  Mar 2 19:58:21.768: As1 LCP: TIMEout: State REQsent  

The debug output in Example 8-3 happens every two seconds until the modems disconnect. If you review the output carefully , the only event that occurs is outgoing LCP packetsO CONFREQ. This type of problem usually occurs because of a speed mismatch between a router and a modem, which is why the problem seems so widespread. Any user connecting to this modem would have the same problem. This should occur only when there is an external modem attached to the router.

The fix involves verifying whether the speed is set the same on both the modem and the router. In this case, the modem is configured with a line speed of 15200 instead of 115200. It is fixed by issuing the line configuration command speed 115200 on the client modem.