I have a server (server.mydomain.com) with ISA 2006 and am using it as an L2TP VPN server. My problem is we want it to be named vpn.mydomain.com externally, so it's easy to remember. This is no problem with PPTP as I can just point a host or alias record there, but with L2TP of course that name (vpn.mydomain.com) doesn't match the computer certificate name (server.mydomain.com) on the machine so authentication fails.
I've tried a few logical ways around this:
*Add certificates of type IPsec, Web Server with the vpn.mydomain.com name - this does not work because it defaults to the computer cert. Even if the computer cert is removed it won't use these. *Copy the computer cert to my own template and enroll, supplying the name I want - This does not work because it won't use the cert (makes me wonder, is it being super-picky and only using certificates with the standard "machine" template?) *Tried creating standard "machine" cert with alt names matching the name I want, receive an error. This may be because the "machine" template is set to get names from AD vs in the request. *Thought about adding a RADIUS server where I know I can select my cert from a list, but really do not want to add that extra dependency to the VPN service. *Thought about having clients check the "match domain only" option, but want to avoid relying on users doing this if at all possible.
So I'm wondering, is there any way to control what certificate ISA will use for the L2TP VPN without using RADIUS?
< Message edited by Ross G -- 12.Aug.2008 2:32:02 PM >