From owner-freebsd-questions Mon Apr 23 21:58:17 2001 Delivered-To: freebsd-questions@freebsd.org Received: from q.closedsrc.org (ip233.gte15.rb1.bel.nwlink.com [209.20.244.233]) by hub.freebsd.org (Postfix) with ESMTP id 1E45A37B423 for ; Mon, 23 Apr 2001 21:58:14 -0700 (PDT) (envelope-from lplist@closedsrc.org) Received: by q.closedsrc.org (Postfix, from userid 1003) id 5741855407; Mon, 23 Apr 2001 21:52:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by q.closedsrc.org (Postfix) with ESMTP id 47A4B51610; Mon, 23 Apr 2001 21:52:11 -0700 (PDT) Date: Mon, 23 Apr 2001 21:52:11 -0700 (PDT) From: Linh Pham To: Ted Mittelstaedt Cc: Mark Ibell , Subject: RE: PPP server problem In-Reply-To: <002601c0cc78$ae5f5900$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-04-23, Ted Mittelstaedt scribbled: # then see if it authenticates. I'd rule out any low-level # problems in the serial port or modem or you wouldn't see # "marki" as a username in the log. It's probably something # simple such as the password is case sensitive and your # sending the wrong case, or the /etc/ppp directory is not readable # by ppp or the files in it aren't readable by ppp, or the # Windows client is sending a space character in the password # or the ppp config files have extra characters in them that you # aren't aware of or something like that. Note also my comment in the article # aobut NT4 cleartext being required, if your running NT. See if # you can test with a different Windows client if possible. If the client is running Windows 2000, both MS-CHAP and MS-CHAP v2 should be disabled in many cases to login successfully. To do so, open up the dial-up icon, choose Properties and under the Security tab, instead of using the default security, choose Advanced and click the settings button. Remove the check from both CHAP checkboxes and OK all the way back out. We have run into weird problems at times when dialing into a straight UNIX box when either options were enabled. Providers like Worldcom/UUNet require those settings to be off no matter what to connect and authenticate properly. You don't have to worry about that under Windows NT 4.0 or Windows 95/98 (and probably ME, but since I wouldn't dare to touch that thing with a 20m pole... I wouldn't know.. hehe). -- Linh Pham [lplist@closedsrc.org] // 404b - Brain not found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message