sc-status = 400 sc-win32-status = 64 What causes this?

I have a user posting to a page. They are going fine, even posting on the
page. At a particular point, they click a button to do a post and the
browser just hangs. When I look in the W3SVC1 log file, I see:
2005-07-28 14:28:52 10.28.98.130 POST
/GPCStoreFront/WebForms/PartInquiry.aspx - 80 - 10.120.198.2
Mozilla/4.0+(compatible;+MSIE+5.5;+Win32) 400 0 64



If I look in the HTTPERR log file, I see the related entry:

2005-07-28 14:28:52 10.120.198.2 20689 10.28.98.130 80 HTTP/1.0
POST /GPCStoreFront/WebForms/PartInquiry.aspx - 1 Timer_EntityBody
DefaultAppPool



My understanding is the 400 means bad request and that the 64 means "The
specified network name is no longer available.". What causes this?

And according to MS, the Timer_EntityBody means:

"The connection expired before the request entity body arrived. When it is
clear that a request has an entity body, the HTTP API turns on the
Timer_EntityBody timer. The limit of this timer is initially set to the
ConnectionTimeout value (normally 2 minutes). Each time another data
indication is received on this request, the HTTP API resets the timer to
give the connection an additional 2 minutes (or whatever is specified in
ConnectionTimeout)."



What does all this mean? Three weeks ago, the user was not having this
problem and now they are. I believe this is an environmental/network
problem because I don't have it. I can do the exact same functionality they
are and mine works fine. I also have a handful of other users doing this
exact same functionality and it works just fine for them too. Also, this
post never makes it back to my asp.net code.

Any help would be appreciated.

Thanks.

Hi Joe,

I have the same problem as yours.
I access my site at my home and all works fine.
When I try to access the site at work it hangs.
Did you find a solution to the problem?

Thanks,

Alexandre