From owner-freebsd-current  Thu Mar  6 09:16:24 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA29244
          for current-outgoing; Thu, 6 Mar 1997 09:16:24 -0800 (PST)
Received: from sol.harbor.ab.ca (sol100.harbor.ab.ca [198.161.82.169])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29239
          for <current@freebsd.org>; Thu, 6 Mar 1997 09:16:21 -0800 (PST)
Received: from olympus (olympus.harbor.ab.ca [198.161.82.144]) by sol.harbor.ab.ca (8.6.10/8.6.9) with SMTP id RAA27601; Thu, 6 Mar 1997 17:12:09 GMT
Date: Thu, 6 Mar 1997 10:12:07 -0700 (MST)
From: Stephen Mathezer <mathezer@harbor.ab.ca>
X-Sender: mathezer@olympus
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 
In-Reply-To: <199703040646.WAA09994@MindBender.serv.net>
Message-ID: <Pine.GSO.3.95.970306095658.12016B-100000@olympus>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


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.
>