Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!sol.ctr.columbia.edu!news.kei.com!news.oc.com!NewsWatcher!user From: wier@merlin.etsu.edu (Bob Wier) Subject: Slow network id? Message-ID: <wier-231093111733@192.43.199.25> Followup-To: comp.os.386bsd.questions Sender: usenet@ra.oc.com Organization: East Texas State University Date: Sat, 23 Oct 1993 17:17:33 GMT Lines: 34 I'm running 386BSD .1 - it's been working perfectly for my uses for 6 months so havn't done anything to the software which was as of about March 1st. 386SX, 4 meg, 1542b, 550meg Fuji, wd8013 non-software configurable thin ethernet card (ie, jumpers). One problem though. When I isolate the network from the rest of the school (ie, no nameserver) I have a mac which speaks to BSD thru 3' of cable - the mac is running MacTCP and NCSA telnet. Ping works fine from bsd to the mac (zero delay, no packet loss). I can also ftp under control of BSD fine. The problem is going back the other way. When I open a window via NCSA to BSD, the window opens immediately, but it takes a *LONG* time to get a login prompt (like 2 minutes). Once I get the prompt it works fine, can login normally. This occurs with ftp from the mac to bsd as well. I'm not a net expert, so I can only guess what's happening. Is maybe BSD trying all possible class c addresses to id all machines on the net? Or is something waiting to timeout (waiting on a return from the non-existant nameserver perhaps?). When I'm on the school net with a nameserver, the window opens from the mac to bsd and the login appears immediately. However, specifying the ipaddress on the ncsa open for bsd when disconnected from the school net does not speed the problem up. Wonder if anyone has a suggestion on this? ======== insert usual disclaimers here ============ Bob Wier, East Texas State U., Commerce, Texas wier@merlin.etsu.edu (watch for address change)