<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: eap-tls failing with domain certificates and 1200 APs</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/eap-tls-failing-with-domain-certificates-and-1200-aps/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/eap-tls-failing-with-domain-certificates-and-1200-aps/</link>
	<description></description>
	<pubDate>Mon, 09 Nov 2009 06:35:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: astronomer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/eap-tls-failing-with-domain-certificates-and-1200-aps/#comment-43019</link>
		<dc:creator>astronomer</dc:creator>
		<pubDate>Fri, 25 May 2007 11:43:33 +0000</pubDate>
		<guid isPermaLink="false">#comment-43019</guid>
		<description>After three and a half hours with microsoft support, here is the answer:
Go to the web site on the certificate server with the browser of the IAS server, click request certificate, click advanced certificate request, click create and submit a request for this ca. On the next page under certificate template: select "web server". Type in something for identifying information. In the "key options" section click the check box for "store certificate in the local computer certificate store". Click submit and then install the certificate. 
Once the certificate is installed, restart the IAS service and it will see the new certificate.
After doing this, I was able to use the certificate based SSID without errors.
rt</description>
		<content:encoded><![CDATA[<p>After three and a half hours with microsoft support, here is the answer:<br />
Go to the web site on the certificate server with the browser of the IAS server, click request certificate, click advanced certificate request, click create and submit a request for this ca. On the next page under certificate template: select &#8220;web server&#8221;. Type in something for identifying information. In the &#8220;key options&#8221; section click the check box for &#8220;store certificate in the local computer certificate store&#8221;. Click submit and then install the certificate.<br />
Once the certificate is installed, restart the IAS service and it will see the new certificate.<br />
After doing this, I was able to use the certificate based SSID without errors.<br />
rt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: astronomer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/eap-tls-failing-with-domain-certificates-and-1200-aps/#comment-43020</link>
		<dc:creator>astronomer</dc:creator>
		<pubDate>Tue, 22 May 2007 19:34:43 +0000</pubDate>
		<guid isPermaLink="false">#comment-43020</guid>
		<description>I used mmc to request another certificate. Now I have two certificates listed for authentication. Still have the same error in IAS. 
I'm starting to think I may have to use the same method that worked in my lab tests. In the lab, IAS had this problem and I tried removing and re-installing this service. It didn't help. 
Finally, I blew the DC, (and the domain), away. After installing the OS from scratch, I created the domain, installed IIS, installed CA, then installed IAS. 
At this point it worked. I believe the issue is IAS was installed before the certificate server and knew nothing about certificates. When the certificate server was installed later, IAS didn't know how to bind to it. When I installed IAS after the certificate server, It seamlessly incorporated the certificate which was already there.
The problem with this method is we already have IAS installed on our main domain controllers so pix VPNs can be authenticated.
I really don't want to rebuild my domain controllers so if anyone knows how to get IAS to see the certificate, I would appreciate hearing about it.</description>
		<content:encoded><![CDATA[<p>I used mmc to request another certificate. Now I have two certificates listed for authentication. Still have the same error in IAS.<br />
I&#8217;m starting to think I may have to use the same method that worked in my lab tests. In the lab, IAS had this problem and I tried removing and re-installing this service. It didn&#8217;t help.<br />
Finally, I blew the DC, (and the domain), away. After installing the OS from scratch, I created the domain, installed IIS, installed CA, then installed IAS.<br />
At this point it worked. I believe the issue is IAS was installed before the certificate server and knew nothing about certificates. When the certificate server was installed later, IAS didn&#8217;t know how to bind to it. When I installed IAS after the certificate server, It seamlessly incorporated the certificate which was already there.<br />
The problem with this method is we already have IAS installed on our main domain controllers so pix VPNs can be authenticated.<br />
I really don&#8217;t want to rebuild my domain controllers so if anyone knows how to get IAS to see the certificate, I would appreciate hearing about it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->