Exchang 2007 OWA

slvtech
slvtech used Ask the Experts™
on
I just set up exchange 2007 and am having issues with owa. I can connect initially but when I put in the username and password it comes up with HTTP 400 bad request. Any help would be appreciated!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Alan HardistyCo-Owner
Top Expert 2011

Commented:

Author

Commented:
I disabled basic authentication and enabled forms based authentication. Now it says my username and or password is wrong.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Did you read the entire thread, or just the first post - the solution that worked (and was the accepted solution) was to remove and reinstall OWA.  Look further down the thread.  I'm not guaranteeing this will work, but it did for this question.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Also you can try re-applying the Rollup update that you have. As of now Rollup update 9 is the latest one... you can try applying the same... you can dowload it from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=55320be2-c65c-48bb-bab8-6335aa7d008c

Author

Commented:
I read the entire thread and I removed owa and rebuilt it. Now when I use basic authentication it lets me in but when I try to send an email it says, "Microsoft Exchange issued an unexpected response (404)." If I use forms based authentication I cannot log in at all.
Alan HardistyCo-Owner
Top Expert 2011

Commented:

Author

Commented:
I installed rollup 9 and am having the same problem.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Please try the following.
Extract from http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/5c3b9041-a479-4979-a176-a11e8cbfc55f
After research, and much head-scratching, it turns out that the problem occurs if the URL used to access "OWA" does not exactly match the external URL configured in "Exchange 2K7".  This explains the problems that other people reporting this issue elsewhere have experienced, where the problems seem to have gone away after disabling and re-enabling "Outlook Anywhere" (and re-entering the external URL).

So, if you're experiencing this problem, here's a suggestion:
1)  Fire up the "Exchange Management Console"; expand "Server configuration" and select "Client access".
2)  On the task panel on the right, you should have the option to "Disable Outlook Anywhere" - click on that.
3)  Once the task has completed, you should have the option to "Enable Outlook Anywhere" - click on that.
4)  You will be asked for the external URL - type in exactly the URL you wish your users to use (including any port number, if you're not running on the standard SSL port of 443).  E.g., "https://server.domain/" (you don't need the "/OWA" etc. on the end) or "https://server.domain:port/".
5)  Once that task has completed, retry your external access.

Your mileage may vary, but at that point our access worked.  If I change the external URL to any of the other possible alias names for our server (there are a few), everything returns to "HTTP 400" errors.

Author

Commented:
when I enable outlook anywhere and try to put in https://mail.domain.net I get the error that it is not a valid hostname.

Author

Commented:
looks like I had to leave the https part out and just put in mail.domain.net then it took, but I am still getting the http 400 errors from external computers.

Author

Commented:
I find this odd but this is what I just did. I tried using https://mail.domain/owa and when I tried to log in I got the HTTP 400 error. Then I logged in with the https://ipaddress/owa and I got in just fine. What is going on with that?
Alan HardistyCo-Owner
Top Expert 2011

Commented:
What did you set the certificate up using?
If you used the IP Address, then you need to re-issue the certificate.

Author

Commented:
It is the default issued certificate.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Can you opne up IIS on the server and then select the server in the right-pane.  Then on the Feature/ Content view area, double click on the Server Certificates and see what it says.

Author

Commented:
What info do you need?
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Is the name on the cert an IP address or the FQDN that you are trying to access?

Author

Commented:
If I go under server certificates the name is Microsoft Exchange.

Author

Commented:
Could there have to be a different port open on the firewall??
Alan HardistyCo-Owner
Top Expert 2011

Commented:
The firewall needs port 443 opened.
For the certificate, the name of the certificate should say something like mail.yourcompany.com. (see attached image)
If not - you will need to create a new certificate.

2007-Certificate.jpg

Author

Commented:
no it just has two the say microsoft exchange under the name column.

Author

Commented:
What do I need to put in for OU?

Author

Commented:
When creating a new cert that is.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
mail.yourcompany.com or whatever you wish to use as the FQDN that is setup in DNS so that the FQDN points to your server.

Author

Commented:
I created a self signed cert. Now how do I apply it.
Alan HardistyCo-Owner
Top Expert 2011

Commented:
Here is a full run down of Certificates in Exchange 2007 from Simon (Mestha) one of EE's leading Exchange Experts.
http://blog.sembee.co.uk/archive/2008/05/30/78.aspx 

Author

Commented:
can I just set up owa to work over http instead of https?
Co-Owner
Top Expert 2011
Commented:
Yes - uncheck the Require Secure Channel in the OWA virtual directory properties in IIS.

Author

Commented:
The MX records through Godaddy were set up wrong. Once I got them setup right everything works great through https. It was weird because it doesn't affect http for OWA just https.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial