• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 28
  • Last Modified:

Exchange 2013 Proxy Connection Error

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
jfreeuk
Asked:
jfreeuk
  • 4
  • 2
1 Solution
 
Skyler KincaidNetwork/Systems EngineerCommented:
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
 
jfreeukAuthor Commented:
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
 
Simon Butler (Sembee)ConsultantCommented:
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
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
jfreeukAuthor Commented:
Hi Simon, thanks for the advice but i already checked this and they are set to my external url
cheers Jamie
0
 
Simon Butler (Sembee)ConsultantCommented:
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
 
jfreeukAuthor Commented:
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
 
jfreeukAuthor Commented:
re-installed Exchange and did the config myself.  issue resolved
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now