The source for the problem was an wrong entry in the MTU-Value for the network.
We adjust the value with a program called "dr. tcp" and everything works perfectly
Thanks RedK for your suggestions
Main Topics
Browse All TopicsHi experts,
we have a problem with an ASP.NET 2.0 application running on a Windows 2003 Server (SP1) os with IIS6.0.
When using the page from the local network everything works fine. The same with most of our customer networks.
However when using the page from certain customer networks we receive an HTTP 400 Bad Request error. This occurs on just a few pages when clicking on asp buttons causing a postback.
The IIS logfiles look like this:
2006-07-24 08:54:00 W3SVC221004838 192.168.8.10 POST /kvp/Suggestion.aspx - 80 - 62.2.135.98 Mozilla/4.0+(compatible;+M
The HTTPERR logfile shows the following entries:
2006-07-24 08:54:20 62.2.135.98 14442 192.168.8.10 80 HTTP/1.1 POST /kvp/Suggestion.aspx - 221004838 Timer_EntityBody DefaultAppPool
Any help is appreciated! Thank you!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
we recently had a similar problem, and I will say that this one is very tough to diagnose. The problem was created by our ISP adding a new switch and lowering the MTU to 1500. This should be acceptable and was for all regular internet traffic. It only failed on websites that where SSL encrypted. To correct the problem we changed the MTU on the router interface to 1450(I believe) and everything started working properly.
Business Accounts
Answer for Membership
by: RedKelvinPosted on 2006-07-25 at 21:11:30ID: 17181329
The microsoft description for a timer_entitybody error is
om/kb/8864 61/ om/newsgro ups/defaul t.aspx? dg= microsoft. public.ine tserver.ii s&tid=7ae2 9089-fa57- 4ce1- 8737- fd2c070b15 58&p=1
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. Initially, the limit of this timer is set to the ConnectionTimeout value (typically 2 minutes). Each time another data indication is received on this request, the HTTP API resets the timer to give the connection two more minutes (or whatever is specified in ConnectionTimeout).
An entry in the httperr log showing Timer_EntityBody indicates IIS did not receive any data from a client request and the request timed out (as determined by the connection timeout metabase property). Client requests with large content length headers can cause this error.
see if these are any help
http://support.microsoft.c
http://support.microsoft.c
Hope that is some help
RedK