Solved

can Public SAN certificate work without Exchange 2007 Hostname

Posted on 2008-10-23
9
241 Views
Last Modified: 2012-05-05
We are going to register SAN certificate with Entrust which we will issue to our Exchange 2007 CAS Server. we have registered a domain e.g. domain.com on internet. But internally we use a different domain for AD and Exchange e.g. xyz.com. we have generated the SAN request and sent to Entrust, they are saying that you can't put xyz.com on the SAN certificate becuase it's not registered on your name. I have added all domain names during certificate file generation :

new-exchangecertificate -generaterequest -subjectname "c=india,o=ABC Corp,CN=webmail.domain.com" -domainname webmail.domain.com,autodiscover.domain.com,cas01.xyz.com,cas01 -Friendlyname "ABC Mail Certificate" -path c:\certreq.txt -privatekeyexportable:$true

now the request file has xyz.com entry (internal domain name used in AD). so my question is if i remove xyz.com entries then will my certificate have any problems (internal network or external network) while working on mails e.g. RPC, OWA or Outlook within LAN.

Please suggest.
0
Comment
Question by:fextech
  • 3
  • 3
  • 2
9 Comments
 
LVL 4

Expert Comment

by:futurefiles
Comment Utility
It can but i think you will get a warning on the outlook clients if the hostname is not in the SAN. Warning would be displayed every time you open outlook, if i remember correctly
0
 
LVL 4

Expert Comment

by:futurefiles
Comment Utility
Whatever server has the hub / cas role installed needs to be on the san as a hostname i.e DNS Name=exchange.abc.local
0
 

Author Comment

by:fextech
Comment Utility
in my case we are not using .local but its .com e.g. xyz.com and it's registered by somebody else.
Are you using Public Certificate for do you have issued through internal CA (Microsoft)?
0
 
LVL 4

Expert Comment

by:futurefiles
Comment Utility
Public from Entrust
why are you using someon elses domain name? your gonna be stuck i think
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 
LVL 31

Expert Comment

by:Paranormastic
Comment Utility
I assume by Entrust you are speaking of their commercial CA service, not their in-house CA product for your own internal certs.

If your internal domain ends in .com and you do not own that .com address, especially if someone else does, then it would not pass their vetting process and they must deny the request in order to maintain their integrity.  Otherwise they are certifying that you have rights to that .com, which you do not.

If it was a .local or a secondary .com that you could prove ownership of, then they would not likely have an issue with it.  This is one of those cases where technically it is possible, but it would probably not be legal for them to do so.
0
 

Author Comment

by:fextech
Comment Utility
That's correct. Legally it is not correct to put some other domain in your own domain. But i don't know what's going to happen when users will be accessign mails internally, if I don't put my internal domain name in the certificate.

I also have doubt that certificate message will keep on prompting to users when they will be working on Outlook internally. Have you ever encountered such situation?
0
 
LVL 31

Accepted Solution

by:
Paranormastic earned 500 total points
Comment Utility
If they try accessing it securely and the name is not there, it will always generate a warning.  If they accept it then it willbe secured, but they will get prompted each time they log in to check their mail.

Depending on your security requirements, you might be able to get away with having unsecured connections across the LAN.  This is all up to your corporate security policy.  

If you cannot do this, then I would recommend looking into getting your improperly setup internal domain name migrated to a proper .local domain.  Here are a few links in this area - be aware of whatever apps you are running and how migration might affect them:

Windows Server 2003 Active Directory Domain Rename Tools
http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

Microsoft Exchange Server Domain Rename Fixup (XDR-Fixup)
http://www.microsoft.com/downloads/details.aspx?familyid=24b47d4a-c4b9-4031-b491-29839148a28c&displaylang=en

Rename a Windows 2003 Forest with Exchange 2003 installed
http://www.msexchange.org/tutorials/Domain-Rename.html
0
 
LVL 31

Expert Comment

by:Paranormastic
Comment Utility
I'm just checking in on old posts today... Are you still having this issue?  If so, please let me know so I can help some more, if not, please close accordingly..
0

Featured Post

Integrate social media with email signatures

Is your company active on social media? Do you also use email signatures? Including social media icons in your email signature is a great way to get fans for free. Let all your email users know you’re on social media quickly and easily, in a single click.

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
Resolve DNS query failed errors for Exchange
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…
To show how to generate a certificate request 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 Servers >> Certificates…

728 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now