The good warm fuzzies of a job well answered? -grin- it was a bloody nightmare to find the fault though... Nothing indicated a location for the cause.
-----Original Message----- From: yuri [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 November 2004 3:18 p.m. To: [EMAIL PROTECTED] Subject: Re: On Topic - Ethernet problems (answer) On Wed, 10 Nov 2004 15:12:00 +1300, C. Falconer wrote: > Yuri: > Worm? Virus? Broken network switch? Server down? Rodents chewed cat5 > cable? > > The answer is that someone had plugged a flylead back into the next > socket. That's all. One would have thought the switch, or the > upstream switch would have partitioned one or other ports off.... But > nope. Instead the entire network went to shite. So I was close with "Broken network switch". I meant to type "Broken network switch _setup_" (plugging both ends of a flylead into the same switch is a broken setup). So, what's my prize? -- ** WARNING to mailing list repliers ** Gmail over-rides "Reply-To:" field. Check your "To:" address before sending reply to this post.
