SG Broadband Community

Can Someone Look over My TCP/IP Analyzer And See If Its Good For My @Home Cable


TCP options string = 020405b4

MTU = 1500
MTU is fully optimized for broadband.

MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.

Default Receive Window (RWIN) = 49152
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 49152
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN 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)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:
Your RcvWindow limits you to: 1966.08 kbps (245.76 KBytes/s) @ 200ms
Your RcvWindow limits you to: 786.432 kbps (98.304 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = OFF

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

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = OFF

IP type of service field (RFC1349)= 00000000




16263 connections tested since 03.10.2001.
Analyzer version: Beta 0.99

DISABLE PROXY, help thread has directions

I Typed regsvr32 -u ahiehelp.dll Already So Many Times
If Thats Not How Then Plz Just Explain On This Thread How To Cause I Don't See Anything Else About Disabling Proxy

OK speedo, from help thread: Then go to (This is for EVERYONE , even @home users) Control panel, internet options, Connections tab at top, LAN Setting's at bottom, and uncheck everything in this box, proxy and auto detect, Nothing sould be checked, REBOOT

Try setting RWIN to 256960. For best results, it should always be an e-v-e-n multiple of MaxMSS.

Where does even multiple come into it, analyzer saids multiple, I don't use multiple and mine works fine?

It's something I recall reading in the SpeedGuide site or on one of the former TweakFiles forums. If I'm wrong, thanks for correcting me. I'm always willing to learn something new.

From Speedguides Terms and deffinitions:

DefaultRcvWindow, (TcpWindowsize in win2k)or simply RWIN is a buffer that's negotiated between the client and server. Since all TCP/IP traffic is transmitted in packets, if the RWIN value is not a multiple of MSS fragmented packets might be sent whenever the buffer fills up. Some of the newer TCP/IP implementations will try to avoid fragmentation of packets, by simply disregarding the remainder of RWIN which is smaller than a segment, then checking every time and adding other partial segments. Either way, you are going to avoid a couple of CPU cycles by sticking to the standards and recommendations of the Internet Society, and making RWin a multiple of MSS.


I see multiple but not even multiple, anyway whatever works best for people

Thanks for the reply.

How About Now
Is This Good?

TCP options string = 020405b40103030201010402

MTU = 1500
MTU is fully optimized for broadband.

MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.

Default Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 64240
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:
Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4111.36 kbps (513.92 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




25632 connections tested since 03.10.2001.
Analyzer version: Beta 0.99

Looks fine