 




<?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: Server 2003 network &#8211; 2 NICS</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/server-2003-network-2-nics/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/server-2003-network-2-nics/</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 13:53:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: rbittel</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/server-2003-network-2-nics/#comment-52992</link>
		<dc:creator>rbittel</dc:creator>
		<pubDate>Wed, 30 Apr 2008 23:50:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-52992</guid>
		<description><![CDATA[Yes, you need to route traffic from the internal NIC to the external NIC. At a command prompt type in &quot;Route&#039; for more info.. I&#039;m not sure of the exact command syntax.]]></description>
		<content:encoded><![CDATA[<p>Yes, you need to route traffic from the internal NIC to the external NIC. At a command prompt type in &#8220;Route&#8217; for more info.. I&#8217;m not sure of the exact command syntax.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlees</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/server-2003-network-2-nics/#comment-51916</link>
		<dc:creator>jlees</dc:creator>
		<pubDate>Wed, 27 Feb 2008 06:40:01 +0000</pubDate>
		<guid isPermaLink="false">#comment-51916</guid>
		<description><![CDATA[Buddy is correct after you enable routing or internet connection sharing on your windows server. (Routing and Remote Access will do the same thing.)]]></description>
		<content:encoded><![CDATA[<p>Buddy is correct after you enable routing or internet connection sharing on your windows server. (Routing and Remote Access will do the same thing.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: buddyfarr</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/server-2003-network-2-nics/#comment-51740</link>
		<dc:creator>buddyfarr</dc:creator>
		<pubDate>Thu, 21 Feb 2008 17:25:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-51740</guid>
		<description><![CDATA[I do believe that you need to change the gateway for the workstations&#039; NICs in DHCP to the IP address of the internal NIC, not the comcast router. once they get directed to the internal NIC then the internal NIC will pass it onto the external NIC and then onto the comcast router.]]></description>
		<content:encoded><![CDATA[<p>I do believe that you need to change the gateway for the workstations&#8217; NICs in DHCP to the IP address of the internal NIC, not the comcast router. once they get directed to the internal NIC then the internal NIC will pass it onto the external NIC and then onto the comcast router.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.034 seconds using memcached
Object Caching 295/301 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-20 13:55:19 -->