Can someone recommend something?

[bushpie]

heres what I got from the SG TCP/IP Analyzer:

TCP options string = 020405b40103030101010402

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) = 62944
RWIN Scaling (RFC1323) = 1 bits
Unscaled Receive Window = 31472
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: 2517.76 kbps (314.72 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1007.104 kbps (125.888 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

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

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

I have tried various settings - these:
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)

When I use the 64240 settings and do the test it reads correctly. Anything above that and I get a 64240 or lower showing in the test.

Went to DSLreports and it reads it correctly for what ever window size I have in the registry, 513920 , 256960, or 128480. I normally use 256960. I'm on Road Runner cable.

I am running windows 2000
cable modem is attached to a 3com 509B nic in the machine.
550Mhz Pent II processor
348 MB ram as reported by windows 2000 and bios

These are my normal registry settings (the test above was done when the settings were set for a window of 128480):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"Tcp1323Opts"=dword:00000001
"EnablePMTUDiscovery"=dword:00000001
"SackOpts"=dword:00000001
"TcpMaxHalfOpen"=dword:00000064
"TcpMaxHalfOpenRetried"=dword:00000050
"GlobalMaxTcpWindowSize"=dword:0003ebc0
"TcpWindowSize"=dword:0003ebc0
"EnablePMTUBHDetect"=dword:00000000

I even tried setting the MTU in the interfaces key.

I've tried various window sizes to see if it would read correctly. I've swapped NICs thinking that something could (tho I doubted it) be possibly wrong. Even replaced the rj45 nic cable with new ones a few times.

Once again:

When I do the test here at SG I get the type of results above for any window size over 64240.

When I do the test at DSLreports it reports the correct window size in the registry.

So what the difference?

[Lobo]

Set tcp1323Opts to 1 and reboot:)

[Lobo]

I see now it is at 1 go here (http://www.speedguide.net/Cable_modems/cable_reg_win2k.shtml) :)

[Lobo]

Or if that fails go to help page below in sig and download Cablenut and install 4.02 (Came out last night and have not updated page yet) before downloading our patch which will give you RWIN of 256960:)

[bushpie]

already tried the SG patch and cablenut. Same thing. It reports properly on DSL reports why not here?

[Lobo]

Try turning off proxy server, tells you how on help page below, 2nd page at bottom:)






REBOOT before taking analyzer test

[bushpie]

Lobo,

the proxy server is not turned on in the settings. Not using the proxy. I'm using a clean install of win 2k. Just tried it on another win2k machine - same thing. connected straight to the cable modem then to the net (thru RR of course). What the heck is going on here. Is something wrong with the SG test?

I did reboot between test and even cleared the cache.

[Lobo]

Do you have RWIN in 3 places on adjuster:)

[bushpie]

Originally posted by Lobo
Do you have RWIN in 3 places on adjuster:)

not using adjuster right now. Used it earlier on one install and got same results. Besides adjuster or not it should not matter if the window registry settings are correct - this is all adjuster does anyway - right? I've done three clean installs today trying to figure this out.

[Lobo]

No the analyzer works fine, but I am lost on this, maybe someone will come along or you could ask in main DSL & Cable forum, sorry:)

[Lobo]

The only thing I can think of is you had some kind of packet loss before and did not get all of patch, follow direction on help page, Cablenuts patch will clean out that part of your registry, then download ours:)

[bushpie]

Originally posted by Lobo
The only thing I can think of is you had some kind of packet loss before and did not get all of patch, follow direction on help page, Cablenuts patch will clean out that part of your registry, then download ours:)

Ok here what I did. I tried the cable nut patch earlier today. Same results. Don't think I got a corrupted download but i got it again a few minutes ago. used it, cleaned out every thing. put the SG patch back in, same results.

OK since this is a clean install with nothing else installed except for the OS, I restored the original default registry from the install. I always save the installed registry when I install a clean OS because that way I can bring it back real quick if installing software screws something up when I start setting the machine up with software. In the "clean install registry" which I bought back there were none of these settings because they do not install by default. I then used the SG patch. Same results.

Went again to the DSLreports page and checked and the registry window size of 256960 was reported by them.

I next went to my second win2000 machine and removed and restored the registry settings with the speed guide patch. Results were the same.

I then for both machines manually removed the sg settings, and manually put them in by hand. Same results. DSLreports shows fine but SG doesn't.

This tends to lead me away from the registry settings as a problem and more towards something else.

Going nuts here.

gonna try my windows xp test machine in a bit as soon as the clean install on it gets done.

[bushpie]

OK got the XP machine on line now - same conditions except for the OS.

Same problem exists. Either there is something wrong with RR or the SG test is wrong. You said its working OK. I've used it in the past and it worked OK. What I can't figure out is why does DSL reports show the correct window size entered in the registry and SG doesn't?

[lance-tek]

you may have a key in the reg that isn't supposed to be there, I know I have made reg keys and they will cause conflict if I have then different than the adjsuter settings....... just a thought

[bushpie]

Originally posted by lance
you may have a key in the reg that isn't supposed to be there, I know I have made reg keys and they will cause conflict if I have then different than the adjsuter settings....... just a thought

i had considered this also. But with serveral clean installs on this one machine and with clean registries each time, and then using another machine and the same thing happens, then a clean install of windows xp on a third (test) machine. Then another clean install on the original machine. I'm of the conclusion that there is not a problem on my end. The problem is either with the SG test (I doubt it tho) or with Road Runner.

If the problem is with Road Runner I wonder what would cause the window size to report correctly at DSLreports and incorrectly at SG?

[bushpie]

Just a few minutes ago I did both the DSLReports tweak test and the SG test. My window size is currently set in the registry at 256960

The results from www.dslreports.com:

(view at http://monitor.dslreports.com/tweak/block:d53254?service=cable&speed=2000&os=winXP&via=normal)

Your Tweakable Settings:
Receive Window (RWIN): 256960
Window Scaling: 2
Path MTU Discovery: ON
RFC1323 Window Scaling: ON
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL: 67
(less any hops behind firewall)
TTL remaining: 46

Example 146000 byte download
Actual data bytes sent: 156220
Actual data packets: 107
Max size packet sent: 1500
Max size packet recd: 1500
Retransmitted data packets: 7
sacks you sent: 10
pushed data pkts: 2
data transmit time: 1.695 secs
our max idletime: 268.9 ms
transfer rate: 69555 bytes/sec
transfer rate: 556 kbits/sec
This is not a speed test!
transfer efficiency: 93%

ICMP (ping) check
Minimum ping: 53 ms
Maximum ping: 83 ms
Ping stability:
53 62 57 72 54 58 68 59 83 72

10 seconds later I did the SpeedGuide test. The results are below with the same setup that I used for the www.dslreports.com test.

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) = 60352
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 15088
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: 2414.08 kbps (301.76 KBytes/s) @ 200ms
Your RcvWindow limits you to: 965.632 kbps (120.704 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

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

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000


www.dslreports.com reports the correct window size entered in the registry. If I change the window size www.dslreports it properly.

Speedguide does not report the window size correctly. As i said some where in the beginning of this post, Ths SG test is not reporting the correct window registry size for anything over 64240. I'm not sure here but it looks like SG is having a couple of problems with win2000 and winxp. However I dont believe this. But how else can you explain the differences?

I know the connection is working OK. I've used three different machines, two of them with brand new clean installs of windows 2000 and XP. I re-installed win2000 on one of the machines 7 times yesterday - clean install each time. Started with perfectly clean registries each time and tried the SG patch, cablenut, and manual entry as well.

I know its not the connection cause my d/l speeds haven't changed. If the window size was really messed up the d/l speed would be affected some, but this is not a true indication because i've been able to set the window size to 65535 and still gotten the same speed d/l that I did before. This makes since because with 2mb sec cap 65535 is more than enough and still have bandwidth left over.

My conclusion:

facts:

1. The registry window size reports correctly from DSLreports.
2. The registry window size does not report correctly from Speed Guide. (not for me - may work for you but don't know why)

so my initial conclusion is a server incompatability or java compatability problem between the SG test and my win2000 , winXP machines.

and to further explain:

these are the speed tests I did from www.pitstop.com:

from www.pitstop.com

DSL/Cable Modem bandwidth test:
Text Block Size 200 KB
Download Time 591 ms
Receive Buffer 256960 bytes
Transmission Speed 2707 Kb/s

T1 bandwidth test.
Text Block Size 500 KB
Download Time 1463 ms
Receive Buffer 256960 bytes
Transmission Speed 2734 Kb/s

T3 bandwidth test.
Text Block Size 1000 KB
Download Time 3485 ms
Receive Buffer 256960 bytes
Transmission Speed 2296 Kb/s

Extreme bandwidth test.
Text Block Size 5000 KB
Download Time 20670 ms
Receive Buffer 256960 bytes
Transmission Speed 1935 Kb/s

upload test:
Upload Speed 319 Kb/s

You see the Receive Buffer size? it's the same as my registry set window size,256960, which it should be on this test.

My final conclusion: My stuff is working properly. There is an incompatability between my connection and SG or the SG test is broken. How else can it be explained?

[bushpie]

Guess no one can figure this one out. Thanks to those that tried to help.