At my office, the network they have set up here is rediculously slow… I’m currently downloading at about 10.5k/sec right now (cries…)
Anybody know what i can do to troubleshoot and find out where the bottleneck is for this problem?
I know very little about network admin’ing…
This wont help mush for download speed but can you do a tracert?
Start, Run, type cmd, then press enter.
tracert yahoo.com(or anywhere)
Paste results here, sounds like they are 1. QoS throttling connection 2. superrrr slow 3. having network issue if this is not all the time thing.
I’m at home now, but here’s a tracert that i did earlier today when i was at work:
U:>tracert google.com
Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 10.68.1.254
2 692 ms 683 ms 593 ms 192.237.112.164
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 757 ms 850 ms 803 ms 143.159.16.145
8 796 ms 788 ms * 143.159.16.147
9 * 598 ms 745 ms luci20.infonet.com [209.28.174.20]
10 564 ms 511 ms 453 ms losangeles50.us.eqip.net [63.250.128.205]
11 879 ms 580 ms 733 ms sanjose6.us.eqip.net [63.250.128.173]
12 871 ms 930 ms 689 ms sanjose1.us.eqip.net [63.250.129.10]
13 652 ms 717 ms 769 ms eqixsj-google-gige.google.com [206.223.116.21]
14 825 ms 749 ms 852 ms 72.14.236.3
15 1021 ms 824 ms 848 ms 72.14.233.146
16 748 ms 861 ms 837 ms 72.14.233.146
17 837 ms 655 ms 707 ms 66.249.94.96
18 869 ms 920 ms 868 ms 72.14.236.130
19 855 ms 575 ms 701 ms 72.14.207.99
Trace complete.
Also, yes, it is ALWAYS this slow… something is really messed up in our network and I’d like to go to the network admins about it if i can narrow down where the issue might be.
WOWSER!
almost 1 second to the first hop!
It sounds to me like someone is downloading porn all day or something!
compare that to this while I am on a livechat, talking on VOIP, and here on JH forums and psoft forums browsing, and I am getting some outside packetloss, but still very usable:
C:>tracert google.com
Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.10.1
2 3 ms 2 ms 2 ms 192.168.1.1
3 31 ms 27 ms 28 ms L100.DSL-01.SANGTX.verizon-gni.net [71.115.96.1]
4 * * * Request timed out.
5 36 ms 35 ms 36 ms so-0-0-0-0.BB-RTR1.DFW01.verizon-gni.net [130.81
.20.60]
6 34 ms 34 ms 33 ms so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.173]
7 34 ms 33 ms 35 ms 4.78.234.1
8 39 ms 36 ms 33 ms ae-32-56.ebr2.Dallas1.Level3.net [4.68.122.190]
9 39 ms * 39 ms ae-1.ebr1.Dallas1.Level3.net [4.69.132.45]
10 58 ms 54 ms 54 ms ae-3.ebr1.Atlanta2.Level3.net [4.69.132.82]
11 68 ms * 150 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
12 78 ms 73 ms 72 ms ae-3.ebr1.NewYork1.Level3.net [4.69.132.90]
13 75 ms 75 ms * ae-11-51.car1.NewYork1.Level3.net [4.68.97.20]
14 75 ms 75 ms 74 ms 4.78.164.218
15 73 ms 72 ms 75 ms 72.14.236.215
16 91 ms 93 ms 88 ms 72.14.233.115
17 89 ms 90 ms 89 ms 66.249.94.94
18 89 ms 96 ms 88 ms 72.14.236.130
19 90 ms 89 ms 89 ms 72.14.207.99
Trace complete.
C:>
ok so we’ve proved my network sucks… 
anybody got any troubleshooting tips? process of elimination, etc…
See if you can find out where the router/switch/network closet is and see if it is 150degrees in there and making the equipment run at slooowwww speeds.
that would be our supply closet/datacenter. normal temps in there.
I sure hope that second hop is outside of your network, otherwise a lan with that time has serious problems. I would think showing tem the tracert is enough to show them there is a problem. I can get across the contry quicker (trace wise) than that second hop going through lots of hops.
well, the 2nd hop starts with 192… doesn’t that usually mean LAN?
If you give brief overview of your network setup to your ISP and the IP assignment, it can help us think more.
192 could be lan, or it would be a WAN to a main office somewhere too, but either way 192ms is SLOW.