Exchange 2013 Remote Connectivity issues

New server, inside the network everything seems okay,  It seems to be trying to lookup the local cas server instead of using the internet dns name.

Failed to create temporary folder for performing tests.
 
 Additional Details
 
Exception details:
Message: The request failed. The remote name could not be resolved: 'xxxxxx.xxx.local'
Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
Stack trace:
 at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.BuildEwsHttpWebRequest()
 at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
 at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
 at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
 at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
Exception details:
Message: The remote name could not be resolved: 'xxxxxxx.xxx.local'
Type: System.Net.WebException
Stack trace:
 at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
 at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
 at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.TraceAndEmitRequest(IEwsHttpWebRequest request, Boolean needSignature, Boolean needTrace)
 at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.BuildEwsHttpWebRequest()


Elapsed Time: 1 ms.
LVL 1
adroadamAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Simon Butler (Sembee)ConsultantCommented:
Have you set all of the URLs within Exchange correctly?
Specifically external URLs ?
Do you have a trusted SSL certificate on the server?

The way that most people are implementing Exchange 2013 is to use a split DNS system to allow the external name to resolve internally and then use the same host name for both internal and external traffic. This gets round the internal name on the public SSL certificate issue.

Simon.

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
adroadamAuthor Commented:
Split DNS and adjusting the internal URLs to match the external URLs. Thanks, Adam
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.