Proxomitron reduces RWIN to 32768

[Peakaboo]

Two things I noticed in looking back on this thread:
1)

mambo Wrote:Hi! It's quite strange, but after upgrading Sidki's filters SpeedGuide test shows the correct RWIN, but just after reloading that page and permit "tame redirect" on page "Connection parameters retrieved".

Sidki's latest filter set (6/9/05) & his 10/16/05 update to the 6/9/05 filter set can be found here: http://www.geocities.com/sidki3003/prox-down.html

can anyone confirm what mambo did as posted on page 4 of this thread 3rd post from top?

2) Mike has been successful at getting the correct rwin from tcpip analyzer when he sticks a buffer like bfilter in passive mode or analogx proxy in between proxo and his browser.

I find it interesting that some with xp sp2 pro have the problem like z12 (Mike) and others do not see this issue like hpguru and that no other os except xp home with sp2 is reporting this issue.

Personally, I'm seeing scaled rwin of 128480 which is well above the 32768 presumed limit of proxo on a win95 machine. I'm seeing proxo open on normal browsing 4 to about 13 tcp connections.

*******************************************

Seems like given a certain config --> xp sp2 is reading the slower rwin of proxo at 32768 (if proxo in fact has this internal rwin) and the tcpip header is picking up this slower rwin if nothing buffers or intercedes.

In a way this makes sense to me because proxo was built during dial-up and probably not with broadband in mind - if the slowest link in the chain is at 32768 (proxo internal rwin) then I think I read somewhere that servers and xp throttles back to the lowest rwin in the chain. I'll try and find the link I think it was a discussion of 2003 server.

The major question which may hold the answer to a solution is what is different between the config setup of z12 vs hpguru's set up. Both are using xp pro sp2 and z12 experiences the rwin slow down while hpguru does not.

Occam's Razor: says if possible compare the two setups to isolate any major differences. Test the differences one by one till a solution is found. Sounds easy in theory anyway

I'd like to think Scott is probably smiling down and saying... all you have to do to resolve this is...