Hi,Could someone please advise.I live in the Uk with cable 10meg down,no advertised speed up,but constantly getting 350 up.Tried advice regarding TCP optimzer,moved modem as far as poss,ran adware,spybot,ccleaner.Still getting awful speeds as stats show.
Any help regarding UMB also. Not sure what it is, or does,told this might cause this inconsistancy.
Thanks.........

stats
TCP options string = 020405b40103030201010402

MTU = 1500
MTU is fully optimized for broadband.

MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.

Default TCP Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled TCP Receive Window = 64240

RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4) <-- current value
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 10278 kbps (1285 KBytes/s) @ 200ms
Your TCP Window limits you to: 4111 kbps (514 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 54 hops
TTL value is ok.

Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 00000000 (0)


Tracing route to www.l.google.com [64.233.183.99]
over a maximum of 30 hops:

1 9 ms 6 ms 6 ms 10.177.0.1
2 6 ms 9 ms 6 ms 80.193.192.1
3 8 ms 9 ms 7 ms pc-62-30-250-54-ha.blueyonder.co.uk [62.30.250.5
4]
4 10 ms 9 ms 12 ms 194.117.136.146
5 17 ms 9 ms 9 ms 194.117.136.162
6 9 ms 7 ms 9 ms 194.117.148.251
7 7 ms 19 ms 10 ms 72.14.238.244
8 16 ms 16 ms 16 ms 209.85.248.80
9 24 ms 37 ms 18 ms 209.85.248.87
10 18 ms 19 ms 19 ms 64.233.175.246
11 18 ms 19 ms 17 ms 72.14.233.81
12 18 ms 31 ms 18 ms 216.239.43.30
13 19 ms 20 ms 19 ms nf-in-f99.google.com [64.233.183.99]

Trace complete.

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

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

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 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 = 179.8 msec; the Packet size = 1460 Bytes; and
There were 1 packets retransmitted, 116 duplicate acks received, and 18 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 1.92%
S2C throughput test: Packet queuing detected: 3.09%
This connection is network limited 99.83% 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 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is not behind a firewall. [Connection to the ephemeral port was successful]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End