Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange 2013 FQDN Certificate Error

Posted on 2014-11-06
7
Medium Priority
?
368 Views
Last Modified: 2014-11-20
Hello weve put mail.ville.xxx.qc.ca for the FQDN of the Default Frontend NAMESERVER but im not sure if it's ok

Because we use TMG and we use owa.ville.xxx.qc.ca for OWA

mail.ville.xxx.qc.ca is a nat to our exchange server directly

we are receiving this error

Microsoft Exchange could not find a certificate that contains the domain name mail.ville.xxx.qc.ca in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default Frontend NAMESERVER with a FQDN parameter of mail.ville.xxx.qc.ca. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

What FQDN i should use ?

If mail.ville.xxx.qc.ca is ok how to add it to the certificate

Thanks !
0
Comment
Question by:jfguenet
  • 4
  • 3
7 Comments
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40426315
Run the following:

Get-ExchangeCertificate | FL

Let us know the output. Most likely what has occurred is that you should change the FQDN of the send connector to something that is common on the certificate. That should resolve the issue.

Also.. I don't think TMG plays into this as you most likely do not have a web rule for it.
0
 

Author Comment

by:jfguenet
ID: 40426462
[PS] C:\Windows\system32>Get-ExchangeCertificate | FL


AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {owa.xxx.xxx.qc.ca, www.owa.xxx.xxx.qc.ca}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/,
                     O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
NotAfter           : 2015-10-01 07:13:26
NotBefore          : 2014-09-23 13:35:19
PublicKeySize      : 2048
RootCAType         : ThirdParty
SerialNumber       : 2B503D0F61C656
Services           : None
Status             : Valid
Subject            : CN=owa.xxx.xxx.qc.ca, OU=Domain Control Validated
Thumbprint         : 62821EE9FFC4C0FF41AA86E1A9A8DDC9BC6688ED

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {server_name.xxx.xxx.qc.ca, AutoDiscover.xxx.xxx.qc.ca,
                     AutoDiscover.xxx.ca, server_name, xxx.xxx.qc.ca, xxx.ca}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=AC-Racine, DC=ville, DC=xxx, DC=qc, DC=ca
NotAfter           : 2016-09-15 15:47:43
NotBefore          : 2014-09-16 15:47:43
PublicKeySize      : 2048
RootCAType         : Enterprise
SerialNumber       : 535F5FB8000000000679
Services           : IMAP, POP, SMTP
Status             : Valid
Subject            : CN=server_name.xxx.xxx.qc.ca, OU=TI, O=xxx, L=xxx, S=QC, C=CA
Thumbprint         : 0D911213DE4A8B565F185A8E3E28AF5B80AC5893

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {owa.xxx.xxx.qc.ca, server_name.xxx.xxx.qc.ca,
                     AutoDiscover.xxx.xxx.qc.ca, AutoDiscover.xxx.ca, server_name,
                     xxx.xxx.qc.ca, xxx.ca}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=AC-Racine, DC=ville, DC=xxx, DC=qc, DC=ca
NotAfter           : 2016-09-15 13:23:11
NotBefore          : 2014-09-16 13:23:11
PublicKeySize      : 2048
RootCAType         : Enterprise
SerialNumber       : 52DB0EDA000000000678
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=owa.xxx.xxx.qc.ca, OU=TI, O=xxx, L=xxx, S=Québec, C=CA
Thumbprint         : 867EAB32807A54ACEFF53BF0850434FED0DAC903
0
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40426475
Change the EHLO name to match the OWA namespace on the certificate and this will fix the STARTTLS issue. If you do not want that namespace there, then you would need a certificate that has the mail.xxx.xxx.xxx.com namespace.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 

Author Comment

by:jfguenet
ID: 40426595
if i put owa.xxx.qc.ca it's not the same public ip address as mail.xxx.qc.ca

owa is for my TMG server
mail is for my exchange server

The EHLO name must me mail no ?

Will i have problem if i put owa ?
0
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40426640
You should not have an issue putting OWA. The name has to be listed on the SSL certificate. I would increase SMTP logging like you did before and check again, but it should resolve your issue.
0
 

Author Comment

by:jfguenet
ID: 40426844
And if i put the server name instead is it better ?
0
 
LVL 19

Accepted Solution

by:
Adam Farage earned 2000 total points
ID: 40427009
The context of the EHLO FQDN must match the Certificate Domains if you would like TLS to work. I would recommend either rekeying the certificate (since you missed AutoDiscover anyways) and keep the name or change the EHLO FQDN to what is listed on your certificate.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
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…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

886 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