Solved

Exchange 2013 - Configure External URL's

Posted on 2013-10-29
2
931 Views
Last Modified: 2013-10-30
Hello,

I installed an Exchange 2013 server, and I am configuring URL's as listed in the following technical document. My eventual goal is to have a basic network with Exchange 2013 running. I will add SSL and want to use Outlook Anywhere.

http://technet.microsoft.com/en-us/library/4acc7f2a-93ce-468c-9ace-d5f7eecbd8d4(v=exchg.150)#ConfigExternalURL

I am looking at the settings for Outlook Anywhere on my Exchange 2013 server. In this section, there are three text boxes requiring entries or choices. The first section is blank, and I don't know what to put in there. What should the entry be?

First Section: Specify the external host name such as contoso.com that users will use to connect to your organization.

Second section: Specify the internal host name such as contoso.com that users will connect to your organization.

Third section: Specify the authentication method for external clients to use when connecting to your organization.

What should I enter into the first section? Should I just enter my www.domain.com name? What is normally entered here?

Here is some background to my configuration:

I setup a basic test domain with two Windows 2012 servers. One has Exchange 2013 installed onto it. My goal is to have a fully functional domain and a working Exchange 2013 server that can send and receive messages. Eventually, I want to use OUtlook Web Access,

Outlook Anywhere and Autodiscover. I have an SSL certificate for 5 domains that I will apply.

Here is what my domain looks like:

My Domain Name
When I installed active directory, I set it up with a <mydomain.com> address.

* I have one static iP
* SERVER1 has Windows 2012 server has AD installed.
* SERVER2 has Windows 2012 server and Exchange 2013 is installed.
* SERVER2, the Exchange 2013 server, has IIS installed with a basic web page.
* Two Windows 7/8.1 workstations are joined to the domain.

Here are the DNS settings at my ISP:

A Record
mail - points to my static IP address

CNAME
autodiscover - points to mail.mycompany.com
owa - points to mail.mycompany.com

MX Record
points to mail.mydomain.com

Firewall
SMTP  Port 25 forwards to SERVER2
HTTP  Port 80 forwards to SERVER2
HTTPS Port 443 forwards to SERVER2

The Exchange 2013 Server has been assigned the following roles:

* Mailbox Role
* Client Access Role

Steps already Taken:

1. Created Send Connector. Tested and Internet recipients receive messages from test account.
2. Verified Accepted Domain, and the authorative domain listed is the one I want to use. No other accepted domains were added.
3. Reviewed the default email address policy and accepted the default SMTP email address policy already in place.
0
Comment
Question by:jhieb
2 Comments
 
LVL 22

Accepted Solution

by:
Nick Rhode earned 500 total points
ID: 39610203
1st Section: I typically use mail.consto.com while others user webmail.  You have an MX record of mail.consto.com so this should be the external on your exchange server.

The CName for OWA and autodiscover are good so I assume your certificate is like this

consto.com
mail.consto.com
autodiscover.consto.com
owa.consto.com (I wouldn't use this record but you can if thats how you want users to access owa and that is your owa URL).  

Looks good.
0
 
LVL 1

Author Comment

by:jhieb
ID: 39610339
Hi NRhode,

Thanks for the feedback. I went through the technote that I listed and used the exact examples in the note for External and Internal URLs. I even setup the same DNS records at my ISP, and also added the two CNAME records to my local DNS server. I am not sure if I created my local DNS records correctly, but it appears to be the same.

The settings are the same as the ones listed in:
http://technet.microsoft.com/en-us/library/4acc7f2a-93ce-468c-9ace-d5f7eecbd8d4(v=exchg.150)#ConfigExternalURL

The only difference is that I am not using contoso.com of course.

I am not able to verify the settings using nslookup, though. I am not sure how to make it use a different DNS server, or even if my ISP has fully updated my DNS settings.

For now, as long as the technote is accurate, and if my paths are correct, I might be ready to apply my SSL. That will be the last step. I sure wish I knew for certain if everything was good to go. I think GoDaddy support is getting tired of refunding my SSL certificate. I have had to do that three times and have them apply credits so that I can get a new one. So, this is why I am proceeding very cautiously this time.
0

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…

762 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now