Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!uwvax!uwmacc!uwmcsd1!marque!gryphon!crash!paul
From: paul@crash.cts.com (Paul Palacios)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Novel problems with Novell networks
Message-ID: <2066@crash.cts.com>
Date: Wed, 2-Dec-87 10:26:43 EST
Article-I.D.: crash.2066
Posted: Wed Dec  2 10:26:43 1987
Date-Received: Sun, 6-Dec-87 08:44:59 EST
References: <1411@mind.UUCP>
Reply-To: paul@crash.CTS.COM (Paul Palacios)
Distribution: na
Organization: Crash TS, El Cajon, CA
Lines: 19
Keywords: crashes kaboom la-la-land Novell unreliable ???

Commonly, such crashes as you describe are caused by one or more of the
following:

1)	there's not enough memory on the fileserver for the cache
2)	some other person or network tried attaching to your fileserver
	with the the same physical node address as someone elses, in your
	local network; someone also has your node address.
3)	broken or bad cable connection:
		at the connector of the cable
		internal to the wire
		at the connector on the net card

I'm sure there are many other reasons / factors involved.  Hope this helps.

----                                                                      ----
-- 
Paul Palacios  UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!portnoy!paul 
POBox 842,(CA) INET: paul@portnoy.cts.com              VOICE: wk:(619)458-0230
Bonita, 92002  ARPA: crash!portnoy!paul@nosc.mil              hm:(619)420-.e.e.