 




<?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: Will NAT66 provide network address translation in IPv6?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/will-nat66-provide-network-address-translation-in-ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/will-nat66-provide-network-address-translation-in-ipv6/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 14:11:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: edotto</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/will-nat66-provide-network-address-translation-in-ipv6/#comment-109682</link>
		<dc:creator>edotto</dc:creator>
		<pubDate>Mon, 30 Jul 2012 16:49:57 +0000</pubDate>
		<guid isPermaLink="false">#comment-109682</guid>
		<description><![CDATA[&lt;p&gt;One of the issues I&#039;ve come across in my experience is deeper than this; it&#039;s setting up a corporate network w/o subnetting and using dynamic IP addresses.&lt;/p&gt;&lt;p&gt;This combination makes it almost impossible to trace issues because you don&#039;t know where machines are in a building.&#160; The largest corporate network I have seen this with is 1K machines - and when 100 of them are in the same room, and you have uneducated users, trying to figure out which machine(s) have software broadcast issues, for one example, render this impossible to trace without interrupting everyone&#039;s work to gather the current IP address(es). Do away with NAT and dynamic IPs in your environment and you&#039;ll be MUCH better equipped to deal with network issues.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>One of the issues I&#8217;ve come across in my experience is deeper than this; it&#8217;s setting up a corporate network w/o subnetting and using dynamic IP addresses.</p>
<p>This combination makes it almost impossible to trace issues because you don&#8217;t know where machines are in a building.&nbsp; The largest corporate network I have seen this with is 1K machines &#8211; and when 100 of them are in the same room, and you have uneducated users, trying to figure out which machine(s) have software broadcast issues, for one example, render this impossible to trace without interrupting everyone&#8217;s work to gather the current IP address(es). Do away with NAT and dynamic IPs in your environment and you&#8217;ll be MUCH better equipped to deal with network issues.</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.047 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 14:26:42 -->