another person with slow net [Archive] - SpeedGuide.net Broadband Community
PDA

View Full Version : another person with slow net

j_syk
03-27-07, 10:42 PM
I have been having extremely slow interent in a university dorm with a t1 connection.
I have a 3 month old HP dv9000 laptop, windows vista, 1.6ghz amd turion dual-core, 2gb ram, 160gb hardrive

the first time i ran the TCP test (from http://nitro.ucsc.edu/) it ran a complete test, but when i ran it again i've been getting protocol errors


WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 7.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 6.97kb/s

------ Client System Details ------
OS data: Name = Windows Vista, Architecture = x86, Version = 6.0
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0-oem

------ Web100 Detailed Analysis ------
10 Mbps Ethernet link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 3020.0 msec; the Packet size = 1380 Bytes; and
No packet loss was observed.
C2S throughput test: Packet queuing detected: 57.46%
S2C throughput test: Packet queuing detected: 86.32%
This connection is receiver limited 60.62% of the time.
Increasing the the client's receive buffer (16.0 KB) will improve performance
This connection is network limited 39.19% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: OFF
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

and a tracert:

Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms srp000362srs.odonnell.mu.edu [134.48.200.19]
2 1 ms 1 ms 1 ms 134.48.10.210
3 1689 ms 1065 ms 1282 ms 134.48.10.12
4 1597 ms 949 ms 923 ms 134.48.10.30
5 * * * Request timed out.
6 * * 1010 ms 66.192.249.145
7 1704 ms 1433 ms 1637 ms core-02-so-0-0-0-0.asbn.twtelecom.net [66.192.244.1]
8 1078 ms 969 ms 1704 ms peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.249.18]
9 * 1259 ms 959 ms 66.192.252.239
10 * * 1715 ms ge-3-1-0-p140.msr1.re1.yahoo.com [216.115.108.57]
11 * 1542 ms * ge-1-42.bas-a2.re3.yahoo.com [66.196.112.203]
12 2137 ms 1470 ms 1528 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.


as you can see the speeds are very slow.
what do i need to do to fix the errors? and then with a complete test i'm sure there'll be more troubleshooting...
j_syk
03-27-07, 10:44 PM
i forgot to mention that no one else in my dorm, including my roomate, are having this slowness problem
trogers
03-27-07, 10:58 PM
I have been having extremely slow interent in a university dorm with a t1 connection.
I have a 3 month old HP dv9000 laptop, windows vista, 1.6ghz amd turion dual-core, 2gb ram, 160gb hardrive

the first time i ran the TCP test (from http://nitro.ucsc.edu/) it ran a complete test, but when i ran it again i've been getting protocol errors


WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 7.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 6.97kb/s

------ Client System Details ------
OS data: Name = Windows Vista, Architecture = x86, Version = 6.0
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0-oem

------ Web100 Detailed Analysis ------
10 Mbps Ethernet link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 3020.0 msec; the Packet size = 1380 Bytes; and
No packet loss was observed.
C2S throughput test: Packet queuing detected: 57.46%
S2C throughput test: Packet queuing detected: 86.32%
This connection is receiver limited 60.62% of the time.
Increasing the the client's receive buffer (16.0 KB) will improve performance
This connection is network limited 39.19% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: OFF
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

and a tracert:

Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms srp000362srs.odonnell.mu.edu [134.48.200.19] <= Ping times show a router
2 1 ms 1 ms 1 ms 134.48.10.210 <= Ping times show another router
3 1689 ms 1065 ms 1282 ms 134.48.10.12 <= Very Very high ping times
4 1597 ms 949 ms 923 ms 134.48.10.30
5 * * * Request timed out.
6 * * 1010 ms 66.192.249.145
7 1704 ms 1433 ms 1637 ms core-02-so-0-0-0-0.asbn.twtelecom.net [66.192.244.1]
8 1078 ms 969 ms 1704 ms peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.249.18]
9 * 1259 ms 959 ms 66.192.252.239
10 * * 1715 ms ge-3-1-0-p140.msr1.re1.yahoo.com [216.115.108.57]
11 * 1542 ms * ge-1-42.bas-a2.re3.yahoo.com [66.196.112.203]
12 2137 ms 1470 ms 1528 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.


as you can see the speeds are very slow.
what do i need to do to fix the errors? and then with a complete test i'm sure there'll be more troubleshooting...

Seems your connection is double NAT (2 routers connected back to back) and very high ping times at hop 3.

Try connecting your comp to the connection point of a dorm friend who does not have slow speed and do another tracert to compare with this one.

If you see a major difference in the ping times of the first 3 hops, contact your University Admin to rectify the problem.
j_syk
03-27-07, 11:25 PM
The first tracert was with the wireless connection and ethernet plugged in
this tracert is just thie wireless

Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 6 ms 4 ms 6 ms 10.160.0.1
2 7 ms 1 ms 4 ms 10.13.1.249
3 4 ms 4 ms 1 ms 134.48.10.210
4 1299 ms 1217 ms 1618 ms 134.48.10.12
5 1864 ms * 1660 ms 134.48.10.28
6 * * * Request timed out.
7 * 1051 ms 1303 ms dist-02-ge-3-0-0-508.milw.twtelecom.net [66.192.244.114]
8 * 1350 ms 1604 ms core-02-so-0-0-0-0.asbn.twtelecom.net [66.192.244.1]
9 1314 ms 1964 ms * peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.249.18]
10 * * * Request timed out.
11 * * 1536 ms ge-2-1-0-p140.msr1.re1.yahoo.com [216.115.108.17]
12 * 991 ms 759 ms ge-1-32.bas-a1.re3.yahoo.com [66.196.112.35]
13 753 ms 743 ms 1189 ms f1.www.vip.re3.yahoo.com [69.147.114.210]
trogers
03-27-07, 11:31 PM
The first tracert was with the wireless connection and ethernet plugged in
this tracert is just thie wireless

Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 6 ms 4 ms 6 ms 10.160.0.1
2 7 ms 1 ms 4 ms 10.13.1.249
3 4 ms 4 ms 1 ms 134.48.10.210
4 1299 ms 1217 ms 1618 ms 134.48.10.12
5 1864 ms * 1660 ms 134.48.10.28
6 * * * Request timed out.
7 * 1051 ms 1303 ms dist-02-ge-3-0-0-508.milw.twtelecom.net [66.192.244.114]
8 * 1350 ms 1604 ms core-02-so-0-0-0-0.asbn.twtelecom.net [66.192.244.1]
9 1314 ms 1964 ms * peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.249.18]
10 * * * Request timed out.
11 * * 1536 ms ge-2-1-0-p140.msr1.re1.yahoo.com [216.115.108.17]
12 * 991 ms 759 ms ge-1-32.bas-a1.re3.yahoo.com [66.196.112.35]
13 753 ms 743 ms 1189 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

I think your University's network does not accept a modem or router. Try a direct connection using just your Nic's ethernet socket.
j_syk
03-27-07, 11:57 PM
this is etherent only, no wireless:

Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms srp000362srs.odonnell.mu.edu [134.48.200.19]
2 1 ms 1 ms 1 ms 134.48.10.210
3 1439 ms 1848 ms 1465 ms 134.48.10.12
4 * 1459 ms 1285 ms 134.48.10.30
5 * * * Request timed out.
6 * 875 ms 693 ms 66.192.249.145
7 * 1134 ms 1654 ms core-02-so-0-0-0-0.asbn.twtelecom.net [66.192.24.1]
8 * 1470 ms 1953 ms peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.29.18]
9 * * 988 ms 66.192.252.239
10 959 ms 1154 ms 1304 ms ge-3-1-0-p140.msr1.re1.yahoo.com [216.115.108.5]
11 * 1575 ms 1250 ms ge-1-30.bas-a2.re3.yahoo.com [66.196.112.37]
12 1337 ms 2239 ms 1438 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.
trogers
03-28-07, 12:06 AM
this is etherent only, no wireless:

Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms srp000362srs.odonnell.mu.edu [134.48.200.19]
2 1 ms 1 ms 1 ms 134.48.10.210
3 1439 ms 1848 ms 1465 ms 134.48.10.12
4 * 1459 ms 1285 ms 134.48.10.30
5 * * * Request timed out.
6 * 875 ms 693 ms 66.192.249.145
7 * 1134 ms 1654 ms core-02-so-0-0-0-0.asbn.twtelecom.net [66.192.24.1]
8 * 1470 ms 1953 ms peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.29.18]
9 * * 988 ms 66.192.252.239
10 959 ms 1154 ms 1304 ms ge-3-1-0-p140.msr1.re1.yahoo.com [216.115.108.5]
11 * 1575 ms 1250 ms ge-1-30.bas-a2.re3.yahoo.com [66.196.112.37]
12 1337 ms 2239 ms 1438 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.

The tracert still shows a double NAT configuration from hop 1 and 2 and high ping times at hop 3. I suggest you get the University's computer admin to look into your connection line.
j_syk
03-28-07, 12:20 AM
is there anything i can do on my end? because i already have taken it into the network office and all the said was that the server has been slow recently.
but given that no one else has my problem i dont think the server speed is a problem.
any settings i can change that might make a difference?
if not, what exactly should i tell IT to look for?
trogers
03-28-07, 12:37 AM
is there anything i can do on my end? because i already have taken it into the network office and all the said was that the server has been slow recently.
but given that no one else has my problem i dont think the server speed is a problem.
any settings i can change that might make a difference?
if not, what exactly should i tell IT to look for?

The reason for your slow speed is the high ping times at hop 3. Get a few other tracerts from your dorm friends. I am sure their ping times are not at such high values. Present all the tracerts to the admin and get them to look into the cause for your high ping times. It could be a problem with the wiring.