"LCP: timeout sending Config-Requests" --- whose fault?

"LCP: timeout sending Config-Requests" --- whose fault?

Post by Joel M. Hoffm » Thu, 21 Dec 1995 04:00:00



More often than not, I get the following when trying to establish a
PPP connection:

         LCP: timeout sending Config-Requests

Is this a problem on my end or the ISP's end?

Thanks.

-Joel

--
-----------------------------------------------------------------------------
|_|~~ Germany, Europe. 1940's ``A DISTINGUISHED speaker said that we must put
__|~| 16 Million DEAD.          our children first.   We in Bosnia wonder  if
                                we have any children left. Seven* thousand
 cnc  Bosnia, Europe. 1990's    children  have been killed  in Bosnia in  the
 cnc  HOW MANY MORE?            last three  years.   Those living, some  with
                                gray hair and eyes and hearts of old men, are
``May the world you             hardly children any more.''
  live in be the world                             - H. Silajdzic
  of your dreams.'' - Debbie Friedman                Prime Minister of Bosnia
-----------------------------------------------------------------------------

 
 
 

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

I'm recently done a fresh install of Redhat 4.0 and am try to
configure ppp to dial my ISP.  I've read posts regarding this error
that point to the ISP as the cause, but there are users on my provider
successfully connecting with pppd under Redhat (I've asked them but
haven't found my answer).  Anyways, It seems like I'm sending my
username/password successfully, but I'm getting a "timeout sending
Config-Requests" error on completion of my script.  

Anyone seen a similar error or have any advice on how to successfully
connect?

Thanks,
Pat Dalzell

My /etc/ppp/options -
connect /etc/ppp/chat
/dev/cua2
bsdcomp 9,15
mru 296
crtscts
defaultroute
lock
modem
noipdefault
passive

/etc/ppp/chat -
#!/bin/sh
NUM=1111111
USER=patd
PASS=password
/usr/sbin/chat -v "" ATDT$NUM ortmaster "" ogin: $USER word: $PASS
180

Expecting "ortmaster" is strange, but it seems to be the only way I
can get to the authentification step without an alarm.  Also waiting
for the 180 outputs the "Packet mode enabled" line in
/var/log/messages - this *seems* to be a good thing and I hoped it
would make good evidence without interfering with the logon process.
I get the same error without waiting for it.

Anyhoo, here's the result from /var/log/messages -
Dec  8 19:07:56 patd pppd[857]: pppd 2.2.0 started by root, uid 0
Dec  8 19:07:58 patd chat[859]: send (ATDT6541350^M)
Dec  8 19:07:58 patd chat[859]: expect (ortmaster)
Dec  8 19:08:36 patd chat[859]: ATDT6541350^MLivingston Portmaster --
got it
Dec  8 19:08:36 patd chat[859]: send (^M)
Dec  8 19:08:36 patd chat[859]: expect (ogin:)
Dec  8 19:08:36 patd chat[859]:  v3.1.4^M
Dec  8 19:08:36 patd chat[859]: ^M
Dec  8 19:08:45 patd kernel: PPP: ppp line discipline successfully
unregistered
Dec  8 19:08:56 patd chat[859]: pm-atl-19b (s4) login: -- got it
Dec  8 19:08:56 patd chat[859]: send (patd^M)
Dec  8 19:08:57 patd chat[859]: expect (word:)
Dec  8 19:08:57 patd chat[859]:  ^M
Dec  8 19:09:16 patd chat[859]: pm-atl-19b (s4) login: patd^M
Dec  8 19:09:16 patd chat[859]: Password: -- got it
Dec  8 19:09:16 patd chat[859]: send (password^M)
Dec  8 19:09:17 patd chat[859]: expect (180)
Dec  8 19:09:36 patd chat[859]:  ^M
Dec  8 19:09:56 patd chat[859]: Packet mode enabled: PPP session from
(204.180 -- got it
Dec  8 19:09:56 patd pppd[857]: Serial connection established.
Dec  8 19:09:58 patd kernel: CSLIP: code copyright 1989 Regents of the
University of California
Dec  8 19:09:58 patd kernel: PPP: version 2.2.0 (dynamic channel
allocation)
Dec  8 19:09:58 patd kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc..
Dec  8 19:09:58 patd kernel: PPP line discipline registered.
Dec  8 19:09:58 patd kernel: registered device ppp0
Dec  8 19:09:58 patd pppd[857]: Using interface ppp0
Dec  8 19:09:58 patd pppd[857]: Connect: ppp0 <--> /dev/cua2
Dec  8 19:10:28 patd pppd[857]: LCP: timeout sending Config-Requests

2. "piping" file descriptors to memory

3. ppp fails "LCP: timeout sending Config-Requests"

4. Port Translation with 2.2 Kernel

5. "LCP: timeout sending Config-Requests" w/ pppd 2.1 p2

6. 2.0.x masq bug

7. PPPD Dial-In, FreeBSD 4.3, "LCP: timeout sending Config-Requests".

8. A Linux Users Manual

9. pppd dial ins and , "LCP: timeout sending Config-Requests"

10. "LCP: timeout sending Config-Requests" Problem????

11. pppd: "LCP: timeout sending Config-Requests"

12. PPPD says: "LCP: timeout sending Config-Requests"

13. (GNOME dialer) "timeout sending Config-Requests" - how to correct?