 




<?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: Changing IP addresses, domain wide, on Windows 2000 AD network</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/changing-ip-addresses-domain-wide-on-windows-2000-ad-network/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/changing-ip-addresses-domain-wide-on-windows-2000-ad-network/</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 03:14:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: bobkberg</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/changing-ip-addresses-domain-wide-on-windows-2000-ad-network/#comment-37078</link>
		<dc:creator>bobkberg</dc:creator>
		<pubDate>Mon, 25 Apr 2005 13:57:22 +0000</pubDate>
		<guid isPermaLink="false">#comment-37078</guid>
		<description><![CDATA[First step is to apply the new IP addressing structure as secondary/additional (depending on the vendor definition) so that the two networks overlay one another, and you don&#039;t lose connectivity to anything during the migration.

Then proceed as suggested above by ramheka

Once you have most of the work accomplished, then set sniffers at various points in the network to check for non-compliant addresses so that you can go back and catch the systems that fell through the cracks - and there are ALWAYS some.

Bob
]]></description>
		<content:encoded><![CDATA[<p>First step is to apply the new IP addressing structure as secondary/additional (depending on the vendor definition) so that the two networks overlay one another, and you don&#8217;t lose connectivity to anything during the migration.</p>
<p>Then proceed as suggested above by ramheka</p>
<p>Once you have most of the work accomplished, then set sniffers at various points in the network to check for non-compliant addresses so that you can go back and catch the systems that fell through the cracks &#8211; and there are ALWAYS some.</p>
<p>Bob</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.012 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-19 04:21:39 -->