Xref: utzoo comp.protocols.tcp-ip:8481 comp.unix.xenix:7833 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!aramis.rutgers.edu!geneva.rutgers.edu!hedrick From: hedrick@geneva.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.tcp-ip,comp.unix.xenix Subject: Re: TCP/IP network "crash" Message-ID:Date: 28 Sep 89 23:09:45 GMT References: <833@dms.UUCP> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 11 Your software is buggy. Now and then we've run into implementations where for some reason or other the software hung. These have generally been new implementations. Such bugs were regarded (correctly) as serious problems, and fixed. It's also possible that a bug or misconfiguration has resulted in a "broadcast storm". In that case, your software isn't hung -- it's just being saturated by lots of packets. I would suggest getting one of the MS/DOS TCP/IP implementations, and running netwatch. That should show you what is going on if it's a broadcast storm. If it's a fragile Ethernet device driver, looking at the net may not shou anything. Probably that can only be debugged if you have source to the software.