Solved

Exchange 2013 Proxy Connection Error

Posted on 2013-11-10
7
21 Views
Last Modified: 2016-04-25
Have Exchange 2013 with wildcard cert. I'm getting the 'There is a problem with the proxy servers security certificate error' when trying to connect Outlook on the local network, if i connect from the outside world all is good.  The connection status tells me the url it's using and it is the external url 'webmail.mydomain.com' so i can understand why i'm getting the error but i just can't see how to get round it.
0
Comment
Question by:jfreeuk
  • 4
  • 2
7 Comments
 
LVL 15

Expert Comment

by:Skyler Kincaid
ID: 39637788
We found that you can not use a WildCard cert for Exchange. You need to get a UCC cert and make sure that you define all the subject alternative names correctly.
0
 

Author Comment

by:jfreeuk
ID: 39637816
Hi, problem with that is the internal address is .local external .co.nz, as far as i know you can't have a non supported domain name on an commercially purchased ssl cert (anymore).
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39638097
You probably haven't changed all of the URLs within Exchange to use your public name.
There some that you cannot change from ECP, it has to be done from the Shell. The most common one is Autodiscover.

get-clientaccessserver | select identity, autodiscoverserviceinternalURI

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:jfreeuk
ID: 39639879
Hi Simon, thanks for the advice but i already checked this and they are set to my external url
cheers Jamie
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39644484
Something has to be wrong in Exchange or your DNS.
Have you checked the external host names are correct AND resolve to the Exchange server? It could be that something is resolving to an external web host.

Simon.
0
 

Author Comment

by:jfreeuk
ID: 39654906
Hi Simon.  I'll go through it again and see if i can spot the error. I actually didn't do the original install so could be something in there.  thanks Jamie
0
 

Author Closing Comment

by:jfreeuk
ID: 41564074
re-installed Exchange and did the config myself.  issue resolved
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create an email address policy 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…
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…

808 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