?
Solved

OWA 2007 through ISA 2006 fails with Server Error, 501

Posted on 2009-05-16
1
Medium Priority
?
807 Views
Last Modified: 2012-05-07
Problem: OWA 2007 works fine internally(https://CAS/exchange or https://CAS/owa both work - exchange will redirect to owa), but fails with error Server Error, 501  Header values specify a method that is not implemented when trying to access it externally through our ISA 2006 server
We use an external SSL certificate.
Full Error Message:   501 - Header values specify a method that is not implemented.
The page you are looking for cannot be displayed because a header value in the request does not match certain configuration settings on the Web server. For example, a request header might specify a POST to a static file that cannot be posted to, or specify a Transfer-Encoding value that cannot make use of compression.
Setup:

We are coming from an exchange 2003 environment, starting to setup our first exchange 2007 servers.

Exchange 2007 servers, all running Server 2008 SP1, rollup 7:
EDGE
CAS/Hub Transport
MBX
The ISA server is running on server 2003, it is ISA 2006

If I try to access a mailbox that is on a 2003 server, it goes through fine, but if the mailbox is on the 2007 server, I get the error message.

http://support.microsoft.com/kb/942058 did not seem to have any effect on the problem.

In my OWA rule on the ISA server for paths, Im using /      /exchange\ 
in addition to the 4 default ones (external path says <same as internal>, paths are /public/*, /OWA/*, /Exchangeweb/*, /Exchange/*)

Forms based Authentication is turned off on the CAS server, its set to basic or integrated windows authentication.

Thoughts on what to check?
0
Comment
Question by:darazman
1 Comment
 

Accepted Solution

by:
darazman earned 0 total points
ID: 24417590
Okay, so I found my problem.  I dont know if not having SP1 on ISA 2006 played a part in the problem or not, but it was service packed, that alone didnt solve my problem though.  installing the http redirect on the IIS 7 server of the CAS server and setting that up as per:

http://technet.microsoft.com/en-us/library/aa998359.aspx

seemed to do the trick.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article involves a discussion about issues people have when it comes to Client Access in relating to Load Balancing in an Exchange environment which we had ourselves, along with a solution I found to the problem.
In migration, Powershell can be a very crucial tool to achieve success and finalize projects within deadline or even fix issues. X500 or Legacy Exchange DN Attribute can cause lots of issue during the migration
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

585 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question