<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exchange 2010 Certificate Revocation Checks and Proxy Settings</title>
	<atom:link href="http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings/feed" rel="self" type="application/rss+xml" />
	<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings</link>
	<description>Microsoft Exchange Server News - Tips - Tutorials</description>
	<lastBuildDate>Mon, 21 May 2012 19:19:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Paul Cunningham</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-7146</link>
		<dc:creator>Paul Cunningham</dc:creator>
		<pubDate>Sat, 17 Mar 2012 13:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-7146</guid>
		<description>As the article suggests, using this tip can break your Exchange tools connection to the server. The solution is explained in the post - use a bypass in your IE settings or when running the netsh command.</description>
		<content:encoded><![CDATA[<p>As the article suggests, using this tip can break your Exchange tools connection to the server. The solution is explained in the post &#8211; use a bypass in your IE settings or when running the netsh command.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Imi</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-7104</link>
		<dc:creator>Imi</dc:creator>
		<pubDate>Tue, 13 Mar 2012 12:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-7104</guid>
		<description>Using the above has broken my connection and I cant get it back. EMC wont connect. STUCK</description>
		<content:encoded><![CDATA[<p>Using the above has broken my connection and I cant get it back. EMC wont connect. STUCK</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-6972</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 27 Feb 2012 06:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-6972</guid>
		<description>What if you are using a proxy.pac on IE for proxy settings, how do u proceed in the shell because i also have the revocation check failure issue?</description>
		<content:encoded><![CDATA[<p>What if you are using a proxy.pac on IE for proxy settings, how do u proceed in the shell because i also have the revocation check failure issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-6914</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 24 Feb 2012 01:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-6914</guid>
		<description>Sorted...

I found in our case we needed to use an IP address vs a hostname, had to state the port as it was not a standard one, had to include a bypass for the domain the server was in,

netsh winhttp set proxy proxy-server=”http=192.168.0.1:8090;https=192.168.0.1:8090″ bypass-list=”*.mydomain.co.nz”

…after that we “refreshed” and CRL error disappeared and the certificate red x changed to a tick inidcating no issues.

We also had an invalid CRL URL in the Thawte certificate but thats another story we managed to sort with a host file entry pointing at the IP address of the correct server.</description>
		<content:encoded><![CDATA[<p>Sorted&#8230;</p>
<p>I found in our case we needed to use an IP address vs a hostname, had to state the port as it was not a standard one, had to include a bypass for the domain the server was in,</p>
<p>netsh winhttp set proxy proxy-server=”http=192.168.0.1:8090;https=192.168.0.1:8090″ bypass-list=”*.mydomain.co.nz”</p>
<p>…after that we “refreshed” and CRL error disappeared and the certificate red x changed to a tick inidcating no issues.</p>
<p>We also had an invalid CRL URL in the Thawte certificate but thats another story we managed to sort with a host file entry pointing at the IP address of the correct server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-6911</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 24 Feb 2012 00:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-6911</guid>
		<description>At what point does the CRL URL get checked? Can it be manually initiated?</description>
		<content:encoded><![CDATA[<p>At what point does the CRL URL get checked? Can it be manually initiated?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zannuzi</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-6018</link>
		<dc:creator>Zannuzi</dc:creator>
		<pubDate>Tue, 20 Dec 2011 01:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-6018</guid>
		<description>Excellent !!!! no where i could find this info. thankssss</description>
		<content:encoded><![CDATA[<p>Excellent !!!! no where i could find this info. thankssss</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-5649</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Fri, 25 Nov 2011 03:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-5649</guid>
		<description>Thanks for the info, this helped me alot!!</description>
		<content:encoded><![CDATA[<p>Thanks for the info, this helped me alot!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-4035</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Thu, 10 Feb 2011 21:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-4035</guid>
		<description>Thanks as well.. fixed my issues too!</description>
		<content:encoded><![CDATA[<p>Thanks as well.. fixed my issues too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chantal</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-3903</link>
		<dc:creator>Chantal</dc:creator>
		<pubDate>Thu, 13 Jan 2011 13:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-3903</guid>
		<description>Finally, we found that our proxy server was preventing the Exchange servers to access the required crl check 
URLs.

So we had to create a isa access rule to allow all exch servers to access the URLs and now, it works fine !</description>
		<content:encoded><![CDATA[<p>Finally, we found that our proxy server was preventing the Exchange servers to access the required crl check<br />
URLs.</p>
<p>So we had to create a isa access rule to allow all exch servers to access the URLs and now, it works fine !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil</title>
		<link>http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings#comment-3902</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Thu, 13 Jan 2011 01:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1795#comment-3902</guid>
		<description>Huge Thanks! Solved my issue.

Neil</description>
		<content:encoded><![CDATA[<p>Huge Thanks! Solved my issue.</p>
<p>Neil</p>
]]></content:encoded>
	</item>
</channel>
</rss>

