We have two web service machines. Call one WS1 and the other WS2. They are
seperated by a firewall. WS1 handles web service calls and also calls web
services provided by WS2. Both machines do not get updated or restarted very
often. The problem is after some period of time, the web service call from
WS1 (within the ASP.NET process) to WS2 hangs and times out.

If I go to WS1 and open IE, I can get the WSDL from WS2, and if I use
another client on WS1 I can actually make the web service call successfully
to WS2 that fails within WS1 ASP.NET process. If I restart the WS1 ASP.NET
process, it starts working again.

I put in a web page that will be housed within the ASP.NET process on WS1.
It allows me to enter URLs and allows me to specify HTTP or TCP. When WS1
ASP.NET process gets into this state, I can enter the URL to WS2 and specify
HTTP, and it gives me the timeout. If I specify TCP it works. If I specify
any URL other than WS2, and specify HTTP or TCP, it works. So it seems
something in the HTTP library gets deadlocked and its associated with a
specific URL.

At first I thought it might be HTTP keep-alive. I configured IIS on WS1 and
WS2 to not use HTTP keep-alive and it continued to show up.

Any ideas?

TIA.
JD