Exchange 2013 Outlook anywhere takes a long time to connect

He have recently upgraded to Exchange 2013 moving from 2007, all users have now been migrated and everything seems to be running ok internally.

Outlook anywhere however is taking an age to connect to the server from users outside the network.

Some users cannot connect but that may be a different issue.

Everything seems to be setup correctly and I tested with Microsoft Remote Connectivity Analyzer which it passed.

With Exchange 2007 it used to be pretty instant.

I cant see any reason for it so would like some help in case there is something ive overlooked.

Cheers.
robquartzelecAsked:
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.

wolfcamelCommented:
is there a lot of new synching traffic going on that could be perhaps slowing down the external link?
If it is working then I would suggest it is configured OK,
the dns lookup can represent a chunk of the connection time and a hosts file entry will help you see if this is a cause.
0
robquartzelecAuthor Commented:
Hi,

Thanks for your response, changing the host file made no difference, still took just as long.

Looking at our connection its not showing heavy usage so I don't think its that.

in Outlook connection status is shows about 6 connections which are 'connecting' very slowly they each one turns to 'established'
0
robquartzelecAuthor Commented:
This is what it looks like eventually when they have all connected which took about 10 minutes, does all this look as it should?
outlok-con-status.png
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Simon Butler (Sembee)ConsultantCommented:
Outlook Anywhere works on the basis that Outlook attempts to connect to the Exchange server's real address (as shown in the server configuration), if that fails then it falls back to Outlook Anywhere host name.
The delay you are seeing would suggest that the host name of the Exchange server resolves on the internet and it has to time out before it connects on Outlook Anywhere.
As each user has a unique endpoint within Outlook for their server, that can only mean you have a wildcard in your domain and the internal and external domains are the same. Remove the wildcard and see if that improves matters.

Simon.
0
robquartzelecAuthor Commented:
Simon, We don't have any wildcard in place. Our internal and external exchange addresses are the same however mail.ourname.com

We have an additional internal forward lookup zone for our outside domain so that the name is resolved inside due to not being able to have internal names on the certificate anymore.

Thats how I understood it should be setup is that correct?
0
Simon Butler (Sembee)ConsultantCommented:
Internal and external name should be the same in most cases, with split DNS being used.
However the server's REAL name should not be the same, so hopefully your Exchange server is not called "mail".

You need to check on one of the external clients that the name resolves correctly to begin with. Then use the Connection Status dialogue to see what Outlook is doing when it is failing to connect. That could give you an idea where the problem is.

Simon.
0
robquartzelecAuthor Commented:
Hi,

Nope our server name is not mail.

The name resolves correctly on the external client, and they can access the OWA site with the same address.

In the connection status is just says connecting for ages then one by one they say established.

Most users will connect after a long period some struggle to at all and others it will cycle through being connected then not then connected again even on a stable broadband connection from there home.

Any other ideas on what to check?

Cheers.
0
Simon Butler (Sembee)ConsultantCommented:
Does the server's REAL name resolve on the internet at all?

Simon.
0
robquartzelecAuthor Commented:
No the server name does not resolve.
0
robquartzelecAuthor Commented:
This has been resolved, we found that SSL Offloading had been enabled in error. Once this had been disabled it now connects instantly.

Some users which have additional mailboxes where prompted for username and password however and removing then re adding them cleared 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
robquartzelecAuthor Commented:
We found the setting which was causing the issues.
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.