From owner-freebsd-isp Thu Apr 10 13:51:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA29337 for isp-outgoing; Thu, 10 Apr 1997 13:51:48 -0700 (PDT) Received: from bellind.com ([206.101.34.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29326 for ; Thu, 10 Apr 1997 13:51:41 -0700 (PDT) From: RGireyev@BellInd.com Received: from cdcexchange.bellind.com ([170.1.130.2]) by firewall.bellind.com with SMTP id <17066-1>; Thu, 10 Apr 1997 13:51:22 -0700 Received: by cdcexchange.bellind.com with Microsoft Exchange (IMC 4.0.837.3) id <01BC45B6.FE0BC580@cdcexchange.bellind.com>; Thu, 10 Apr 1997 13:56:30 -0700 Message-ID: To: Cc: Subject: RE: Windows 95 -ppp-> FreeBSD nameserver problem Date: Thu, 10 Apr 1997 13:56:29 -0700 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The pitiful, crap, windors95 dung does not have scripting options. So you cannot write a script to do this for your customers. You must tell your, already confused users, to do the following: Click Start->Settings->Control Panel Double Click Network Scroll through installed network components and locate TCP/IP (This of course assumes Microsoft stack) Highlight TCP/IP and click on Properties A screen with six tabs will show up Select the DNS Configuration Click on Enable DNS Enter Host and Domain Enter DNS IP number AND CLICK ADD If applicable enter Domain Suffix IP and click add. This should resolve the DNS problem, but the fun is only starting :-). Enabled WINS or improper or missing gateway IP number maybe the source of other problems. Hope this helps. Rudy >---------- >From: Charles Reese[SMTP:reese@chem.duke.edu] >Sent: Thursday, April 10, 1997 12:05 PM >To: freebsd-isp@freebsd.org >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. > >HELP HELP >please >Charlie Reese > > > >------------------------------------------------------------- >Charles E. Reese * * >Durham, NC 27710 * Buy Sell Trade CDs * >919-660-1585 * NO MIDDLEMAN * >919-544-7217 * TOTALLY FREE * > * http://trader.ourway.com * >reese@chem.duke.edu * * >------------------------------------------------------------- > >