Date: Thu, 6 Mar 1997 10:12:07 -0700 (MST) From: Stephen Mathezer <mathezer@harbor.ab.ca> To: "Michael L. VanLoon -- HeadCandy.com" <michaelv@MindBender.serv.net> Cc: current@freebsd.org Subject: Re: Solution to Help w/ ppp to NT 4 server Message-ID: <Pine.GSO.3.95.970306095658.12016B-100000@olympus> In-Reply-To: <199703040646.WAA09994@MindBender.serv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the help. As it turns out, we are running NT 4 with SP 2 but my problems turned out to be a misunderstanding on my part, we have yet to see any problems attributable to NT. I needed to turn off the 'Require Microsoft Authentication' checkbox on the server but then I also needed to use the 'name' option on pppd. Apparently pppd tries to use your hostname as a username despite the fact that mty chap-secrets specified something else. Once I used turned off the Microsoft extensions and used the 'name' option everything worked great! -Steve On Mon, 3 Mar 1997, Michael L. VanLoon -- HeadCandy.com wrote: > > >I inquired yesterday about connecting as a client to an NT 4 server with > >ppp. I couldn't get either pppd or iijppp to successfully authenticate. > >I believe that this is due to the Microsoft Chap extensions on the NT > >server which encrypts the username/password. Anyways, I have turned off > >those extensions on the server and expect everything to work fine but in > >the course of exploring this I discovered some patches to pppd to support > >the MS extensions. > [...] > > Also, verify what version of NT they're running. If they have > upgraded NT 4.0 to Service Patch 2, verify that they have applied the > PPP fix. Stock Service Patch 2 broke some PPP functionality. > Alternately, they can back-step to SP1 if there are no specific fixes > they need in SP2. SP3 should be out soon, and is the first SP to go > through a beta cycle, so it should be very solid. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.95.970306095658.12016B-100000>