TImeout sending Config-Requests !

TImeout sending Config-Requests !

Post by Wayne Bolin » Mon, 30 Nov 1998 04:00:00



Just loaded up RH 5.1 after having formerly been a Slackware user.
Everything works great except one important thing.  PPP dial up to my ISP.
I am only able to connect about 1 out of 20 tries.  The rest of the time I
get the dreaded IPCP:  Timeout sending Config-Requests.  I have searched
Usenet and found this is a very common problem, only difference is with some
people is it LCP instead of IPCP.  Read all the appropriate HOW TO's, looked
at the RH tips on Dial UP and PPP, and tried the various solutions offered
to other posts on usenet.  No luck.  Is there a working solution to this
common problem??  Any help would be GREATLY appreciated.
 
 
 

TImeout sending Config-Requests !

Post by Clifford Ki » Mon, 30 Nov 1998 04:00:00


: Just loaded up RH 5.1 after having formerly been a Slackware user.
: Everything works great except one important thing.  PPP dial up to my ISP.
: I am only able to connect about 1 out of 20 tries.  The rest of the time I
: get the dreaded IPCP:  Timeout sending Config-Requests.  I have searched
: Usenet and found this is a very common problem, only difference is with some
: people is it LCP instead of IPCP.  Read all the appropriate HOW TO's, looked
: at the RH tips on Dial UP and PPP, and tried the various solutions offered
: to other posts on usenet.  No luck.  Is there a working solution to this
: common problem??  Any help would be GREATLY appreciated.

One thing that can cause an IPCP negotiation problem is a poorly
implemented ppp at the ISP with regard to the asyncmap.  Try the pppd
option "asyncmap 0" and if this doesn't work, "asyncmap a0000", and
"asyncmap 20a0000" are other candidates.  Yet another candidate is the
asyncmap the ISP requested for itself, usually in messages found in
/var/log/debug when pppd is used with the "debug" option.

It's also possible, depending on what else is configured for pppd, that
one or both the pppd options "ipcp-accept-local" and "ipcp-accept-remote"
are necessary.  man pppd for details.

--

/* 97.3% of all statistics are made up. */

 
 
 

1. LCP: timeout sending Config-Requests - more info

I am receiveing this error messagecould anyone give me any pointers or a
place
where I can find information on how to solve this problem.
I have checked in pppdocs and can find nothing mentioned about this.

LCP: timeout sending Config-Requests

Connect appears to be made correctly up to the point where
it would go into ppp mode on my side. I am tryn to kppp to connect.

Below are the logs and script files, I am using.

------------------------------------
(Is in the login script debug window, terminal mode)
CONNECT 38400
login: XXXXXX
Password: XXXXXX
 Entering PPP Mode.
 IP address is XXX.XXX.XXX.XXX
 MTU is 1524.

(Is in the PPP-logfile  -minus the system info)
pppd 2.3.7 started by root, uid 0
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS0
LCP: timeout sending Config-Requests
Connection terminated.
Connect time 0.9 minutes.
Exit.

(Is in chat-ppp0)
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDTXXXXXXX'
'CONNECT' ''
'ogin:' 'XXXXXX'
'ord:' 'XXXXXX'
'TIMEOUT' '5'
'~--' ''

2. Checking multiple directories for documents

3. pppd fails with: LCP: timeout sending Config-Requests

4. Problem with setup

5. Rehat 4.0 ppp: "LCP: timeout sending Config-Requests"

6. LINUX FT and NIS

7. IPXCP: timeout sending Config-Requests

8. shutdown already running msg

9. LCP: timeout sending Config-Requests

10. PPP - LCP timeout sending Config-Requests

11. PPP Prob - LCP: timeout sending Config-requests

12. pppd -> LCP: timeout sending Config-Requests ???

13. LCP: timeout sending Config-Requests