From owner-freebsd-isp Sun Jan 25 20:55:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04650 for freebsd-isp-outgoing; Sun, 25 Jan 1998 20:55:28 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04643 for ; Sun, 25 Jan 1998 20:55:26 -0800 (PST) (envelope-from kendo@Mars.mcs.net) Received: from Mars.mcs.net (kendo@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id WAA08531; Sun, 25 Jan 1998 22:55:25 -0600 (CST) Received: from localhost (kendo@localhost) by Mars.mcs.net (8.8.7/8.8.2) with SMTP id WAA07900; Sun, 25 Jan 1998 22:55:24 -0600 (CST) Date: Sun, 25 Jan 1998 22:55:24 -0600 (CST) From: kendo To: Robert Ricci cc: freebsd-isp@FreeBSD.ORG Subject: Re: Win95 and WINS In-Reply-To: <34C6DD23.D14B6735@theonlynet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I work in the ISP industry. I have encountered Win95 problems of this ilk. Wins Config should be set to disable wins resolution. If it is already set this way try setting it to use DHCP for WINS resolution and rebooting. After reboot, go back in and set it to Disable WINS resolution again. Usually this fixes those problems. I have no explanation as to why Win95 blows. On Wed, 21 Jan 1998, Robert Ricci wrote: > We use a FreeBSD box with Cyclades cards in it for our dial-in accounts. > Mgetty answers the line, then pppd is used for the ppp end of things. > Many of our clients who use Windows 95 have had occasional problems > dialing in. The symptoms are diverse ("Cannot establish a compatible > protocol" to inability to send any packets once authenticated). However, > the common theme seems to be that if they change the WINS setting (In > the TCP/IP settings in the Control Panel), the problem goes away. Some > people have to turn on WINS, some have to turn it off. (Don't ask me why > turning it ON helps!) From ijppp on my home FreeBSD machine, I have no > such problems. Have any of you ever had an experience like this? Were > you able to fix it? (Unfortunately, telling all my customers "Get a real > OS" isn't an option.) Here's what's in my /etc/ppp/options file: > > crtscts > modem > proxyarp > defaultroute > dns1 206.29.203.3 > domain theonlynet.com > kdebug 0 > auth > -chap > +pap > login > passive > silent > asyncmap 000a0000 > pap-timeout 30 > > Any changes I should make here? > > Also - We have a WEIRD version of FreeBSD on this machine - 2.2-GAMMA . > I'd love to upgrade, but I can't spare the downtime right now. I've got > Danny's pppkit , but I've been afraid to install the pppd that came with > it, because of our unusual version of FreeBSD. Do you know if it will > work? > > Apparently NT terminal servers (I shudder at the thought) don't have > this problem. Another scheme to try to make us use NT? > > Robert Ricci > rricci@theonlynet.com > > "We demand rigidly defined areas of doubt and uncertainty!" > -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" >