PDA

View Full Version : question



_daynzy
12-28-2008, 02:11 PM
in our house, we have 3 laptops, and one wired desktop..

they're all hooked up to a d-link router... laptops wireless, decktop wired. theres also a ps3 hooked up wirelessly too


our internet is awful slow on each computer.. is it suppose to be slower because of the number of computers, or should it still be fast?\

shaw highspeed with their new modem

Hans
12-28-2008, 02:36 PM
It should not matter, unless all 3 are downloading at maximum speed.
You can go to the following site to test your speed and line statistics.

http://web100.uvm.edu:7123/

Once the test is done, you can click on statistics and more details to see where the problem is, if there is a problem.

It should look something like this :

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

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_11

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 149.73 msec; the Packet size = 1380 Bytes; and
There were 53 packets retransmitted, 748 duplicate acks received, and 675 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 1.52%
S2C throughput test: Packet queuing detected: 36.60%
This connection is receiver limited 12.62% of the time.
This connection is sender limited 2.23% of the time.
This connection is network limited 85.16% of the time.

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

Server 'web100.uvm.edu' is probably behind a firewall. [Connection to the ephemeral port failed]
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
Information: Network Address Translation (NAT) box is modifying the Client's IP address

_daynzy
12-28-2008, 02:46 PM
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 8.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 2.03Mb/s

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

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 137.1 msec; the Packet size = 1380 Bytes; and
There were 110 packets retransmitted, 218 duplicate acks received, and 96 SACK blocks received
The connection stalled 3 times due to packet loss
The connection was idle 1.14 seconds (10.36%) of the time
C2S throughput test: Packet queuing detected: 7.51%
S2C throughput test: Packet queuing detected: 77.83%
This connection is receiver limited 19.2% of the time.
This connection is sender limited 2.23% of the time.
This connection is network limited 78.58% of the time.

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

Server 'web100.uvm.edu' is probably behind a firewall. [Connection to the ephemeral port failed]
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
Information: Network Address Translation (NAT) box is modifying the Client's IP address

Hans
12-28-2008, 06:43 PM
The connection stalled 3 times due to packet loss.

More then likely that's your problem.