I checked out that my CHAP user should be "MSN/yunsheng" instead of "yunsheng". And now my connection is fine. Thanks for your help.
Tim > > >>From: "Paul J. Keenan" <[EMAIL PROTECTED]> >>To: Yunsheng Zheng <[EMAIL PROTECTED]> >>Subject: Re: CHAP problem >>Date: Thu, 30 Dec 1999 19:11:33 +0000 >> >>On Wed, Dec 29, 1999 at 09:59:28PM -0800, Yunsheng Zheng wrote: >> > Hi guys, >> > >> > I am new to Debian and I'm trying to set up a PPP connection to my ISP, >> > which is MSN. I used pon to dial and I have problem. It seems CHAP was >> > not authenticated by the server. Thanks in advance for any hints and >>suggestions. >> > >> > The following is my chap-secrets: >> > # Secrets for authentication using CHAP >> > # client server secret IP addresses >> > # The next line was added by pppconfig for provider. >> > yunsheng * mypasswdhere >> > >> > The following is my ppp.log: >> > Dec 24 17:00:32 BlackJade pppd[227]: rcvd [LCP ConfReq id=0x2 <mru 1524> >><asyncmap 0xa0000> <auth chap 05> <pcomp> <accomp>] >> > Dec 24 17:00:32 BlackJade pppd[227]: sent [LCP ConfAck id=0x2 <mru 1524> >><asyncmap 0xa0000> <auth chap 05> <pcomp> <accomp>] >> >>Good so far. This is both machines agreeing to use the standard CHAP >>protocol (05). >> >> > Dec 24 17:00:32 BlackJade pppd[227]: rcvd [CHAP Challenge id=0x1 >><c6c69aa3913632d82392e3d944a04a18>, name = "tnt1.ontario"] >> > Dec 24 17:00:32 BlackJade pppd[227]: sent [CHAP Response id=0x1 >><8af8b385bd53459e8267f1b9514128eb>, name = "yunsheng"] >> > Dec 24 17:00:33 BlackJade pppd[227]: rcvd [CHAP Failure id=0x1 "\000"] >> > Dec 24 17:00:33 BlackJade pppd[227]: Remote message: >> > Dec 24 17:00:33 BlackJade pppd[227]: CHAP authentication failed >> >>Oh dear. >> >>The CHAP request from the server tnt1.ontario came in. The pppd program >>made a hash of the arbitary string sent to you (c6c69aa9...) using your >>password in the CHAP secrets file as the key, and came up with the >>string 8af8b385... >> >>But at the same time, the server was hashing up the same string, with its >>copy of the chap secret password, and it came up with a different answer. >>Since the hashing algorithm is the same on both machines, either : >> >> you both came up with the same answer, but you were still not allowed >> to log in (e.g. your account has been suspended) >> >> or >> >> your response didn't match the server's computed result (the passwords >> used in the hashing process didn't match). >> >>So it rejected the authentication attempt. >>I think the latter is more likely. >> >>Browsing /usr/share/doc/ppp/FAQ.gz comes up with : >>--------------------------------------------------------------------- >>- The file may contain comments, which begin with a `#' and continue >>to the end of the line. >> >>- Double quotes `"' should be used around a field if it contains >>characters with special significance, such as space, tab, `#', etc. >> >>- The backslash `\' may be used before characters with special >>significance (space, tab, `#', `\', etc.) to remove that significance. >>--------------------------------------------------------------------- >> >>So either escape the metacharacters with "\" or enclose the string >>in quotes if it's not already like that. If you need backslash >>or quotes inside the password string, use >> >>Other than that, you need to contact the ISP and ask them to check >>that you are authorised to dial into tnt1.ontario, and ask them to >>email you the chap secret password for reconfirmation. >> >>Good luck. >> >> > >> > Tim >> > >> > >> >>-- >>Regards, >>Paul >
