Hal's Guide to Network Troubleshooting

[prillalar]

I've seen so many posts about networking problems on my flist in the last few days. I administer the networks both at work and at home, so I thought I would share my never-fail troubleshooting process.

1. Make sure everything is plugged in.

2. Turn everything off and on again, in varying orders.

3. Human sacrifice.

And that's all you need to know!

Comments

[zortified.livejournal.com]

You should specify that it helps if you sacrifice the idiot who made the computer not work in the first place.

;-)

[marksykins.livejournal.com]

Can animals sacrifice be substituted in a pinch?

[insaneneko.livejournal.com]

Ah, crap, no wonder I have such a hard time fixing things. I do 1 and 2, but never 3. Doh.

[lapislaz.livejournal.com]

Dangit! I knew I was leaving something out!

::goes off to start turning things on and off::

[storyteller.livejournal.com]

Thank you for the help! :D :D :D

[annotated_em]

Huh. First good reason I've heard yet for keeping roommates around.

[noshootingstars.livejournal.com]

Sometimes I'm so impatient I skip straight to number three only to later discover I could have fixed the problem with 1 & 2. Boy, is that embarrassing.

[mousapelli.livejournal.com]

*cries and cries*

[penknife.livejournal.com]

Clearly I need to move on to #3. I was going to try fiddling with my firewall settings, but I think at this point #3 would be more satisfying.

[qem_chibati]

Sadly the candidates for number 3, are prooving to difficult to actually complete the sacrifice...

[leviosa8.livejournal.com]

Human sacrifice...
My father knows a lot about that.
He learned how to install a PC, a net, and a network all by himself and wasting many a weekend for over a decade now.

[mitethe.livejournal.com]

My choice of victims must be unsatisfactory because 3 still doesn't do the trick. Maybe if it's en masse...?