<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MU" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Does the ISA Firewall Support VLAN Tagging?</title>
	<link>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/</link>
	<description>Written by Dr Thomas W Shinder, consultant to Microsoft, HP and many Fortune 500 companies on ISA firewall and Web proxy deployments this blog is where administrators get information about ISA Server Universal Threat Management firewalls. Topics include how to manage, deploy, and troubleshoot ISA Server as a network firewall, Web proxy/Web cache, remote access VPN server and VPN gateway to provide a high level of network security for all corporate computers.</description>
	<pubDate>Wed,  7 Jan 2009 18:13:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>

	<item>
		<title>by: MV</title>
		<link>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/#comment-14904</link>
		<pubDate>Wed, 18 Oct 2006 20:51:42 +0000</pubDate>
		<guid>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/#comment-14904</guid>
					<description>What about SP2 and the VB script in KB 912943?

At the end of the KB it says:

You cannot enable 802.1Q VLAN tagging and integrated NLB on the same interface of a network adapter. This limitation is imposed by NLB. (What Jim says above)

But then the KB also mentions:

You cannot enable both 802.1Q VLAN tagging and integrated NLB on different interfaces of a network adapter on ISA Server 2004, Enterprise Edition computers. To enable this functionality, you must install ISA Server 2004 SP2 and run the VBScript file that is described in the &quot;Resolution&quot; section.&quot;

So there is some support for it but not on the same interface....</description>
		<content:encoded><![CDATA[<p>What about SP2 and the VB script in KB 912943?</p>
<p>At the end of the KB it says:</p>
<p>You cannot enable 802.1Q VLAN tagging and integrated NLB on the same interface of a network adapter. This limitation is imposed by NLB. (What Jim says above)</p>
<p>But then the KB also mentions:</p>
<p>You cannot enable both 802.1Q VLAN tagging and integrated NLB on different interfaces of a network adapter on ISA Server 2004, Enterprise Edition computers. To enable this functionality, you must install ISA Server 2004 SP2 and run the VBScript file that is described in the &#8220;Resolution&#8221; section.&#8221;</p>
<p>So there is some support for it but not on the same interface&#8230;.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jim Harrison</title>
		<link>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/#comment-13580</link>
		<pubDate>Wed, 04 Oct 2006 18:55:32 +0000</pubDate>
		<guid>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/#comment-13580</guid>
					<description>NLB; not ISA, is the limiting factor here.
You can't use 802.1Q or 802.1ag with NLB because of the way NLB manipulates the packets.</description>
		<content:encoded><![CDATA[<p>NLB; not ISA, is the limiting factor here.<br />
You can&#8217;t use 802.1Q or 802.1ag with NLB because of the way NLB manipulates the packets.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Polom</title>
		<link>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/#comment-13572</link>
		<pubDate>Wed, 04 Oct 2006 15:12:38 +0000</pubDate>
		<guid>http://blogs.isaserver.org/shinder/2006/10/04/does-the-isa-firewall-support-vlan-tagging/#comment-13572</guid>
					<description>Hello Tom,

I'm using an ISA Server 2004 to filter the traffic between many VLAN and IPSec tunnels (aka &quot;remote sites&quot;). All my VLAN are managed on a team (802.3ad) of gb adapters and everything works fine.

The only major drawback of that technical choice (Windows Server and ISA in the heart of my network !) is that I have no way to implement fault tolerance :( I would have loved migrating to ISA Server EE but it's impossible, even for that such a critical system !

The reason is that, to my knowledge, there's no way to use both ISA's integrated NLB and 802.1Q.

In the long run it may lead me to use a different solution for my security need, because redundancy becomes a prerequisite for my company :-&amp;#124;

Any ideas are welcome !

Best regards,
Polom.</description>
		<content:encoded><![CDATA[<p>Hello Tom,</p>
<p>I&#8217;m using an ISA Server 2004 to filter the traffic between many VLAN and IPSec tunnels (aka &#8220;remote sites&#8221;). All my VLAN are managed on a team (802.3ad) of gb adapters and everything works fine.</p>
<p>The only major drawback of that technical choice (Windows Server and ISA in the heart of my network !) is that I have no way to implement fault tolerance <img src='http://blogs.isaserver.org/shinder/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  I would have loved migrating to ISA Server EE but it&#8217;s impossible, even for that such a critical system !</p>
<p>The reason is that, to my knowledge, there&#8217;s no way to use both ISA&#8217;s integrated NLB and 802.1Q.</p>
<p>In the long run it may lead me to use a different solution for my security need, because redundancy becomes a prerequisite for my company <img src='http://blogs.isaserver.org/shinder/wp-includes/images/smilies/icon_neutral.gif' alt=':-|' class='wp-smiley' /> </p>
<p>Any ideas are welcome !</p>
<p>Best regards,<br />
Polom.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
