[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 802
  • Last Modified:

OWA 2007 through ISA 2006 fails with Server Error, 501

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
darazman
Asked:
darazman
1 Solution
 
darazmanAuthor Commented:
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

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now