Re: OWA 2007 400 bad request

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

it's happened again. Logon dialog box, then the logon form, then HTTP 400
Bad Request. No other info. Only the "This error means that Internet
Explorer was able to connect to the web server, but the webpage could not be
found because of a problem with the address".

I tried going to https://server.domain.co.nz/owa/auth/ and got 403
Forbidden.

Then going back to https://server.domain.co.nz/owa/auth/owaauth.dll gives
the HTTP 400.

Thanks, Neal.



"Neal" <neal@xxxxxxxxxx> wrote in message
news:efrerZ5hHHA.4904@xxxxxxxxxxxxxxxxxxxxxxx
I had an Exchange 2003 behind a firewall (not ISA). All was OK.

I added an Ex2007 (which will take over once I move everything to it and
decommission). All roles on one box. I changed the firewall to point
port 80 and 443 to the new server.

I just tried it again to check for other error messages and it works now!
I didn't change anything. If it happens again, I'll collect the error.

Thanks, Neal

"Steve Antonio [MSFT]" <steveant@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:qoov239gpscp0aesoucck4qk3vlt6392p4@xxxxxxxxxx
What Version of Exchange? Are you using a FE/BE configuration?

Are you using ISA to publish OWA or is there a firewall between server
and the external client?

When you get the HTTP 400, do you also see any of the following errors
in parens after the "Bad Request" message?

Request Header Too Long
Header Field Too Long
Invalid Hostname
Invalid Header
The data is invalid
Invalid URL

Steve Antonio, CISSP
Microsoft Exchange Support

On Thu, 26 Apr 2007 11:16:09 +1200, "Neal" <neal@xxxxxxxxxx> wrote:

From on the LAN, I can get to OWA all OK.

From an external location, I first get a dialog box popping up. I enter
domain\name and my password, then get to the new OWA logon screen. I
then
enter my domain\name and password again in the form but get
HTTP 400 Bad Request for the page
https://server.domain.co.nz/owa/auth/owaauth.dll

Any ideas?
Thanks, Neal





.

Relevant Pages

  • RE: OWA works from client but not from server
    ... Recently, the SBS domain users cannot access OWA from the SBS server, ... the error message may be one of the ... HTTP 400 - Bad Request ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA works from client but not from server
    ... Recently, the SBS domain users cannot access OWA from the SBS server,   ... the error message may be one of the ... HTTP 400 - Bad Request ...
    (microsoft.public.windows.server.sbs)
  • Re: How to write something to a html textfield and send it?
    ... > No need for controlling any particular browser. ... I'm not familiar with HTTP user ... and building the request in your program. ... The server doesn't know anything about a textfield; ...
    (comp.programming)
  • Re: undefined function error if I use a fully-qualifed include
    ... >>obtains filename.php by performing an HTTP request to the specified ... which specifies "Go and get this resource using the HTTP protocol". ... PHP doesn't ... off to Apache to satisfy. ...
    (comp.lang.php)
  • Re: Attributes that Update during Computer logon
    ... prior to logon but the learning curve for our users is what may be difficult ... You mention that the computer may request its password to be reset, ... in reviewing the attributes for a Computer object (using a LDAP ... Finally you mentioned that "lastLogon" was not replicated but is the ...
    (microsoft.public.windows.server.active_directory)