http 400 errors and timer_entity body errors

We are running IIS 6 on W2k3 server with SP2
Have found numerous examples of people with similar issues but no resolution

http://www.issociate.de/board/goto/900772/sc-status_=_400___ ____sc-win32-status_=_64___What_causes_this?.html

http://forums.asp.net/p/966636/1765928.aspx#1765928

http://forums.iis.net/t/1080546.aspx

Happens with .net 2.0 postback to specific users and is reproducable.
Browsers vary. Does seem to be network specific. Have one user on a work
network that can reproduce (using multiple browsers Mac, IE, Firefox etc).
He can take the same pc, browser combo home, plug into his home network and
everything functions without an issue or error.

User request HTTP POST to login or submit a form and eventually is returned
a page cannot be displayed error. On the IIS logs we see 400 errors 400 0 64

In HTTPERR logs we see Timer_EntityBody errors. We have thousands of users
using the app without any issues (affects approx .02% of users)

We have experimented with various registry settings to disable MTU
discovery, force MTU to 576 etc etc, but that has not helped. Have
experimented with numerous variables at application level but seems to be
IIS/http/network related.
Any thoughts?

Re: http 400 errors and timer_entity body errors

> Happens with .net 2.0 postback to specific users and is reproducable.
> Browsers vary. Does seem to be network specific. Have one user on a work
> network that can reproduce (using multiple browsers Mac, IE, Firefox etc).
> He can take the same pc, browser combo home, plug into his home network
> and
> everything functions without an issue or error.

Can you get packet captures (preferably at both ends) using a tool like
Wireshark, of this particular user, both when he/she is having the problem,
and when they are not? We can then compare the differences WRT to the lower
level network traffic to see what the problem is.

It does not appear to be an application layer issue /if/ the user has the
same problem with multiple browsers.

Cheers
Ken


"supercal5" wrote in message
news:3DC4F31A-281E-49F9-9F43-2CDBA9284DA1@microsoft.com...
> We are running IIS 6 on W2k3 server with SP2
> Have found numerous examples of people with similar issues but no
> resolution
>
> http://www.issociate.de/board/goto/900772/sc-status_=_400___ ____sc-win32-status_=_64___What_causes_this?.html
>
> http://forums.asp.net/p/966636/1765928.aspx#1765928
>
> http://forums.iis.net/t/1080546.aspx
>
> Happens with .net 2.0 postback to specific users and is reproducable.
> Browsers vary. Does seem to be network specific. Have one user on a work
> network that can reproduce (using multiple browsers Mac, IE, Firefox etc).
> He can take the same pc, browser combo home, plug into his home network
> and
> everything functions without an issue or error.
>
> User request HTTP POST to login or submit a form and eventually is
> returned
> a page cannot be displayed error. On the IIS logs we see 400 errors 400 0
> 64
>
> In HTTPERR logs we see Timer_EntityBody errors. We have thousands of
> users
> using the app without any issues (affects approx .02% of users)
>
> We have experimented with various registry settings to disable MTU
> discovery, force MTU to 576 etc etc, but that has not helped. Have
> experimented with numerous variables at application level but seems to be
> IIS/http/network related.
> Any thoughts?
>