Outlook Anywhere is not using external hostname in Exchange 2013

For some reason Outlook anywhere is not displaying the external hostname in Outlook (proxy settings) but the internal hostname.  

I keep validating the configuration over and over again but I can't figure it out.  

Some snapshots hopfully will help you to understand what I'm talking about.



Ge-OutlookAnywhere2013-09-10-17-48-38.jpg
quadrumaneAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Please elaborate
0
Berkson WeinTech FreelancerCommented:
If you look in ECP does it show the correct external hostname?
0
ChrisCommented:
http://support.microsoft.com/kb/2754898

this explains it to you

you could combine the two and use split brain dns/pinpoint records to access via the same name whether internal or external but there is some work needed to do this
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

quadrumaneAuthor Commented:
Yes the external hostname has been set in Outlookanywhere and all virtual directories (OWA, OAB, ECP..)  

But as soon as Outlook is configured  (autodiscover) the host name (s1-cas-001.domain.com)  is added instead of mail.domain.com in proxy settings and msstd

Thanks
0
ChrisCommented:
but when you connect via external network and then check connection status what name do you see there?
0
quadrumaneAuthor Commented:
Thanks, the article is useful.  It's by design.  Now I know.  

We plan to add another Client Access Server, NLB is to be used to load balance the Exchange web traffic.   But split DNS is not something I has in mind, I would have prefered to point to the mail DNS A record as we've been doing for years with previous Exchange versions.  

Thans again !
0
quadrumaneAuthor Commented:
The status connection shows a lot of GUID.  Most of the GUID have the external name proxy (mail.domain.com) some GUID are using the hostname.  

We have a lot of shared mailboxes.   I suspect External HostName is used to connect the shared mailboxes but InternalHostName is used to connect the mailbox, my mailbox.
0
ChrisCommented:
when you say NLB presumably you mean hardware load balancer

i don't like split brain DNS i use pin point records for Lync and Exchange to simplify the name space

yeap server name you will probably see some random looking GUID but the proxy should come up with the hostname.

I have mine test lab setup on a single name space so i can't verify if i see something different
0
quadrumaneAuthor Commented:
No harwdare load balancers as we no longer need to create an CAS array Windows NLB will be used.  NLB is not exactly the best option I'm aware of it.  But it will be useful in the event that a CAS goes down.  Besides the third CAS will be at the Datacenter (same AD domain site to site VPN)

The proxy come up with the hostname and external hostname, depending on the GUID.  I guess it's also "by design".  It seems to be working so far.

The external DNS is pointing to the WAN IP, the router translates (NAT) it to the private IP.  This private IP is the one assigned to the CAS.  But as soon as the secondary CAS will be online an A record (mail) will be used as the virtual IP.  

The third CAS (Datacenter) is not on the same subnet.  I guess I will have to figure something out or it will be resilient only.  

Thanks again
0
ChrisCommented:
windows NLB's are no longer supported - certainly if you phone MS for support. I think it even causes issues.
Obviously if you have any kind mailbox clustering installed you won't be able to install NLB.

yeap you you would swap the current front end server's IP for another and setup a VIP

 that's where a hardware load balancer comes in as you can have servers not in the same subnet - have a look at Kemp technologies, they do virtual and physical ones for not too much cash
0
SteveCommented:
NLB wont work. use CASARRAYs to achieve this.

As the Mailbox DBs have already been created you'll need to manually update them to use the CASarray, but newly created DBs would automatically use the appropriate CASarray.
0
quadrumaneAuthor Commented:
I don't have any older mailbox.  All mailboxes have been moved to the new mailbox Exchange 2013.  The CAS role is enabled in a different Exchange server.  I think Microsoft is fully supporting NLB on Exchange 2013.  But I can be wrong.
0
ChrisCommented:
Just double checked. They do support it. A couple of MS engineers told me it wasn't supported and it was current recommend guidance to use hardware load balancers but that was a few months ago
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.