Re: Linux pppd fails to connect.to Windows2000. - PPP

This is a discussion on Re: Linux pppd fails to connect.to Windows2000. - PPP ; OK, So I have managed to get my employers to remove the compression. I now get the following log in /var/log/messages. Again you can see that CHAP authentication has succeeded but it fails again in the protocol/compression negotiations. Am I ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: Linux pppd fails to connect.to Windows2000.

  1. Re: Linux pppd fails to connect.to Windows2000.

    OK, So I have managed to get my employers to remove the compression.

    I now get the following log in /var/log/messages.
    Again you can see that CHAP authentication has succeeded but it fails
    again in the protocol/compression negotiations.

    Am I still screwed by Microsoft MS-PPC patents?

    Jul 7 23:08:10 localhost pppd[2031]: pppd 2.4.1 started by root, uid 0
    Jul 7 23:08:10 localhost pppd[2031]: pppd 2.4.1 started by root, uid 0
    Jul 7 23:08:11 localhost chat[2032]: abort on (NO CARRIER)
    Jul 7 23:08:11 localhost chat[2032]: abort on (NO DIALTONE)
    Jul 7 23:08:11 localhost chat[2032]: abort on (ERROR)
    Jul 7 23:08:11 localhost chat[2032]: abort on (NO ANSWER)
    Jul 7 23:08:11 localhost chat[2032]: abort on (BUSY)
    Jul 7 23:08:11 localhost chat[2032]: report (CONNECT)
    Jul 7 23:08:11 localhost chat[2032]: send (AT&F^M)
    Jul 7 23:08:11 localhost chat[2032]: expect (OK)
    Jul 7 23:08:11 localhost chat[2032]: AT&F^M^M
    Jul 7 23:08:11 localhost chat[2032]: OK
    Jul 7 23:08:11 localhost chat[2032]: -- got it
    Jul 7 23:08:11 localhost chat[2032]: send (ATS0=2DTPHONENUMBER^M)
    Jul 7 23:08:12 localhost chat[2032]: expect (CONNECT)
    Jul 7 23:08:12 localhost chat[2032]: ^M
    Jul 7 23:08:43 localhost chat[2032]: ATS0=2DTPHONENUMBER^M^M
    Jul 7 23:08:43 localhost chat[2032]: CONNECT
    Jul 7 23:08:43 localhost chat[2032]: -- got it
    Jul 7 23:08:43 localhost chat[2032]: send (CLIENT^M)
    Jul 7 23:08:43 localhost pppd[2031]: Serial connection established.
    Jul 7 23:08:43 localhost pppd[2031]: Serial connection established.
    Jul 7 23:08:43 localhost pppd[2031]: using channel 7
    Jul 7 23:08:43 localhost pppd[2031]: Using interface ppp0
    Jul 7 23:08:43 localhost pppd[2031]: Using interface ppp0
    Jul 7 23:08:43 localhost pppd[2031]: Connect: ppp0 <--> /dev/modem
    Jul 7 23:08:43 localhost pppd[2031]: Connect: ppp0 <--> /dev/modem
    Jul 7 23:08:44 localhost pppd[2031]: sent [LCP ConfReq id=0x1 ]
    Jul 7 23:08:44 localhost pppd[2031]: rcvd [LCP ConfReq id=0x0 < 17 04 01 a9>]
    Jul 7 23:08:44 localhost pppd[2031]: sent [LCP ConfRej id=0x0 < 17 04 01 a9>]
    Jul 7 23:08:44 localhost pppd[2031]: rcvd [LCP ConfAck id=0x1 ]
    Jul 7 23:08:44 localhost pppd[2031]: rcvd [LCP ConfReq id=0x1 ]
    Jul 7 23:08:44 localhost pppd[2031]: sent [LCP ConfNak id=0x1 ]
    Jul 7 23:08:44 localhost pppd[2031]: rcvd [LCP ConfReq id=0x2 ]
    Jul 7 23:08:44 localhost pppd[2031]: sent [LCP ConfAck id=0x2 ]
    Jul 7 23:08:44 localhost pppd[2031]: rcvd [CHAP Challenge id=0x0 , name = "MachineName"]
    Jul 7 23:08:44 localhost pppd[2031]: sent [CHAP Response id=0x0 <00000000000000000000000000000000000000000000000010 8662582889ee4cea605e8184678b60dbe270bf7b2b6dfe01>, name = "myloginname"]
    Jul 7 23:08:45 localhost pppd[2031]: rcvd [CHAP Success id=0x0 ""]
    Jul 7 23:08:45 localhost pppd[2031]: sent [IPCP ConfReq id=0x1 ]
    Jul 7 23:08:45 localhost pppd[2031]: sent [CCP ConfReq id=0x1 ]
    Jul 7 23:08:45 localhost pppd[2031]: rcvd [CCP ConfReq id=0x4 < 12 06 00 00 00 f0>]
    Jul 7 23:08:45 localhost pppd[2031]: sent [CCP ConfRej id=0x4 < 12 06 00 00 00 f0>]
    Jul 7 23:08:45 localhost pppd[2031]: rcvd [IPCP ConfReq id=0x5 ]
    Jul 7 23:08:45 localhost pppd[2031]: sent [IPCP ConfAck id=0x5 ]
    Jul 7 23:08:45 localhost pppd[2031]: rcvd [IPCP ConfNak id=0x1 ]
    Jul 7 23:08:45 localhost pppd[2031]: sent [IPCP ConfReq id=0x2 ]
    Jul 7 23:08:45 localhost pppd[2031]: rcvd [CCP ConfRej id=0x1 ]
    Jul 7 23:08:45 localhost pppd[2031]: sent [CCP ConfReq id=0x2]
    Jul 7 23:08:45 localhost pppd[2031]: rcvd [LCP TermReq id=0x6 "Y.e\37777777740\000<\37777777715t\000\000\002\37777777746"]
    Jul 7 23:08:45 localhost pppd[2031]: LCP terminated by peer (Y.eM-`^@ Jul 7 23:08:45 localhost pppd[2031]: LCP terminated by peer (Y.eM-`^@ Jul 7 23:08:45 localhost pppd[2031]: sent [LCP TermAck id=0x6]
    Jul 7 23:08:46 localhost pppd[2031]: Hangup (SIGHUP)
    Jul 7 23:08:46 localhost pppd[2031]: Hangup (SIGHUP)
    Jul 7 23:08:46 localhost pppd[2031]: Modem hangup
    Jul 7 23:08:46 localhost pppd[2031]: Modem hangup
    Jul 7 23:08:46 localhost pppd[2031]: Connection terminated.
    Jul 7 23:08:46 localhost pppd[2031]: Connection terminated.
    Jul 7 23:08:47 localhost pppd[2031]: Exit.
    Jul 7 23:08:47 localhost pppd[2031]: Exit.

  2. Re: Linux pppd fails to connect.to Windows2000.

    Nick wrote:
    > OK, So I have managed to get my employers to remove the compression.


    > I now get the following log in /var/log/messages.
    > Again you can see that CHAP authentication has succeeded but it fails
    > again in the protocol/compression negotiations.


    > Am I still screwed by Microsoft MS-PPC patents?


    > Jul 7 23:08:10 localhost pppd[2031]: pppd 2.4.1 started by root, uid 0

    ^^^^^^^^^^
    If you'll reread my first post you'll find I said

    In this case the standard 2.4.1 pppd doesn't support any form of MS-PPC,
    and rejects MS-PPC altogether.

    The recently available pppd 2.4.2b3, source at ftp.samba.org, does
    support the encryption in MS-PPC but not the patented MPPC.

    So the problem is the same but now pppd 2.3.2b3 should make it work since

    > Jul 7 23:08:45 localhost pppd[2031]: rcvd [CCP ConfReq id=0x4 < 12 06
    > 00 00 00 f0>]
    > Jul 7 23:08:45 localhost pppd[2031]: sent [CCP ConfRej id=0x4 < 12 06
    > 00 00 00 f0>]


    shows that indeed the MPPC part of the request is gone, and so there should
    be no Configure-Reject with proper configuration of pppd 2.4.2b3.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* Emacs vs vi:
    Sort of like a Swiss Army knife versus a rapier. */

  3. Re: Linux pppd fails to connect.to Windows2000.

    Clifford Kite wrote:

    > So the problem is the same but now pppd 2.3.2b3 should make it work since


    That's 2.4.2b3 of course.

    -- Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* Editing with vi is a lot better than using a huge swiss army knife.
    Use =} to wrap paragraphs in vi. Or put map ^] !}fmt -72^M in
    ~/.exrc and use ^] to wrap to 72 columns or whatever you choose. */

+ Reply to Thread