> > I always try power
> > cycling all of the network hardware. 99+% of the time it
> solves the problem.
>
> I'll have to keep this in mind. The funny thing is
> that the switch,
> along with everything else, already _was_ power cycled, in each of the
> (brief) power outages. Of course, when I worked in tech
> support and we
> needed a customer to power cycle a machine, we'd say to leave
> it off for
> about 30 sec. before turning it back on...
And, of course, even though it is not SUPPOSED to matter, the ORDER in which
you turn things on can make a difference as well. I used to have a network
with one Unix server, two Novell servers, and about a dozen NT servers
(guess which ones required the most tinkering!!) The startup order was:
1. hubs
2. switches
3. routers
4. Unix
5. Novell (in any order)
6. NT (in a specific order)
This sequence was guaranteed to work. Any deviation was a crap shoot.
And speaking of tech support, let's not forget "copying" floppy disks on the
Xerox, adapting 5.25" floppies to fit a 3.5" drive using the scissor method,
nor those really convenient coffee cup holders they put in systems these
days. :-)
