And, of course, that would also bring up another point to check... the NAT to make sure it's correct again. Joe Heaton
________________________________ From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2008 8:08 AM To: NT System Admin Issues Subject: Re: Changing ip of DC and Exchange server One would hope he had an FE server somewhere along the line... Not to mention, one would hope he didn't have a publicly assigned address on his Exchange box and was instead NATing the address on the firewall thus removing any need to mess with the MX record... Hope, one would.. On Tue, Mar 11, 2008 at 8:00 AM, Joe Heaton <[EMAIL PROTECTED]> wrote: Don't forget your external MX record. Joe Heaton ________________________________ From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 8:37 PM To: NT System Admin Issues Subject: Changing ip of DC and Exchange server I have a W2k3 DC and Exchange server I need to reassign a new IP. Aside from DNS reflecting the actual data versus the old, what other things might I encounter? As long as DNS gets updated (which would even happen on its own over time) I can't think of anything else to worry about? Thanks, jlc ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
