Official Network Troubleshooting Thread

[Simmy]

Lo all,

I'm hoping we can make a thread about troubleshooting networks (both wireless and wired) and sticky it to the top of this forum section. I'll make a start later on as I've just got back from the gym and I'm too tired to do it now (Plus big brother is on :p).

If you've got any input yourselves, please add to this thread. I will try and edit the thread so that all the important info is well laid out in the first post.

[acs]

My first step is always.
run
Cmd
ipconfig /all

That gives you plenty of info ( or none info) to start with.

[jhoppe]

LEDs...making sure the LED's are lit and lit correctly...oftentimes, they get overlooked, but they are a good place to start.

[Crgky127]

WinSockFix deserves a mention. Also on some laptops, there is a switch near the front to turn on/off the wireless radio. And even worse, some have a function key for it (it's worse because programs can turn it off without telling you for no reason!).

[bmetman]

I think that is a great idea. That would definetly be a helpful thread. I like ipconfig/all, link lights and of course ping.

[seedubya]

Depends on what the trouble is but the basics are....

cables secure,
link lights
ipconfig /all
ping localhost
ping 127.0.0.1
ping default gateway or other internal IP
ping www.google.com or other website, by name
ping 159.134.237.6 (or other external IP)

Somewhere in the midst of all this you'll hit a showstopper - start troubleshooting from there.

We need a troubleshooting flowchart to do this properly.

EDIT: I just signed up for Gliffy, an online flowchart creator. Login is NOSPAMMERScolmmwhelan@gmail.com PW is technibble
I have not started the diagram, I'll leave that to someone else.

[minuswires]

I like to troubleshoot networks using the OSI MODEL.
Using all 8 Layers. Yes 8 layers. The "user" is the 8th Layer

Anywho start from the Cables/wires/ports then to the switching, etc.

Using the OSI Model really works for me. You don't miss any steps.

I also like to use Netstat -a
Netstat is a good way also to see if a machine has Spyware/Virus
because you get to see what connections are established.

In all my training I truly found Cisco's CCNA Course/Certification to be most helpfull in my career. It really takes you to the next level in understanding what really happens in the wire and client / server relationship.

[TimeCode]

1) When installing a NetGear router NEVER use the CD that comes in the box. Turn it over, and look for the IP Address on the bottom. Set your PC's IP to the same subnet and then go to your browser and type in the exact IP Address that was on the bottom of the router. Set it up within the web interface.

2) Always have a cable tester to check that the pin-out is correct and there are no shorts.

3) ping 4.2.2.2

4) Don't bother pinging microsoft.com. It doesn't reply. Google and Yahoo do.

[Wheelie]

I like to troubleshoot networks using the OSI MODEL.
Using all 8 Layers. Yes 8 layers. The "user" is the 8th Layer

Anywho start from the Cables/wires/ports then to the switching, etc.

Using the OSI Model really works for me. You don't miss any steps.

I also like to use Netstat -a
Netstat is a good way also to see if a machine has Spyware/Virus
because you get to see what connections are established.

In all my training I truly found Cisco's CCNA Course/Certification to be most helpfull in my career. It really takes you to the next level in understanding what really happens in the wire and client / server relationship.
Damn good info. Thanks.