<?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: SharePoint / ISA AAM and SSL Termination issue</title>
	<atom:link href="http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/</link>
	<description>My thoughts on all things IT</description>
	<lastBuildDate>Fri, 18 Dec 2009 21:17:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Quick update to ISA and SSL termination issue &#171; Hugheser&#8217;s IT Blog</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-471</link>
		<dc:creator>Quick update to ISA and SSL termination issue &#171; Hugheser&#8217;s IT Blog</dc:creator>
		<pubDate>Wed, 16 Dec 2009 14:52:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-471</guid>
		<description>[...] posted about this a few times here.  More Here and Here.  This problem no longer affects my installation but it looks like Microsoft has released a fix.  [...]</description>
		<content:encoded><![CDATA[<p>[...] posted about this a few times here.  More Here and Here.  This problem no longer affects my installation but it looks like Microsoft has released a fix.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-469</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 16 Dec 2009 14:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-469</guid>
		<description>Check here for another update. http://www.hugheserblog.com/2009/12/16/quick-update-to-isa-and-ssl-termination-issue/</description>
		<content:encoded><![CDATA[<p>Check here for another update. <a href="http://www.hugheserblog.com/2009/12/16/quick-update-to-isa-and-ssl-termination-issue/" rel="nofollow">http://www.hugheserblog.com/2009/12/16/quick-update-to-isa-and-ssl-termination-issue/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-435</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 08 Dec 2009 14:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-435</guid>
		<description>Vanathi, 
Unfortunately no.  My work around was to have a unique internal IP for each web application on each web frontend.  That fixed it but I wouldn&#039;t say it is ideal.  They are internal IPs so we have plenty but it makes hurts manageability.
James above mentions disabling Link translation fixed it for him.  Unfortunately that didn&#039;t help in my case.  Good luck and if you find a solution, please let me know so I can update the post.</description>
		<content:encoded><![CDATA[<p>Vanathi,<br />
Unfortunately no.  My work around was to have a unique internal IP for each web application on each web frontend.  That fixed it but I wouldn&#8217;t say it is ideal.  They are internal IPs so we have plenty but it makes hurts manageability.<br />
James above mentions disabling Link translation fixed it for him.  Unfortunately that didn&#8217;t help in my case.  Good luck and if you find a solution, please let me know so I can update the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathi</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-414</link>
		<dc:creator>Nathi</dc:creator>
		<pubDate>Tue, 24 Nov 2009 04:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-414</guid>
		<description>Hi

Any solution found for this issue. We are getting the same problem with the similar setup in our end. Any help would be appreciated.

Thanks
Vanathi</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>Any solution found for this issue. We are getting the same problem with the similar setup in our end. Any help would be appreciated.</p>
<p>Thanks<br />
Vanathi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-322</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 27 Oct 2009 14:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-322</guid>
		<description>I finally got around to looking into the link translation.  It still has the same problem when it is turned off.  In fact, I had it turned off before I went ahead and disabled SSL termination.  Maybe there is something else causing it.  Regardless, having SSL all the way through is fine.  It may add to the load a bit but I doubt it is significant.  We are also having other services setup close so SSL is a good idea at this point.</description>
		<content:encoded><![CDATA[<p>I finally got around to looking into the link translation.  It still has the same problem when it is turned off.  In fact, I had it turned off before I went ahead and disabled SSL termination.  Maybe there is something else causing it.  Regardless, having SSL all the way through is fine.  It may add to the load a bit but I doubt it is significant.  We are also having other services setup close so SSL is a good idea at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-244</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 14 Oct 2009 19:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-244</guid>
		<description>Interesting.  I tried disabling it but it didn&#039;t seem to make a difference.  I even tried using the link translation to translate it back to itself as well as several other crazy things.  I may hop on the test farm and see if I was overlooking something with link translation.

Thanks for the feedback.</description>
		<content:encoded><![CDATA[<p>Interesting.  I tried disabling it but it didn&#8217;t seem to make a difference.  I even tried using the link translation to translate it back to itself as well as several other crazy things.  I may hop on the test farm and see if I was overlooking something with link translation.</p>
<p>Thanks for the feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Murray</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-243</link>
		<dc:creator>James Murray</dc:creator>
		<pubDate>Wed, 14 Oct 2009 19:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-243</guid>
		<description>Hi

I stumbled across this post and I&#039;ve read the updated one. I had exactly the same problem and run it just as you do in your diagram.

What I found was when I turned Link Translation off on the ISA firewall that sharepoint was more than capable of handling the link translation and the errors I was getting dissappeared while still running on port 80.

Link translation is turned on by default on the ISA server rule even if you tell it that link translation has already been configured so you actually have to go into the Listner itself and turn it off

Hope this helps
James</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>I stumbled across this post and I&#8217;ve read the updated one. I had exactly the same problem and run it just as you do in your diagram.</p>
<p>What I found was when I turned Link Translation off on the ISA firewall that sharepoint was more than capable of handling the link translation and the errors I was getting dissappeared while still running on port 80.</p>
<p>Link translation is turned on by default on the ISA server rule even if you tell it that link translation has already been configured so you actually have to go into the Listner itself and turn it off</p>
<p>Hope this helps<br />
James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SharePoint / ISA AAM and SSL Termination issue UPDATE &#171; Hugheser&#8217;s IT Blog</title>
		<link>http://www.hugheserblog.com/2009/06/05/sharepoint-isa-aam-and-ssl-termination-issue/comment-page-1/#comment-207</link>
		<dc:creator>SharePoint / ISA AAM and SSL Termination issue UPDATE &#171; Hugheser&#8217;s IT Blog</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hugheserblog.com/?p=14#comment-207</guid>
		<description>[...] attention to what brings people to my site.  Currently one of the most popular posts is this one: SharePoint / ISA AAM and SSL Termination issue.  This really bothered me because I was never able to provide a solution.  It wasn&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[...] attention to what brings people to my site.  Currently one of the most popular posts is this one: SharePoint / ISA AAM and SSL Termination issue.  This really bothered me because I was never able to provide a solution.  It wasn&#8217;t [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
