Can't access one website (W2K)

[WinDude]

Hi all,

I found this site when searching for win2k support for an odd problem I am experiencing and hoping someone here can help. There is one (and only one that I've found) website that I cannot access from my browser -- www.mfgquote.com . It used to work, but then suddenly stopped some months ago. The connection just times out. I get the same problem from Firefox and IE on Win2k SP2. I also tried accessing it by IP address, but still no luck.

On that same hard-drive, I have it setup as dual-boot with Linux, and I can access the site from that O.S. (although that site uses some plug-ins that I can't use under my Linux system).

I also have another old hard-drive that has Win2k on it, and I can access the website with no problem on the same machine with the same exact hardware.

So it has to be a problem with Win2k and probably it's network-access software.

I have tried disabling all virus scanners and spyware scanners, but no difference.

Any clues where to go about finding this problem? I am really trying to avoid re-installing Win2k at this point, since it usually causes confusion with my Linux setup and I can't afford the downtime while I'm travelling for the next couple months. I can connect both hard-drives simultaneously (so I can access both Win2k installations simultaneously), so perhaps there are some files I should be comparing?

Thanks,
-Neil.

[josefz]

Hi Neil,

see if this helps: <a target="_blank" href=http://winhlp.com/WxNetwork.htm#Cannot_browse_some_web_sites> Cannot browse some web sites</a>.

I know, this is intended for XP, but...

[WinDude]

Found the issue indirectly thru this info/page you directed me to. Thanks. Here's the details....

That page talked mostly about MTU and how to change it using a DRTCP tool. Setting it to 1400 or even 500 did not solve the problem. However, it also pointed to a TCP/IP analyzer at www.speedguide.net. That was useful in seeing the changes.

So what I did was to use the DRTCP tool on both installations of Win2K -- the one that can access that website and the other that cannot -- to compare the settings. There were some differences, and setting the non-working installation's settings to the same as the working one solved the problem. On the non-working installation, these settings were ...
- Tcp Receive Window: 65536
- Window Scaling: Yes
- Time Stamping: No

On the working installation, these were unset to set to "Default".

I won't claim to know what these mean, but changing them solved the problem.

Much thanks!
-Neil.