Re: OWA works from client but not from server
- From: jonjof <boebzer2@xxxxxxxxx>
- Date: Thu, 24 Jul 2008 14:34:08 -0700 (PDT)
On Jul 23, 12:35 pm, v-rob...@xxxxxxxxxxxxxxxxxxxx ("Robbin Meng
[MSFT]") wrote:
Hello Jon,
Thank you for your post.
My name is Robbin Meng, and it is my pleasure to work with you on this
issue!
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:
Recently, the SBS domain users cannot access OWA from the SBS server,
however it works fine from the cleints with same user accounts. It
generates http 400 bad request error if you try log on via any
authenticated user on the Server.
If I have misunderstood your concerns please feel free to let me know.
Depending on the different scenarios, the error message may be one of the
following:
HTTP 400 - Bad Request (Request Header Too Long)
HTTP 400 - Bad Request (Header Field Too Long)
HTTP 400 - Bad Request (Invalid Hostname)
HTTP 400 - Bad Request (Invalid Header)
HTTP 400 - Bad Request (The data is invalid)
HTTP 400 - Bad Request (Invalid URL)
HTTP 400 - Bad Request
Scenario 1:
=======
Users intermittently receive "HTTP 400 Bad Request" messages or some users
receive this error message when logging onto OWA.
The Kerberos ticket created by the front-end server exceeded the maximum
header size that IIS would accept. (The Default limit of IIS 5.0 SP4 is
16KB). This usually occurs when the user is a member of over a hundred
Windows user groups.
There are three registry entries that you can configure to resolve this
issue:
MaxClientRequestBuffer
MaxFieldLength
MaxRequestBytes
For more information about the relationship between the above three key,
please refer to KB920862 and KB310156.
Error message when an Outlook Web Access user tries to access a mailbox in
Exchange Server 2003: "HTTP 400 Bad Request (Request header too long)"http://support.microsoft.com/kb/920862/en-us
How to limit the header size of the HTTP transmission that IIS accepts from
a client in Windows 2000http://support.microsoft.com/kb/310156/en-us
Have you published the OWA to the Internet? If so, are you accessing the
OWA from the SBS server using internal URL/IP or external URL/IP that
generate this error? If the issue occurs using external URL/IP, please
consider Scenario 2.
Scenario 2:
=======
Users received the HTTP 400 error when accessed the OWA from internal via
firewall.
a. Check the Configuration of Firewall on the SBS management console to see
if the WebDav commands were blocked.
b. Known issue when Web site is published through ISA 2004. If you are
using SBS premium edition with ISA 2004 installed, please check KB 925882..http://support.microsoft.com/kb/925882/en-us ;
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
Information Need
==============
1. On the SBS server, open event viewer, please help save the Application
and System log to *.evt and send to me at v-rob...@xxxxxxxxxxxxx
2. If possible, please capture some screenshot when the error messages
appear and send them to me : v-rob...@xxxxxxxxxxxxx
Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.
Thank you for your time and cooperation.
Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! -www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner..
You can locate the newsgroup here:http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
checkhttp://support.microsoft.comfor regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Dear Robbert
I did try reply to your own e-mail address, with the attachments, but
the mail bounced.
Please advise.
With thanks
Jon
.
- Follow-Ups:
- Re: OWA works from client but not from server
- From: "Robbin Meng [MSFT]"
- Re: OWA works from client but not from server
- References:
- OWA works from client but not from server
- From: jonjof
- RE: OWA works from client but not from server
- From: "Robbin Meng [MSFT]"
- OWA works from client but not from server
- Prev by Date: Re: Routing IP cameras to internet
- Next by Date: Re: AntiVirus Software for SBS2003
- Previous by thread: RE: OWA works from client but not from server
- Next by thread: Re: OWA works from client but not from server
- Index(es):
Relevant Pages
|
