pppd debug output contains Connect script failed
|
Your chat
script supplies a user name and ssword.
ogin: user-name
ssword: password
|
However, the peer that you intended to connect to does not
prompt for this information.
|
-
Delete the login and password from the chat script.
-
Try to call the peer again.
-
If you still get the message, call the ISP. Ask the ISP for
the correct login sequence.
|
The /usr/bin/chat -v log contains the
message: "expect (login:)" alarm read timed out
|
Your chat script supplies a user name and ssword.
ogin: pppuser
ssword: \q\U
|
However, the peer that you intend to connect to does not prompt for
this information.
|
-
Delete the login and password from the chat script.
-
Try to call the peer again.
-
If you still get the message, call the ISP. Ask the ISP for
the correct login sequence.
|
pppd debug output
contains possibly looped-back
|
The local machine or its peer is hanging at
the command line and not running PPP. An incorrectly configured login name
and password are in the chat script.
|
-
Delete the login and password from the chat script.
-
Try to call the peer again.
-
If you still get the message, call the ISP. Ask for the correct
login sequence.
|
pppd debug output shows that LCP activates,
but the link terminates soon afterward.
|
The password in the chat script might be incorrect.
|
-
Ensure that you have the correct password for the local machine.
-
Check the password in the chat script. Fix the password
if incorrect.
-
Try to call the peer again.
-
If you still get the message, call the ISP. Ask the ISP for
the correct login sequence.
|
Text from the peer begins with a tilde (~).
|
Your chat script supplies a user name and ssword.
ogin: pppuser
ssword: \q\U
|
However, the peer that you intend to connect to does not prompt
for this information.
|
-
Delete the login and password from the chat script.
-
Try to call the peer again.
-
If you still get the message, call the ISP. Request the correct
login sequence.
|
The modem hangs.
|
Your chat script contains the following line to force
the local machine to wait for the CONNECT message from
the peer:
|
Use the following line when you want the chat script to wait for CONNECT from
the peer:
End the chat script with ~ \c.
|
pppd debug output contains LCP: timeout sending Config-Requests
|
Your chat script contains the following line to force the local machine to
wait for the CONNECT message from the peer:
|
Use the following line when you want
the chat script to wait for CONNECT from the peer:
End the chat script with ~ \c.
|
pppd debug output contains: Serial link is not
8-bit clean
|
Your chat script contains the following line to force the local machine to
wait for the CONNECT message from the peer:
|
Use the following
line when you want the chat script to wait for CONNECT from the peer:
End the chat script with ~ \c.
|
pppd debug output contains: Loopback detected
|
Your chat script contains the following line to force the local machine to
wait for the CONNECT message from the peer:
|
Use the following
line when you want the chat script to wait for CONNECT from the peer:
End the chat script with ~ \c.
|
pppd debug output
contains SIGHUP
|
Your chat script contains the following line to force the local machine to
wait for the CONNECT message from the peer:
|
Use the following
line when you want the chat script to wait for CONNECT from the peer:
End the chat script with ~ \c.
|