 




<?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: Win 2000 Server as IP Router</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/win-2000-server-as-ip-router/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/win-2000-server-as-ip-router/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 10:29:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Terrell Dolmajian</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/win-2000-server-as-ip-router/#comment-73454</link>
		<dc:creator>Terrell Dolmajian</dc:creator>
		<pubDate>Thu, 04 Feb 2010 16:24:38 +0000</pubDate>
		<guid isPermaLink="false">#comment-73454</guid>
		<description><![CDATA[Your article&#039;s topic has been one of my keenest interests for years. It&#039;s good to find someone else who shares my deepest passion.]]></description>
		<content:encoded><![CDATA[<p>Your article&#8217;s topic has been one of my keenest interests for years. It&#8217;s good to find someone else who shares my deepest passion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gregnottage</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/win-2000-server-as-ip-router/#comment-44021</link>
		<dc:creator>gregnottage</dc:creator>
		<pubDate>Thu, 22 Sep 2005 10:27:36 +0000</pubDate>
		<guid isPermaLink="false">#comment-44021</guid>
		<description><![CDATA[Cool, thanks for the info.  Setting up NAT worked like a charm!

I now have a fully working router ;-)

Thank-you very much for your kind assistance, it&#039;s hugely appreciated.

Kindest Regards,

Greg.]]></description>
		<content:encoded><![CDATA[<p>Cool, thanks for the info.  Setting up NAT worked like a charm!</p>
<p>I now have a fully working router <img src='http://itknowledgeexchange.techtarget.com/itanswers/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Thank-you very much for your kind assistance, it&#8217;s hugely appreciated.</p>
<p>Kindest Regards,</p>
<p>Greg.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: humblenetadmin</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/win-2000-server-as-ip-router/#comment-44022</link>
		<dc:creator>humblenetadmin</dc:creator>
		<pubDate>Wed, 21 Sep 2005 16:56:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-44022</guid>
		<description><![CDATA[You may need to put a route in your firewall going back to the 2000 server box interface that the firewall is attached to.

I just recently setup a linux box as a router with eth0 as 111.111.111.160 and eht1 as 192.168.1.254

computers on the 111 network could not get to the computers on the 192 network and vice versa.

My firewall is on the 111 network and when I put the route
192.168.1.0/24 in the router then all was well.

The reason is that all clients on the 111 network have gateways to the IP of the firewall, as well as does the eth0 of the linux router box. So any traffic destined for an IP that cant be found on the network is then directed to the firewall. For the 192 network, the eth0 111.111.111.160 routed traffic for the 111 network to the default gateway of eth0 which is the firewall, and it had no routing info.

The route 192.168.1.0/24 111.111.111.160 in the firewall basically states, any traffic from the 111 network destined for the 192 network goes to 111.111.111.160 network interface eth0 on the linux router box, and any traffic from the 192 network to the 111 network follows the route to the firewall and then is routed to the 111 network.

Hope this is not to confusing and actually is of some help

The HumbleNetAdmin]]></description>
		<content:encoded><![CDATA[<p>You may need to put a route in your firewall going back to the 2000 server box interface that the firewall is attached to.</p>
<p>I just recently setup a linux box as a router with eth0 as 111.111.111.160 and eht1 as 192.168.1.254</p>
<p>computers on the 111 network could not get to the computers on the 192 network and vice versa.</p>
<p>My firewall is on the 111 network and when I put the route<br />
192.168.1.0/24 in the router then all was well.</p>
<p>The reason is that all clients on the 111 network have gateways to the IP of the firewall, as well as does the eth0 of the linux router box. So any traffic destined for an IP that cant be found on the network is then directed to the firewall. For the 192 network, the eth0 111.111.111.160 routed traffic for the 111 network to the default gateway of eth0 which is the firewall, and it had no routing info.</p>
<p>The route 192.168.1.0/24 111.111.111.160 in the firewall basically states, any traffic from the 111 network destined for the 192 network goes to 111.111.111.160 network interface eth0 on the linux router box, and any traffic from the 192 network to the 111 network follows the route to the firewall and then is routed to the 111 network.</p>
<p>Hope this is not to confusing and actually is of some help</p>
<p>The HumbleNetAdmin</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 6/9 queries in 0.017 seconds using memcached
Object Caching 300/303 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 10:57:47 -->