Wierd HTTP protocol behavior on the internet between Win 2K and Windows XP Prof

[CK]

Hi

I'm seeing a wierd behavior with Win 2K and Windows XP Professional when
accessing a HTTP server. The web application takes around 6mins to load
because of complex computations and database acess. When i acess the web
application from inside the firewall everything works fine on Win 2K and XP
Prof, but when i acess the same server from outside the firewall from
internet the Win2K machine never gets the HTTP response, whereas the XP
machine works fine. I checked the server logs and i can see that after 6
minutes the web server sends out response html page to the client, but it
never reaches the client browser on Win 2K. The browser shows that it is
still waiting for the server to respond. What could be happening here? Why
XP machines works but not the Win 2K. Both machine have same version of IE
browser. I even tried with Netscape browser and the results are the same. It
looks like it has nothing to do with the browser version but it definitely
has got something to do with the networking layer implemenation on Win 2K
and XP.

We increased the firewall timeout to 15mins or so, and with the trace i
noticed browsers do send HTTP/1.1 request with Connection: Keep-Alive
header.

Any suggestions or ideas will really help me a lot.

Thanks
Jey

 

[Brian Oakes [MSFT]]

Make sure the versions of IE are identical, and then get a client side
netmon trace. We need to look at the http gets to make sure they are the
same and the responses etc.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.