Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 Jun 1997 08:09:01 -0400
From:      Brad Bates <>
To:        "'freebsd-questions@FreeBSD.ORG'" <>
Cc:        "'WaiKin Wong'" <>
Subject:   Dead Thread?  RE: BSD and NT rass
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
Yes, NT will work (if it is setup to do so) & I stand corrected
on that.  We also found out the answer on how to do it if one
does have access to the server. Thanks to those who passed
that along (and answered the question that was at hand).

New (non-Micro$oft) thread anyone?

From: 	WaiKin Wong[]
Sent: 	Saturday, June 07, 1997 2:54 AM
To: 	Brad Bates; Chuck Gibson; freebsd-questions@FreeBSD.ORG
Subject: 	Re: BSD and NT rass

At 07:09 AM 6/6/97 -0400, Brad Bates wrote:
>NT does not work like a UNIX PPP server, and unless
>you are running the NT server (I assume your ISP runs it)
>you probably will not get to connect like you expect.  NT's
>remote access server uses a Microsoft flavor of PPP that
>is designed to shelter the fragile folks who use Windows
>95 and 3.11 from gory things like a login prompt on a black
>screen.  They just call in and connect, and their logins are
>in the dialog boxes in windows, which is then passed via
>the abstraction layers to and through the OS and hardware.
>Trying to get a login prompt from an NT system by just
>calling via modem on a terminal screen will not work.  I have
>not heard of anything that lets one do this from UNIX to NT,
>only from NT or Windows to UNIX.
>Has anyone done this out there?
>Primary reasons -- TCP/IP is new to that world (sold as a
>feature!); and logins and passwords are handled via windows
>(usually dialog boxes) and passed within applications and/or
>the OS using API calls.  See the MS resource kits and/or
>the API specifications for more.

How completely wrong... RAS isn't that foreign to the world of PPP logins.
Read the man chapter about CHAP and PAP authentication for PPPD. That's it.
NT does both of them. No magic here.

Want to link to this message? Use this URL: <>