How best to troubleshoot my network issues

Hello,
I have a relatively small network, consiting of an SBS 2003 server and about 20 PCs.
The building is long with two floors.
The setup is as follows:
The server sits at the south end of the top floor. It connects to a big switch about 30 feet away. This switch connects a bunch of PCs, but a cable connects this switch to a small switch at the north end of the building, from which all PCs there and downstairs connect.
These PCs have an extremely slow connection.
I'm not sure if my problem lies with cabling, or the switch, or whatever else may be affecting it.
I'm looking for some advice on how to test to pinpoint the problem.
I've been researching, but googling turns up a lot of software to purchase - which I don't mind doing - but I can't sort out the crap from the good ones... I'm hoping someone will suggest something they use with a similar setup.
Thanks!
Amber

 

Hi. My name is Zack Magee, and I am newly certified to help you out here. (I love saying that )

Let's start by tracking down where the lag is. In command prompt, type tracert google.com and post the response here. This will allow me to see where the lag is.

 

I would also suggest looking at the switches and post what the manufacturer and model is so that we know what the specs are and what speed the interfaces should/could be running at.

 

Is the lag on the internet or connections between local pcs? Tracrt to google wont help with the one issue

 

This is why I carry this..
http://www.jdsu.com/en-us/Test-and-...t-list/Pages/lanscaperpro-network-tester.aspx

 

Yeah the way I read the original post was that the slow down happens on the PC's only behind the small switch. So I don't think the tracert would help much. That's why I would be interested in the manufacturer and model of that switch. Also the cable lengths in use here would be helpful since it connects Pc's on another floor and is there a hub in there somewhere? That tester would be handy but a bit pricey for this situation!

 

a basic simple method would be to use ping the the continous ping option to see an average of response time for a path.

 

Maybe I'm old fashioned or just low tech. I do all of this before i move on to tools and testing and tracing.

Has it always been slow in this configuration or did it start to happen over time?

Those PC's that are at the far end are all slow connecting to the server, the internet or both?

How far is that switch from the one before it? The limit between switches is 100 ft of cable length.

How old is that furthest switch?

Could someone have touched a button on the switch to change the the speed out off of auto to have it restricted to say, 10 of the 10/100? Does the switch have an uplink port? Are you using that port from furthest switch to the first switch? Is that cable definitely running into the uplink port (if there is one) in the first switch and the first switch doesn't have anything set or pressed on it that would interfere with uplink?

Is the first switch a 24 port switch? You can usually change which block the cable runs to, all of the ports will auto sense. Take the connecting cable out of the port section it is in and trade it with one that is in another block of ports that you know is good. I've had this happen with netgear more than once and another brand as well. The switch is good except for one section. (you can try this at the other switch as well, switch ports)


Check that the cable between switches is not kinked or pinched in any way and that it is stamped on it certified in a version of CAT5 or CAT6 cable. I would power down the switches, reseat the cables in question, power back up. (i'm also in a building that is two floors and long, this step i have to guess at for the portion i can't see)

If none of that made any difference, i would try a spare switch and test if it changes anything. A spare switch is a lifesaver if you don't already have one, it's never a waste.

I think that's my bag of tricks before I move on to tracing.

 

I figured a tracert to google would help, because it will show me the amount of time it took to hop to the first switch, the second switch, and the ISP's router.

 

These are likely just layer 2 switches so they will not show up on the tracert. Tracert only shows layer 3 hops. The first hop will likely be whatever device is the gateway on this network.