The following errors are related to log output from the procedure, How to Diagnose and Fix Communications Problems. Some of the errors show actual error output, and some are symptom descriptions.
too many Configure-Requests
Cause: One peer cannot hear the other peer.
Solution: Check for the following problems:
The system or modem might have faulty cabling.
The modem configuration might have incorrect bit settings. Or, the configuration might have broken flow control.
The chat script might have failed. In this situation, see Common Chat Script Problems.
IPCP starts but terminates immediately
Cause: IP addresses are likely configured incorrectly.
Solution: Check the chat script to verify whether the script has incorrect IP addresses. If the chat script is correct, request debug logs for the peer, and check IP addresses in the peer logs.
LCP starts, but higher-level protocols fail or show CRC errors
Cause: The asynchronous control character map (ACCM) is incorrectly set.
Solution: Use the default-async option to set the ACCM to the standard default of FFFFFFFF. First, try to use default-async as an option to pppd on the command line. If the problem clears, then add default-async to /etc/ppp/options or to /etc/ppp/peers/peer-name after the call option.
Link exhibits very poor performance
Cause: IThe modem might be incorrectly configured, with flow-control configuration errors, modem setup errors, and incorrectly configured DTE rates.
Solution: Check the modem configuration. Adjust the configuration if necessary.