Computer Help Forums: Change IP Address to a domain controller which is also exchange se - Computer Help Forums

Hi

Anybody knows the proper procedure to change the ip address to a domain
controller that happens to be our exchange server too.

Thanks in advance

"mosquito_hippy" wrote in message news:FD732212-AE69-4DB1-AA8A-23F7E93114F0@microsoft.com...
> Hi
>
> Anybody knows the proper procedure to change the ip address to a domain
> controller that happens to be our exchange server too.
>
> Thanks in advance


It would be more helpful if you provided more info, such as do you just want to change the IP of the domain controller, or the whole network? Is DHCP running on this machine, how many users do you have, printers with IPs, any other resources that may be port remapped from your NAT/firewall, etc.

Is this SBS or non-SBS?

First, it is suggested to not put Exchange on a DC. The changes a DC makes vastly hits Exchange in the performance area, as well as may cause issues with the databases and transaction logs, because a DC disables write-behind cache on the machine, a non-reversible setting as long as it is a DC.

As for changing IPs:

Instruct everyone to shut down their machines on the Friday before the weekend that you plan the IP change.

Change the internal interface on your router/NAT/firewall first. Connect to it either using a web interface or telnet.

Then change IPs on your printers to the planned IP they will have. Either connect to them using a web browser, or simply change them on their console, depending on the printer manufacturer.

Then on the DC, assuming the DC is single homed (one NIC) and not two NICs (another issue with DCs if more than one NIC or IP), simply change the IP on it, then run:
ipconfig /registerdns
net stop netlogon
net start netlogon

Then assuming DHCP, you will need to recreate the scope, and the scope options (DNS, WINS, gateway, etc.)

I hope that helps.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay

Thanks Ace

Yes, first, i know shouldn't be installed exchange on the dc but i hadn't
too much options back then.

From your explanation i conclude that exchange won't need any change, is
that correct?


Thanks in advance




"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "mosquito_hippy" wrote in message news:FD732212-AE69-4DB1-AA8A-23F7E93114F0@microsoft.com...
> > Hi
> >
> > Anybody knows the proper procedure to change the ip address to a domain
> > controller that happens to be our exchange server too.
> >
> > Thanks in advance
>
>
> It would be more helpful if you provided more info, such as do you just want to change the IP of the domain controller, or the whole network? Is DHCP running on this machine, how many users do you have, printers with IPs, any other resources that may be port remapped from your NAT/firewall, etc.
>
> Is this SBS or non-SBS?
>
> First, it is suggested to not put Exchange on a DC. The changes a DC makes vastly hits Exchange in the performance area, as well as may cause issues with the databases and transaction logs, because a DC disables write-behind cache on the machine, a non-reversible setting as long as it is a DC.
>
> As for changing IPs:
>
> Instruct everyone to shut down their machines on the Friday before the weekend that you plan the IP change.
>
> Change the internal interface on your router/NAT/firewall first. Connect to it either using a web interface or telnet.
>
> Then change IPs on your printers to the planned IP they will have. Either connect to them using a web browser, or simply change them on their console, depending on the printer manufacturer.
>
> Then on the DC, assuming the DC is single homed (one NIC) and not two NICs (another issue with DCs if more than one NIC or IP), simply change the IP on it, then run:
> ipconfig /registerdns
> net stop netlogon
> net start netlogon
>
> Then assuming DHCP, you will need to recreate the scope, and the scope options (DNS, WINS, gateway, etc.)
>
> I hope that helps.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> aceman@mvps.RemoveThisPart.org
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>
>
>
>
>
>

"mosquito_hippy" wrote in message news:670FFEEF-73C7-4A09-A236-AD9DA98E103F@microsoft.com...
> Thanks Ace
>
> Yes, first, i know shouldn't be installed exchange on the dc but i hadn't
> too much options back then.
>
> From your explanation i conclude that exchange won't need any change, is
> that correct?
>
>
> Thanks in advance


Exchange is part of the OS, so no, unless you have specified something in the allow to relay in IIS or specified a specific IP for the SMTP service to use? I don't know if you changed anything from default with the limited info you provided, so not sure how to answer. Also, you are talking about Exchange 2003?

Of course you will have to change the port remaps on your firewall.

Ace