I was just discussing this with one of the LAN guys here and it sound like the problem is with the Novell client and some service it expects to be running before a user logs in. If the network is unavailable and that service doesn't start in time and then a user attempts to log in, the PC reboots. It appears to be a combination of "features" that cause the problem.
John >>> "Steven A. Ridder" 1/25/02 9:09:00 AM >>> Those DELL's with the 3com nic's have so many problems! There's a thread over in comp.dcom.sys.cisco with someone else having problems with the same PC's and NIC's. Usually the 3c509's are OK. I remember the 3C509B's as being rock-solid. How fast are the PC's booting to beat portfast? Or are the NIC's some sort of boot on lan client, where the NIC get's taken over before the OS even loads. Maybe someone can disable the wake on lan feature if those DELL's have it, because otherwise I can't imagine a NIC caring about network connectivity before the OS kernel wakes up and takes over the NIC anyways. ""John Neiberger"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Well, sort of resolved. This turned out to be a known issue with Dell > machines, specifically machines using a 3COM 3C905C NIC. They expect > the network to be available almost immediately upon bootup and can't > handle the delay caused by spanning tree. In some cases, even portfast > did not reduce the time sufficiently. > > So, watch out for those 3COM NICs! > > John Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33208&t=33203 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
