Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

Getting certificate error on my local network when connecting to exchange

Exchange 2013

I can connect to a mailbox via outlook perfectly from outside the network, but within the local network I get this error below. It's not using the godaddy certificate or address. It's using the local server address as you can see.cert-error.jpg
0
cnl83
Asked:
cnl83
  • 3
  • 2
  • 2
  • +4
1 Solution
 
JasonDuncanworksCommented:
1. What version of Outlook are you using?
2. Does this happen to everyone?
3. Is this new / did it ever work?
4. Are you joined to the domain?
0
 
Cliff GaliherCommented:
Is this not a question you already have open? As I said in your password question, the cause of the password prompt is because of a URL/SSL issue. The two are related and you are already working that problem. This only complicates issues and will add confusion.
0
 
cnl83Author Commented:
That was isolated to just Outlook 2007. This is all clients now.
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
Seth SimmonsSr. Systems AdministratorCommented:
you should not be using .local to connect internally; use your external (.com, .net or whatever it is) to connect internally
might need to configure split dns

Windows - Setting Up Split DNS
http://www.petenetlive.com/KB/Article/0000830.htm
0
 
MASTechnical Department HeadCommented:
0
 
Cliff GaliherCommented:
Unfortunately the nature of EE (or any forum) is that experts are not sitting on your network and don't know the details of your implementation. As I stated in that thread, we reached a point where I believe you really need to call in a paid consultant to fix your issues. The reason I gave that advice at that time wasn't laziness, but was because there was a tipping point where a forum was no longer a good way to resolve your issue.

 I hate to say it, but by following some of the (blatantly bad) advice that was given to you after I dropped off that question, you've actually created this new error. They are not unrelated. The other drawback of a forum is that if you don't have some prerequisite knowledge, it is very difficult to filter "good" advice from "bad" advice. And since you aren't paying anyone, you have no warranty or recourse.

So I will again suggest that you should contact a local consultant in your area that you trust or find a reputable company that offers paid remote support and has a good reputation. I fear that if you continue to try to solve these problems through EE, you will only further create issues and may get yourself into a state you cannot get out of.

Ultimately, of course, that choice is yours.
0
 
R--RCommented:
Please check in IIS default web site binded to proper SSL certificate. Go to EAC and click on server and go to certificate and check whether the correct certificate has IIS, SMTP, IMAP and POP3 services are assigned.
Verify certificate have SAN entries eg mail.domain.com and autodiscover.domain.com. Make sure DNS host A record mail.domain.com is pointed to the exchange 2013 in internal DNS. If the DNS hots A record is not present then create a record.
run get-clientaccessserver | fl and check if autodiscoverurl is pointed to mail.domain.com
Go to server and virtualdirectories and make sure all the virtual directories are configured with external and internal entries as mail.domain.com
0
 
JasonDuncanworksCommented:
I had to do this for a client, it sets exchange to use external name for internal. Change the name to your domain
Set-AutodiscoverVirtualDirectory -Identity * -internalurl “https://mail.qcstorage.net/autodiscover/autodiscover.xml”
Set-ClientAccessServer -Identity * -AutodiscoverServiceInternalUri “https://mail.qcstorage.net/autodiscover/autodiscover.xml”
Set-webservicesvirtualdirectory -Identity * -internalurl “https://mail.qcstorage.net/EWS/Exchange.asmx”
Set-oabvirtualdirectory -Identity * -internalurl “https://mail.qcstorage.net/oab”
Set-owavirtualdirectory -Identity * -internalurl “https://mail.qcstorage.net/owa”
Set-ecpvirtualdirectory -Identity * -internalurl “https://mail.qcstorage.net/ecp”
Set-ActiveSyncVirtualDirectory -Identity * -InternalUrl "https://mail.qcstorage.net/Microsoft-Server-ActiveSync"

Open IIS Manager by clicking Start, then enter inetmgr.
Expand the server and expand Application Pools, then right-click on MSExchangeAutodiscoverAppPool, and select Recycle.
0
 
cnl83Author Commented:
http://supertekboy.com/2014/07/08/designing-simple-namespace-exchange-2013/

Going through each step in this link resolved my issue.
0
 
cnl83Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for cnl83's comment #a40369517

for the following reason:

It's what another Expert Exchanger provided to me to resolve my error. Though it did block my access to my own web site.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
I told you in the beginning not to be using .local and you may need to configure split dns.
Jason elaborated more on what I stated which both amounts to the solution.
you stated "It's what another Expert Exchanger provided to me to resolve my error." though selected your own comment as the solution.
0
 
Gareth GudgerCommented:
Hey CNL83,

Just wanted to post here as well. Make sure you add an A record of "WWW" in your newly created split-brain DNS zone on your internal DNS server. Then point that to the public IP of your hosting provider for your website.

That will fix that issue.

-Gareth
0

Featured Post

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

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