Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in1.uu.net!zib-berlin.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: BSDI access server Date: 24 Feb 1996 16:18:52 GMT Organization: Private BSD site, Dresden Lines: 20 Message-ID: <4gndpc$9g0@uriah.heep.sax.de> References: <312CD31F.65BC@smat-mtc.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 "Brian M. Webb" <bwebb@smat-mtc.com> writes: > 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. You are posting to the wrong group, but nevertheless, the answer is similar for BSD/OS or FreeBSD: kill Micro$loth's private protocols. They insist on using it, and consider a connection without the crap to be soooo worthless that they give up the connection. There must be a knob somewhere in Winglows to prevent it from giving up, and use standard PPP instead. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)