Date: Thu, 10 Apr 1997 15:28:32 +0000 From: reakins@nms.net To: Charles Reese <reese@chem.duke.edu> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Windows 95 -ppp-> FreeBSD nameserver problem Message-ID: <199703121839.LAA01183@www.nms.net> In-Reply-To: <1.5.4.32.19970410190507.00724c50@chem.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Thu, 10 Apr 1997 15:05:07 -0400 > To: freebsd-isp@FreeBSD.ORG > From: Charles Reese <reese@chem.duke.edu> > Subject: Windows 95 -ppp-> FreeBSD nameserver problem > I have set up a FreeBSD box as a terminal server using pppd. It all seemed > to be working fine (2 days) until last night when suddenly Windows 95 > dial-in users cannot seem to get nameservice. Win 95 apps like Netscape and > WS_FTP work fine with IP numbers but not at all with names. The Win 95 > dial-in properties have the nameserver boxes filled in correctly as far as I > can tell. The nameservers are not on the same subnet as the terminal server > but are connected via an Ascend router (frame relay) to the Digex (our ISP) > nameservers. The nameservers work fine if I do a shell login to the > terminal server and telnet, ftp etc from there. Since the nameservers work fine when you use a shell account, and the 95 boxes can connect using ip addresses, the problem appears to be a routing problem between the nameserver(s) and your Win95 boxes. Check your default gateway entry in win 95 and make sure that the routes to the nameservers are correct elsewhere in your network. Ronald E. Eakins, Sr. SNE, NMS, Inc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703121839.LAA01183>