Chat scripts are trouble-prone areas for dial-up links. The following is list of common chat script errors, descriptions, and solutions. For procedural information, refer to How to Obtain Debugging Information for Chat Scripts.
pppd debug output contains Connect script failed
Cause: Your chat script supplies a user name and password.
ogin: user-name ssword: passwordHowever, the peer that you intended to connect to does not prompt for this information.
Solution: Delete the login and password from the chat script, then try to call the peer again. If you still get the message, call the ISP to get the correct login sequence.
The /usr/bin/chat -v log contains "expect (login:)" alarm read timed out
Cause: Your chat script supplies a user name and password.
ogin: pppuser ssword: \q\UHowever, the peer that you intend to connect to does not prompt for this information.
Solution: Delete the login and password from the chat script and try to call the peer again. If you still get the message, call the ISP to get the correct login sequence.
pppd debug output contains "possibly looped-back"
Cause: The local system 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.
Solution: Delete the login and password from the chat script and try to call the peer again. If you still get the message, call the ISP to get the correct login sequence.
pppd debug output shows that LCP activates, but the link terminates soon afterward.
Cause: The password in the chat script might be incorrect.
Solution: Ensure that you have the correct password for the local system. Then,
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 (~).
Cause: Your chat script supplies a user name and password.
ogin: pppuser ssword: \q\UHowever, the peer that you intend to connect to does not prompt for this information.
Solution: Delete the login and password from the chat script and try to call the peer again. If you still get the message, call the ISP to get the correct login sequence.
The modem hangs.
Cause: Your chat script contains the following line to force the local system to wait for the CONNECT message from the peer:
CONNECT "
Solution: Use the following line when you want the chat script to wait for CONNECT from the peer:
CONNECT \cEnd the chat script with ~ \c.
pppd debug output contains "LCP: timeout sending Config-Requests"
Cause: Your chat script contains the following line to force the local system to wait for the CONNECT message from the peer:
CONNECT "
Solution: Use the following line when you want the chat script to wait for CONNECT from the peer:
CONNECT \cEnd the chat script with ~ \c.
pppd debug output contains "Loopback detected"
Cause: Your chat script contains the following line to force the local system to wait for the CONNECT message from the peer:
CONNECT "
Solution: Use the following line when you want the chat script to wait for CONNECT from the peer:
CONNECT \cEnd the chat script with ~ \c.
pppd debug output contains "Serial link is not 8-bit clean"
Cause: Your chat script contains the following line to force the local system to wait for the CONNECT message from the peer:
CONNECT "
Solution: Use the following line when you want the chat script to wait for CONNECT from the peer:
CONNECT \cEnd the chat script with ~ \c.
pppd debug output contains SIGHUP
Cause: Your chat script contains the following line to force the local system to wait for the CONNECT message from the peer:
CONNECT "
Solution: Use the following line when you want the chat script to wait for CONNECT from the peer:
CONNECT \cEnd the chat script with ~ \c.