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

Discussion in 'Linux Networking' started by Marc, Sep 16, 2003.

  1. Marc

    Marc Guest

    Hi,


    I'm trying to set up a DSL connection in my linux (suse 7.1, kernel
    2.4.28, ISP:Bluewin.ch) with a speedtouch usb modem.

    My problem is when I try:

    "pppd call adsl &" which is suppose to start my DSL connection I've
    got the following message: "LCP: timeout sending Config-Requests"

    What the hell is that and how do I fix it???

    Here is a snap shot of the logs...

    Sep 16 23:03:39 localhost pppd[4351]: pppd 2.4.1 started by root, uid
    0
    Sep 16 23:03:39 localhost pppoa2[4352]: Starting PPPoA2 ( merged
    version
    includes new ATM/AAL5 stack ) 1_0
    Sep 16 23:03:39 localhost pppoa2[4352]: I'm the parent process, I
    handle
    the endpoint 0x07
    Sep 16 23:03:39 localhost pppoa2[4356]: I'm the children process, I
    handle
    the endpoint 0x87
    Sep 16 23:03:39 localhost pppd[4351]: Using interface ppp0
    Sep 16 23:03:39 localhost pppd[4351]: Connect: ppp0 <--> /dev/pts/0
    Sep 16 23:04:10 localhost pppd[4351]: LCP: timeout sending
    Config-Requests
    Sep 16 23:04:10 localhost pppd[4351]: Connection terminated.
    Sep 16 23:04:10 localhost pppd[4351]: Using interface ppp0
    Sep 16 23:04:10 localhost pppd[4351]: Connect: ppp0 <--> /dev/pts/1
    Sep 16 23:04:10 localhost pppoa2[4379]: Starting PPPoA2 ( merged
    version
    includes new ATM/AAL5 stack ) 1_0
    Sep 16 23:04:10 localhost pppoa2[4379]: I'm the parent process, I
    handle
    the endpoint 0x07
    Sep 16 23:04:10 localhost pppoa2[4379]: pusb_claim_interface 1 failed
    Sep 16 23:04:10 localhost pppd[4351]: Modem hangup
    Sep 16 23:04:10 localhost pppd[4351]: Connection terminated.
    .... [more of the same] ...
     
    Marc, Sep 16, 2003
    #1
    1. Advertisements

  2. No one is answering from the remote side.

    Make sure that your provider really uses PPPoA (and not PPPoE).

    If it is PPPoA then check whether you have configured the
    correct VPI/VCI in the modem (if this is possible). If you
    can configure the encapsulation on the VC, check that it is
    also correct (VC mux'ed or LLC/SNAP encapsulated) according
    to the ISPs requirements.

    Check also whether your DSL connection is operational (normally
    a green LED should indicate this on the modem).


    BTW: Don't multi-post use cross-posting instead.

    Ciao, Horst
     
    Horst Knobloch, Sep 16, 2003
    #2
    1. Advertisements

  3. Marc

    Paul D Guest

    Marc

    If Horst's suggestions don't work (ie you have tried the exact settins that
    your ISP suggested) change just VCMux to LLC and see if that helps.
    I know a few people who have DLink modems that have been working fine for
    months using VCMux. Then one day they cannot connect. Changing to LLC
    fixed the problem.
    Neither BT or the ISPs will claim responsibility, but I believe BT are at
    fault

    P
     
    Paul D, Sep 19, 2003
    #3
  4. Marc

    Paul D Guest

    Marc
    Could you tell us what you found, and if/how you resolved your problem?

    Many thanks
    Paul
     
    Paul D, Sep 23, 2003
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.