Nothing should happen if all done well. Note the ability for network devices and operating systems and applications to cache previously used IP. Hence the delay in getting the correct IP / name combination to work. /Gill > -----Original Message----- > From: mino.faggiano@xxxxxxxxxxx [mailto:mino.faggiano@xxxxxxxxxxx] > Sent: Monday, January 10, 2005 12:50 PM > To: [ExchangeList] > Subject: [exchangelist] Changing the IP address of an > existing Exchange 2003 /Win2K3 DC > > http://www.MSExchange.org/ > > I Plan on performing an exchange migration from 5.5 to 2003. > I would like to maintain the IP address of the original > server (saves hassle of changing MX records and firewall > NAT). Does anyone know if this presents as a problem? It is > also the primary DNS / DHCP server. > > ------------------------------------------------------ > List Archives: > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp > Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ > ------------------------------------------------------ > Other Internet Software Marketing Sites: > World of Windows Networking: http://www.windowsnetworking.com > Leading Network Software Directory: http://www.serverfiles.com > No.1 ISA Server Resource Site: http://www.isaserver.org > Windows Security Resource Site: > http://www.windowsecurity.com/ Network Security Library: > http://www.secinf.net/ Windows 2000/NT Fax Solutions: > http://www.ntfaxfaq.com > ------------------------------------------------------ > You are currently subscribed to this MSEXchange.org > Discussion List as: ssgill@xxxxxxxxxxxxxxxxxxxx To > unsubscribe visit > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Report abuse to listadmin@xxxxxxxxxxxxxx
