I've also found this in IIS 6.0 Server Log:
2006-06-01 18:56:58 10.0.0.220 POST /LxServiceStateServer/DataServices.asmx
- 80 - 10.0.0.71 HTTP/1.1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+1.1.4322.2032) 200 0 64 25 678
The strange thing here is that the http status code is 200 (seems to be
fine), yet the win32 status code is 64 (something strange here =)
And here is the tcp trace from the client side:
socket (2764) connected
socket (2764) receiving data asynchronously [len=4096]
socket (2764) set one of its options [level=SOL_SOCKET, optname=4101]
socket (2764) determined its local name [name=10.0.0.71:1828]
socket (2764) determined its peer's name [name=10.0.0.220:80]
socket (2764) sending data synchronously [len=394]
socket (2764) sent 394 bytes of data
POST /LxServiceStateServer/DataServices.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 1.1.4322.2032)
Content-Type: text/xml; charset=utf-8
SOAPAction: "
http://ns/EmployeesAndDepartmentsList"
Content-Length: 308
Expect: 100-continue
Connection: Close
Host: ns
Cookie: ASP.NET_SessionId=nps1rpfw0wndz4az1kiv0sqb
socket (2764) set one of its options [level=SOL_SOCKET, optname=4101]
socket (2764) received 25 bytes of data
HTTP/1.1 100 Continue
socket (2764) receiving data asynchronously [len=4071]
socket (2764) sending data synchronously [len=308]
socket (2764) sent 308 bytes of data (Incomplete last line)
<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"><soap:Body><EmployeesAndDepartmentsList xmlns="
http://ns" /></soap:Body></soap:Envelope>
socket (2764) will be closed when outstanding asynchronous calls finish
socket (2764) could not receive data - 995 (?]
socket (2724) created [family=AF_INET, type=SOCK_STREAM,
protocol=IPPROTO_TCP, dwFlags=WSA_FLAG_OVERLAPPED]
socket (2724) connecting synchronously [name=10.0.0.220:80]
socket (2724) connected
socket (2724) receiving data asynchronously [len=4096]
socket (2724) set one of its options [level=SOL_SOCKET, optname=4101]
socket (2724) determined its local name [name=10.0.0.71:1869]
socket (2724) determined its peer's name [name=10.0.0.220:80]
socket (2724) sending data synchronously [len=382]
socket (2724) sent 382 bytes of data
POST /LxServiceStateServer/DataServices.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 1.1.4322.2032)
Content-Type: text/xml; charset=utf-8
SOAPAction: "
http://ns/ReceiveMessages"
Content-Length: 296
Expect: 100-continue
Connection: Close
Host: ns
Cookie: ASP.NET_SessionId=nps1rpfw0wndz4az1kiv0sqb
socket (2724) set one of its options [level=SOL_SOCKET, optname=4101]
socket (2724) received 25 bytes of data
HTTP/1.1 100 Continue
socket (2724) receiving data asynchronously [len=4071]
socket (2724) sending data synchronously [len=296]
socket (2724) sent 296 bytes of data (Incomplete last line)
<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"><soap:Body><ReceiveMessages
xmlns="
http://ns" /></soap:Body></soap:Envelope>
socket (2724) will be closed when outstanding asynchronous calls finish
Seems that after 64 error it is impossible for client to resolve server name
neither read/write from socket, neither create new sockets to work with the
current server unless the client application is completely restarted.