I have implemented a single Exchange 2007 and began migrating a few test users only to find that they get a http 400 error after entering their UN+PW.I have looked through the event viewer and cant find anything to point to an issue, does anyone have any ideas?Happy New Year!

Hi,Does this issue happens only internal or also external ?Please check the url's you configured on the CAS server, when incorrectly configured this can cause this issue.Also try to run the following Powershell command:test-OwaConnectivity -URL:https://mail.yourdomain.com/owa-MailboxCredential:(get-credential yourdomain\username)And post the output of the command.Did you also checked the security logs for errors ?Regards,Johan blog: www.johanveldhuis.nl

Are you hittinghttps://server.domain.com/owa orhttps://server.domain.com/exchange.Is the problem happening both internally and externally?

Hi, Cause of HTTP 400 may have a lot of possibilities, please follow the steps below to narrow down the issue. 1. Please check properties of OWA virtual directory. Whether IP address of that computer has been listed in IP address and domain name restriction (OWA-Properties-Directory Security) 2. Check if you have installed other ISAPI Filters under default web site. If yes, then please remove it. 3. Please check if the issue will occur both intranet and internet. Is there any firewall in front of the network? 4. Please check if you have redirection settings on default web site. 5. What is your authentication method for OWA? If you have ISA, then please check the authentication method there. 6. Please run Get-exchangecertificate |fl to check if you have certificate installed for IIS services. Besides, Id like to know if you have Exchange 2003 FE or Exchange 2003 BE in the network? Regards, Xiu

Johan Veldhuis said: Also try to run the following Powershell command:test-OwaConnectivity -URL:https://mail.yourdomain.com/owa-MailboxCredential:(get-credential yourdomain\username)And post the output of the command.Johan,Thanks for the response, the problem is happening internally and externally.it even happens from the server itself.here is what was recieved from the power shell;Test-OwaConnectivity : A parameter cannot be found that matches parameter name'System.Management.Automation.PSCredential'.At line:1 char:21+ test-OwaConnectivity <<<< -URL:https://server.domain.com/owa-MailboxCredential:(get-credential DOMAIN\username)Thanks,Edvin

Vinay Pal Singh said: Are you hittinghttps://server.domain.com/owa orhttps://server.domain.com/exchange.Is the problem happening both internally and externally?HI Vinay,I have used both combinations, to no avail.Thanks,Edvin

Xiu, This is a migration from a single Exchange 2003 Enterprise Server to Exchange 2007 Enterprise on Windows 2008 STD. Both servers are behind a firewall appliance and I havent played around with any of the IIS7 configs.There arent any redirections and the problem happens everywhere.Under IIS the Default Website has Anonymous Authentication and owa has Basic AuthenticationI have only the default certificates installed.Thanks,Edvin

Hi, From Exchange Server, please try to launch IE and then type http://localhost/owa to check if you can access OWA. Besides, please run ExBPA to have a health scan and then post the detail report here. Meanwhile, We shall check IIS logging to get more information for further troubleshooting. Please open IIS Manager, navigate to the Default Web site ,find OWA .In the right result pane, find logging, please remember the log directory. XWEB: Diagnostic Logging Levels for OWA Defined in the Exchange Administrator Program http://support.microsoft.com/kb/246248 Default settings for Exchange-related virtual directories in Exchange Server 2007 Hope it helps. Xiu

Hi,How is the issue now?Regards,Xiu