cpeele
asked on
Any issues with changing Domain Controller IP to old DC address?
Setup: We have a domain with about 70 workstations and 2 Domain Controllers. One is Windows 2000 Server, and has been the only DC for years, controlling DHCP, DNS, WINS, file and print sharing. The other DC was added recently and is Windows Server 2003 R2 Standard. We added this one to ultimately take over all roles. We have already made it a DC, added all roles (except DHCP) and transferred FSMO roles. Everything looks good so far.
What we would like to do is take down the old server, and then change the IP of this new server to the one the old server had. That way, it's easier for us and the users. So the question is, can this be done (I am thinking yes) and are there any issues to look out for. Is this common? Any tips and advice would be great. Thanks.
What we would like to do is take down the old server, and then change the IP of this new server to the one the old server had. That way, it's easier for us and the users. So the question is, can this be done (I am thinking yes) and are there any issues to look out for. Is this common? Any tips and advice would be great. Thanks.
cluebeck
Sound all good to me. Although i have to say you should never really be using the ip-adress anyway, especially not normal users. Always use the DNS name that way you are more flexible.
As you are changing only IP address just check DNS if DNS entries are updated with new host name. There is a chance you will have one IP pointing to two host names.
I assume you will not demote the old DC first, just power it off. Don't forget to change the IP and disable the services before you reconnect it to network.
I assume you will not demote the old DC first, just power it off. Don't forget to change the IP and disable the services before you reconnect it to network.
ASKER
Thanks for the comments. Do you mean using the IP address for mappings? We tend to do this to ensure the shares can be reached. And if we change the IP of this server, we wouldn't have to change any mappings that include the IP. And we are so used to using the IP to access the server as well.
Any other comments welcome.
Any other comments welcome.
ASKER
Actually I was going to demote the old one first. Are you saying this is not the best approach?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
or off course you can change the IP of the old server in the same time and leave it on the network
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>>If you ever boot up the old server with the same IP and still a DNS server you might create a real nightmare.
That is why I wrote him to change the IP and disable services before reconnecting old server to network. Alternatively, he can leave the old one on network but must change the IP in the same time. This is much easier than a restore if anything goes wrong.
That is why I wrote him to change the IP and disable services before reconnecting old server to network. Alternatively, he can leave the old one on network but must change the IP in the same time. This is much easier than a restore if anything goes wrong.
ASKER
Thanks for the comments, both of you. This helps us a lot.
Thanks cpeele. Good luck with it.
Cheers !
--Rob
Cheers !
--Rob