Issue Digital Cert for NetBIOS name

I'm using Certification Services on my W2K3 server, and wondered if it's
possible to issue a certificate to a NetBIOS name for the sake of
Internal/Intranet web page.

In other words, because the web server will never be access via the Internet
can I create a CSR and issue a .cer on a website with the url
http:// or is the FQDN a must? I don't want to receive the SSL
error messages, having tried this....it gives me an error that the cert has
been assigned to a different website name.

TIA

Re: Issue Digital Cert for NetBIOS name

Yes. it is possible use netbios name as cert common cert name.
As for you error, make sure the cert is bind to specific ip + port
if you got multiple cert, each need to be on different ip/port.


--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"Scott" wrote in message
news:9C6A1258-0E2D-4C91-8BE2-823B876247BA@microsoft.com...
> I'm using Certification Services on my W2K3 server, and wondered if it's
> possible to issue a certificate to a NetBIOS name for the sake of
> Internal/Intranet web page.
>
> In other words, because the web server will never be access via the
> Internet
> can I create a CSR and issue a .cer on a website with the url
> http:// or is the FQDN a must? I don't want to receive the SSL
> error messages, having tried this....it gives me an error that the cert
> has
> been assigned to a different website name.
>
> TIA

Re: Issue Digital Cert for NetBIOS name

Yes - this is possible

the common name can be anything "server" or "server.com" or "anything you
like"

What is relevant is that the URL entered by the user matches the common name
on the cert (or the SAN - subject alternate name). And that is a matter of
"name resolution" - resolving the name in the URL to the physical host.

Cheers
Ken

"Scott" wrote in message
news:9C6A1258-0E2D-4C91-8BE2-823B876247BA@microsoft.com...
> I'm using Certification Services on my W2K3 server, and wondered if it's
> possible to issue a certificate to a NetBIOS name for the sake of
> Internal/Intranet web page.
>
> In other words, because the web server will never be access via the
> Internet
> can I create a CSR and issue a .cer on a website with the url
> http:// or is the FQDN a must? I don't want to receive the SSL
> error messages, having tried this....it gives me an error that the cert
> has
> been assigned to a different website name.
>
> TIA