asked on

2003 to 2010 transition

In mid transition from Exchange 2003 to 2010 and setting up the redirect from the new 2010 server to the 2003 system for owa, I've set the "exchange2003URL" to point to our frontend 2003 server url "https://*********/exchange"
When logging in I am presented with the 2010 outlook web app and am redirected to the 2003 server but getting "page cannot be displayed" error code 64, it is going to the correct server as the certificate is the correct OWA ssl but it seems to be landing on the "/exchweb" page instead of the "/Exchange" I've tried enabling forms based authentication but this stops anyone logging into owa

Systech Admin

Refer https://www.experts-exchange.com/questions/27394064/cannot-access-OWA-over-https-Error-Code-64-Host-not-available.html

Jon Carney

ASKER

Hi Systechadmin

Thanks for the reply, I did see that post but the cert it refers to is an internal cert, we are using a wildcard issued by third party geotrust with all intermediate certs installed on all Exchange servers.

Systech Admin

Is there any proxy server like ISA or TMG?

Jon Carney

ASKER

There is an ISA 2006 server but I've tried bypassing the server for internal use by changing the DNS entry to point directly to the FE Exchange server and not ISA as we're using split DNS but getting the same results.
Trying it directly on the new exchange server via a web browser lets you log in fine.

ASKER CERTIFIED SOLUTION

Systech Admin

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jon Carney

ASKER

Right, I've set up the rules on the ISA server and legacy is pointing to 2003 servers, seem to be getting a bit further but now seeing an "error code 10061: connection refused" after the redirect?

Systech Admin

is the legacy domain included in the certificate? Please check the ISA logs for any rules issues.