Date: Wed, 21 Jan 1998 22:46:11 -0700 From: Robert Ricci <rricci@theonlynet.com> To: freebsd-isp@FreeBSD.ORG Subject: Win95 and WINS Message-ID: <34C6DD23.D14B6735@theonlynet.com>
next in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34C6DD23.D14B6735>