Re: WLAN Server Certificate for private internal AD Domain

From: Ashwin Palekar\(MS\) (ashwinp_at_online.microsoft.com)
Date: 04/13/04


Date: Mon, 12 Apr 2004 21:07:05 -0700


> Does anyone know if that FQDN has to correspond to my Active Directory
> Domain (ias.company.ad) or if it can just be a legitimate DNS name
> (ias.company.com) for which I can obtain a certificate.. and which I
> also control internally?

--> It can be either.

--> Alternatively, you can also use a Certificate issued by your own
internal CA. (assuming you have some way to provision the trusted root to
the client (either using web page or AD))

-- 
-- 
===========================================================
This posting is provided "AS IS" with no warranties and confers no rights
===========================================================
"Jeff" <ataribaby_23@hotmail.com> wrote in message 
news:e409a5bc.0404121307.6a33475a@posting.google.com...
> Hi-
> I'm trying to obtain a WLAN Server certificate from Verisign for
> PEAP-MS-CHAP V2.
> My internal MS Active Directory Domain (company.ad)is not registered
> on the internet therefore I am unable to prove to verisign that I am
> who I say I am.
> According to Verisign: "The company.ad domain is a valid domain name
> and therefore must be registered.  Unfortunately, we cannot approve
> the certificate without confirmation that the Domain belongs to the
> organization enrolling for the certificate"
>
> I do realize now that the .ad root zone is for the country of Andorra.
>
> According to Microsoft's documentation, the WLAN Server Certificate
> must contain the fully qualified domain name (FQDN) of the computer
> account of the IAS server computer in the Subject Alternative Name
> property.
>
> Does anyone know if that FQDN has to correspond to my Active Directory
> Domain (ias.company.ad) or if it can just be a legitimate DNS name
> (ias.company.com) for which I can obtain a certificate.. and which I
> also control internally?
>
> Thanks in advance
> - Jeff Roberts - 


Relevant Pages

  • Re: SSL certificates
    ... Default - which points to the internal FQDN ... My SSL Cert has mail.mydomain.com which is why I am now getting the errors ... Microsoft Exchange couldn't find a certificate that contains the domain name ... self-signed certificate to advertise StartTLS to internet Server to Server ...
    (microsoft.public.exchange.admin)
  • RE: FQDN
    ... > You must run CEICW and specify the FQDN that you will use to access the ... On the SBS 2003 Server open the Server Management console. ... Click the "Connect to the Internet" link. ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)
  • RE: FQDN
    ... > You must run CEICW and specify the FQDN that you will use to access the ... On the SBS 2003 Server open the Server Management console. ... Click the "Connect to the Internet" link. ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)
  • Re: Internal Namespace Issue
    ... accessible by Outlook from both the inside and outside. ... the internal outlook clients are resolving to the FQDN of the server ... localservername.domain.com - using the SSL Certificate for the public ... do with the Internet directly. ...
    (microsoft.public.windows.server.dns)
  • Re: Do I have to have a my own DNS?
    ... Internic and it's different than the universiy's .edu FQDN. ... Your DNS servers ... your ISP's DNS servers for Internet resolution. ... to Windows 2003 Active Directory. ...
    (microsoft.public.windows.server.active_directory)