Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!spool.mu.edu!howland.reston.ans.net!gatech!newsfeed.internetmci.com!news.sprintlink.net!news.utse.smatnet.net!news2.smatnet.net!news.smat-mtc.com!usenet
From: "Brian M. Webb" <bwebb@smat-mtc.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: BSDI access server
Date: Thu, 22 Feb 1996 15:33:35 -0500
Organization: Sprint Mid-Atlantic Telecom
Lines: 13
Message-ID: <312CD31F.65BC@smat-mtc.com>
NNTP-Posting-Host: pjefft.smat-mtc.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.0GoldB1 (Win95; I)
When Windows 95 clients connect to my BSDI BSD 2.0.1 server they receive
"incompatible set of protocols" on automatic login. So instead they have a
terminal window open on connect and then enter in the login:name and
password:password information.
I am a Window's 95 MCP, and have supported Win95 at Microsoft.
Everything is configured properly in Win95 for automatic login. It is set to
PPP:Win95, NT, PPP. Logon to network enabled, TCP/IP is the only protocol
selected. TCP/IP is configured as I have a user defined IP address and DNS
address in the 95 connectoid. I have only the dial up adapter and TCP/IP
configured. Everthing is binding. However it won't login automatically to
my MSDI BSD 2.0.1 server.
Is there something in BSD 2.0.1 I have to configure? What am I
overlooking?