Solved

Exchange 2013 Proxy Connection Error

Posted on 2013-11-10
7
22 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
In this video we show how to create an Accepted Domain 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 >> Ac…

734 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