<div>
Are you strickly running SSL connections from the outside?<br />
<br />
If so, do you have the correct CERT installed. &nbsp;The cert must be able to handle multiple host names. 1 for your public, and 1 for your internal. &nbsp;If it doesn't, that's most likely your issue.<br />
<br />

</div>


<div>
It does the same thing when connecting via HTTP and HTTPS. &nbsp;Although with HTTP, we do not get the obvious certificate prompt, it just seems to redirect to the internal FQDN as mentioned.<br />
<br />
Another note to mention is that it does not matter if you connect via the mail.domain.co.uk or the IP address, it still ends up at internal FQDN.
</div>


<div>
Require Secure Channel (SSL) is not ticked, in answer to your first question.
</div>


<div>
Gotcha, what happens if you try to access OWA via HTTP not HTTPS from the outside?<br />

</div>


<div>
No, they are not configured as front-end servers. &nbsp;Just two servers on the same domain, in opposite ends of the country. &nbsp;Upon further investigation, it does appear as though the particular mailboxes we are trying to access are on the far server.<br />
<br />
mail.domain.co.uk points to the external IP address of server1.<br />
<br />
server2 is the remote server at the opposite end of the country and this is the server that holds this particular Exchange mailbox that we are trying to access OWA for.<br />
<br />
If this ties in with your explanation, any idea of how to work around it?
</div>


<div>
Is server2 directly reachable via a public ip address and a router? &nbsp;Or is it only reachable from your internal network?
</div>


<div>
<div class="content wysiwyg-content">
Two servers running Windows Server 2003 Standard edition, each with Exchange Standard 2003.<br />
<br />
We were successfully accessing OWA externally via a hostname mail.domain.co.uk set up by our domain people but this appears to have stopped working over the weekend.<br />
<br />
Now, when accessing mail.domain.co.uk, it resolves to the internal FQDN of one of the two servers (server2.domain.local) and fails to find the page.<br />
<br />
When accessing OWA via https, we get as far as the certificate prompt prior to the log on screen.<br />
<br />
We can access OWA successfully from both of the servers, internally.<br />
<br />
Any help trying to get to the bottom of this pesky problem would be greatly appreciated as we are currently tearing our hair out over it.
</div>
</div>


Two servers running Windows Server 2003 Standard edition, each with Exchange Standard 2003.

We were successfully accessing OWA externally via a hostname mail.domain.co.uk set up by our domain people but this appears to have stopped working over the weekend.

Now, when accessing mail.domain.co.uk, it resolves to the internal FQDN of one of the two servers (server2.domain.local) and fails to find the page.

When accessing OWA via https, we get as far as the certificate prompt prior to the log on screen.

We can access OWA successfully from both of the servers, internally.

Any help trying to get to the bottom of this pesky problem would be greatly appreciated as we are currently tearing our hair out over it.

External access to OWA on Exchange 2003 resolves to the internal FQDN and fails.

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.