Solved

OWA working externally via the FQDN ie https://remote.companyname.com.au/exchange but not internally

Posted on 2008-11-03
3
405 Views
Last Modified: 2012-06-21
I have an SBS server which I have enabled OWA.  I am able to access OWA externally via the FQDN ie https://remote.companyname.com.au/exchange but I can't use the same address internally.  I just get the page can not be displayed.  However internally I can use https://servername/exchange.  I would like to be able to use the same FQDN name internally.  Any assistance would be greatly appreciated.
0
Comment
Question by:iJules
  • 2
3 Comments
 
LVL 16

Accepted Solution

by:
BBRazz earned 500 total points
ID: 22866614
It fails because you are trying to access an internal resource, locally and the server cannot route it correctly.

The best option is to create a  Forward ZONE on your DNS Server for remote.companyname.com.au

Then create a new A record in this zome with a blank name entry, and put in the IP of your local SBS Server.

Then, when clients connect to https://remote.companyname.com.au/exchange, they will connect on the Local IP and not the external.

You may also need to add remote.companyname.com.au as a Header in IIS on the Default Web Site

-BBRazz
0
 

Author Comment

by:iJules
ID: 22872967
Thank you very much that did it.

I created the new Forward Zone for companyname.com.au
Then created a blank Host (A) record with the IP of the SBS server
Then I also created a new Host (A) record for remote also pointing to the SBS server
I can now access remote.companyname.com.au internally



0
 

Author Closing Comment

by:iJules
ID: 31512655
I appreciate your assistance very much.  Thank you for taking the time to answer the question.

iJules
0

Featured Post

Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

786 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