|T O P I C R E V I E W
||Posted - 09/29/2011 : 5:04:21 PM
I am sure there is a quick answer for this, but it is defeating me at the moment.
Running SBS 2003 and unfortunately the internal domain and external domain have been setup with exactly the SAME name, e.g. 'abc.com'. I have OWA working, but external users have to enter the external IP address of the SBS server to access OWA - 'https://222.xxx.xxx.xxx/exchange', which is a real pain.
I have tried publishing a certificate using something like 'owa.abc.com', but I cannot access OWA because of the int/ext domain name problem.
Bearing in mind that the int/ext domain names are the same, how can I setup a more user-friendly URL to access OWA?
Any help greatly appreciated.
|4 L A T E S T R E P L I E S (Newest First)
||Posted - 10/06/2011 : 1:42:22 PM
Don't forget to run CEICW again and now enter the hostname you created, i.e. owa.abc.com. Now SBS 2003 will create a new certificate with this hostname and enables the certificate in IIS.
||Posted - 10/06/2011 : 1:31:47 PM
Thanks for the help guys. I will contact our webhoster and get them to add an (A) record that will point to something like owa.abc.com on our external IP address.
||Posted - 09/30/2011 : 03:05:47 AM
what Joe said. Whoever manages the external name resolution for your Internet domain (in most cases, it's either your ISP or your webhoster) needs to put in a host (A) record pointing the name that appears on the cert (if you're unsure which it is, just open the OWA site and look at the SSL cert in your browser) to the external IP address.
Although a split brain DNS can be a pain in the @r$3 otherwise, in scenarios where users need to open OWA (or use Server ActiveSync) both from inside and outside the LAN, having the same domain and host names can actually simplify things.
||Posted - 09/29/2011 : 5:47:07 PM
Sorry for the silly question, but have you got any internet DNS entries for the Exchange server?
An A/ PTR record with the name pointing at the IP address.
Welcome to the forum by the way.