Change ip address windows 2000 domain controller

I need to know what are the impacts and considerations of changing the following solution's local IP Address in the worst case scenario. Please help me with suggesting the list of Business Impacts and Role Back plan. Attachments: Up to 10 attachments including images can be used with a maximum of 3. RonyPaul ,.

How are things going on your end? Please keep me posted on this issue. If you have any further questions or concerns about this question, please let us know. I appreciate your time and efforts. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hello RonyPaul ,. Would you please tell me how things are going on your side. If you have any questions or concerns about the information I provided, please don't hesitate to let us know. If the Answer is helpful, please click " Accept Answer " and upvote it. Best regards, Wendy Please remember to mark the replies as answers if they help and unmark them if they provide no help. Monday, October 24, AM. Regards, Hi Agree with other,you can change ip address of a domain controller,follow the articles which others shared.

Monday, October 24, PM. Tuesday, October 25, AM. It is not mandatory - but it's something you should consider for redundancy reasons the best practice Does it mean that the DC must be unpromoted before change the IP address? Not necessary - simply change the IP address on the existing DC and follow the steps described in the earlier responses to your question above When the LDAP synchronization is done between the 2 DC servers, do the same for the second DC server?

If your intention is to change the IP address of other domain controllers, then yes, you would follow the same procedure hth Marcin. Hello, Can you confirm that a secondary DC server is mandatory? Who are the certified experts? How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk. We're a community of IT professionals committed to sharing knowledge.

Our experts volunteer their time to help other people in the technology industry learn and succeed. Plans and Pricing. Any caveats there? Make sure that DNS is updated properly as well. If you need to migrate all servers to the new range, plan, plan and plan again, don't think it's as simple as moving an IP on all systems, some do not like IP changes, migration is going to be your friend for some systems, be sure you document changes in case you need a way out.

I would simply add the new IP to the existing DCs. You can give them multiple addresses in different subnets without an issue. That will give you time to migrate things over. Monitor the old IP with Wireshark and hunt down every connection you see until you've killed all external references.

Then, you can remove the old IP. Why are you doing this at all? I have been known to take a new DC, configure it in one subnet, and them move it to its final subnet when it goes into production. I try really really hard to never take away a DNS or DHCP server that has been in production use, as there may be lots of statically assigned devices and even DHCP relay agents that would need to be reconfigured.

It's modifying all of those other things that is difficult. If you have DCs on