<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/MU" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Stefaan Pouseele Blog</title>
	<link>http://blogs.isaserver.org/pouseele</link>
	<description>Stefaan Pouseele, an ISA Server MVP, discusses issues brought up within various ISA articles and Microsoft publications. Updates to the ISA Firewall, protocol support, discussions on the different ISA clients, ISA features, how to clean up network traffic and links to new ISA server literature are all be included within the blog. Get help on troubleshooting the ISA network firewall and learn how to create good security policies. Coverage on ISA Server 2006 also appears.</description>
	<pubDate>Fri, 14 Mar 2008 18:39:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<language>en</language>
	


		<item>
		<title>RAS Administration DLL - Useful on ISA Server?</title>
		<link>http://blogs.isaserver.org/pouseele/2007/12/22/ras-administration-dll-useful-on-isa-server/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/12/22/ras-administration-dll-useful-on-isa-server/#comments</comments>
		<pubDate>Sat, 22 Dec 2007 13:18:59 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/12/22/ras-administration-dll-useful-on-isa-server/</guid>
   		<description><![CDATA[I don't know if many ISA server guys and girls also read the Routing and Remote Access Blog but, because ISA makes extensively use of the Windows RAS features for the VPN stuff, it might be useful to follow that one too. <a href="http://blogs.isaserver.org/pouseele/2007/12/22/ras-administration-dll-useful-on-isa-server/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/12/22/ras-administration-dll-useful-on-isa-server/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>A lesson learned by debugging Silverlight through ISA Server</title>
		<link>http://blogs.isaserver.org/pouseele/2007/12/09/a-lesson-learned-by-debugging-silverlight-through-isa-server/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/12/09/a-lesson-learned-by-debugging-silverlight-through-isa-server/#comments</comments>
		<pubDate>Sun, 09 Dec 2007 09:10:52 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/12/09/a-lesson-learned-by-debugging-silverlight-through-isa-server/</guid>
   		<description><![CDATA[Let this be a lesson to all of us, just because someone complains about an application level problem doesn't mean it's always above layer-5 ... (Jim Harrison). Some time ago, I wanted to catch up on some TechEd 2007 videos published on the TechNet Spotlight site. However I was unable to play any Silverlight enabled video through an up-to-date ISA 2006 server as long as my IE 7 browser was configured as a Web Proxy client. <a href="http://blogs.isaserver.org/pouseele/2007/12/09/a-lesson-learned-by-debugging-silverlight-through-isa-server/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/12/09/a-lesson-learned-by-debugging-silverlight-through-isa-server/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Multiple L2TP/IPsec VPN clients behind a NAT device</title>
		<link>http://blogs.isaserver.org/pouseele/2007/11/24/multiple-l2tpipsec-vpn-clients-behind-a-nat-device/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/11/24/multiple-l2tpipsec-vpn-clients-behind-a-nat-device/#comments</comments>
		<pubDate>Sat, 24 Nov 2007 16:56:39 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/11/24/multiple-l2tpipsec-vpn-clients-behind-a-nat-device/</guid>
   		<description><![CDATA[An ever recurring topic on the message boards is the inability to connect to a VPN server with multiple VPN clients from behind a NAT device. We can assure you that if you run an up-to-date ISA 2004/2006 server, that means one with all the latest ISA and Windows service packs, the culprit is *not* the ISA server but definitely the NAT device not handling properly multiple VPN clients. In this blog we will analyze this scenario for L2TP/IPsec based VPN clients. <a href="http://blogs.isaserver.org/pouseele/2007/11/24/multiple-l2tpipsec-vpn-clients-behind-a-nat-device/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/11/24/multiple-l2tpipsec-vpn-clients-behind-a-nat-device/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Windows Media Player Authentication Prompts</title>
		<link>http://blogs.isaserver.org/pouseele/2007/11/09/windows-media-player-authentication-prompts/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/11/09/windows-media-player-authentication-prompts/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 18:10:54 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/11/09/windows-media-player-authentication-prompts/</guid>
   		<description><![CDATA[I want to share the following information provided by Jim Harrison about the random authentication prompts from Windows Media Player (WMP).  Problem: WMP sometimes displays authentication prompts even though the logged-on user account is resolvable by the ISA server and has permissions to access the content through the ISA server policies.  Scenario:  The ISA web proxy is configured for Windows Integrated authentication. The ISA server policies enforces authentication for HTTP traffic. <a href="http://blogs.isaserver.org/pouseele/2007/11/09/windows-media-player-authentication-prompts/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/11/09/windows-media-player-authentication-prompts/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Clearing the Cached WPAD Script</title>
		<link>http://blogs.isaserver.org/pouseele/2007/11/09/clearing-the-cached-wpad-script/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/11/09/clearing-the-cached-wpad-script/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 16:00:59 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/11/09/clearing-the-cached-wpad-script/</guid>
   		<description><![CDATA[When ISA server delivers the WPAD script, it sets a Cache-Control header with the value "max-age=3000", that means 50 minutes. Internet Explorer rounds this up to 1 hour. So, if you are testing WPAD changes, i.e. you are playing with "Auto Discovery" or "Direct Access", then you will need to be sure to delete the previously acquired WPAD script and resolved WPAD name. <a href="http://blogs.isaserver.org/pouseele/2007/11/09/clearing-the-cached-wpad-script/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/11/09/clearing-the-cached-wpad-script/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Certificate Enrollment Requires a Custom Protocol</title>
		<link>http://blogs.isaserver.org/pouseele/2007/10/12/certificate-enrollment-requires-a-custom-protocol/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/10/12/certificate-enrollment-requires-a-custom-protocol/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 13:25:54 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/10/12/certificate-enrollment-requires-a-custom-protocol/</guid>
   		<description><![CDATA[When you request a certificate using the Certificate MMC snap-in or the certificate auto-enrollment mechanism, the request fails. Of course we assume here that the CA is started and you have sufficient permissions to request a certificate. This issue occurs because DCOM is required to acquire a certificate. However, for access rules a default "Enable strict RPC compliance" setting is configured on each RPC rule. <a href="http://blogs.isaserver.org/pouseele/2007/10/12/certificate-enrollment-requires-a-custom-protocol/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/10/12/certificate-enrollment-requires-a-custom-protocol/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>ISA Server and Windows Server 2003 Service Pack 2</title>
		<link>http://blogs.isaserver.org/pouseele/2007/08/16/isa-server-and-windows-server-2003-service-pack-2/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/08/16/isa-server-and-windows-server-2003-service-pack-2/#comments</comments>
		<pubDate>Thu, 16 Aug 2007 16:10:47 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/08/16/isa-server-and-windows-server-2003-service-pack-2/</guid>
   		<description><![CDATA[The ISA Server product team blog ISA Server and Windows Server 2003 Service Pack 2 states that it might be necessary to disable receive-side scaling (RSS) when running an ISA server on Windows 2003 SP2. In fact, according to Jim Harrison it is absolutely recommended to disable receive-side scaling *and* offload support in the TCP/IP stack. <a href="http://blogs.isaserver.org/pouseele/2007/08/16/isa-server-and-windows-server-2003-service-pack-2/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/08/16/isa-server-and-windows-server-2003-service-pack-2/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Testing RPC over HTTP through ISA Server 2006</title>
		<link>http://blogs.isaserver.org/pouseele/2007/08/14/testing-rpc-over-http-through-isa-server-2006/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/08/14/testing-rpc-over-http-through-isa-server-2006/#comments</comments>
		<pubDate>Tue, 14 Aug 2007 18:54:13 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/08/14/testing-rpc-over-http-through-isa-server-2006/</guid>
   		<description><![CDATA[You can read Jim Harrison's definitive guide at:   Testing RPC over HTTP through ISA Server 2006 Part 1; Protocols, Authentication and Processing  Testing RPC over HTTP through ISA Server 2006 Part 2; Test Tools and Strategies  Testing RPC over HTTP through ISA Server 2006 Part 3; Common Failures and Resolutions HTH, Stefaan. <a href="http://blogs.isaserver.org/pouseele/2007/08/14/testing-rpc-over-http-through-isa-server-2006/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/08/14/testing-rpc-over-http-through-isa-server-2006/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Basic Troubleshooting for IPsec based VPN&#8217;s</title>
		<link>http://blogs.isaserver.org/pouseele/2007/07/07/basic-troubleshooting-for-ipsec-based-vpns/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/07/07/basic-troubleshooting-for-ipsec-based-vpns/#comments</comments>
		<pubDate>Sat, 07 Jul 2007 09:39:13 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/07/07/basic-troubleshooting-for-ipsec-based-vpns/</guid>
   		<description><![CDATA[Troubleshooting IPsec based VPN's can be very challenging. The reason for this&nbsp;is that you need to have a thorough knowledge of the&nbsp;IPsec protocol. Moreover, how to enable and&nbsp;interpret the more advanced IPsec diagnostic logging, more precisely the Oakley log, is not very well documented. In this short article we will summarise some troubleshooting steps you can apply to the IPsec part of the VPN. <a href="http://blogs.isaserver.org/pouseele/2007/07/07/basic-troubleshooting-for-ipsec-based-vpns/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/07/07/basic-troubleshooting-for-ipsec-based-vpns/feed/</wfw:commentRSS>
   		</item>
		<item>
		<title>Multiple PPTP VPN clients behind a NAT device</title>
		<link>http://blogs.isaserver.org/pouseele/2007/06/17/multiple-pptp-vpn-clients-behind-a-nat-device/</link>
		<comments>http://blogs.isaserver.org/pouseele/2007/06/17/multiple-pptp-vpn-clients-behind-a-nat-device/#comments</comments>
		<pubDate>Sun, 17 Jun 2007 20:58:28 +0000</pubDate>
		<dc:creator>Stefaan Pouseele</dc:creator>
		
	<category>ISA Corner</category>
		<guid isPermaLink="false">http://blogs.isaserver.org/pouseele/2007/06/17/multiple-pptp-vpn-clients-behind-a-nat-device/</guid>
   		<description><![CDATA[An ever recurring topic on the message boards is the&nbsp;inability to connect&nbsp;to a VPN server with multiple VPN clients from behind a NAT device. We can assure you that if you run an up-to-date ISA 2004/2006 server, that means one with all the latest ISA and Windows service packs, the culprit is *not* the ISA server but definitely the NAT device not handling properly multiple VPN clients. In this blog we will analyse this&nbsp;scenario&nbsp;for PPTP based VPN clients. <a href="http://blogs.isaserver.org/pouseele/2007/06/17/multiple-pptp-vpn-clients-behind-a-nat-device/">more...</a>]]></description>

   		<wfw:commentRSS>http://blogs.isaserver.org/pouseele/2007/06/17/multiple-pptp-vpn-clients-behind-a-nat-device/feed/</wfw:commentRSS>
   		</item>
	

</channel>
</rss>
