Comments on: How To: Change a Domain Controller IP address: Multi-DCs http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/ totalnetsolutions.net - Complete Networking Solutions for business Fri, 26 Feb 2010 20:40:30 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: what is my ip address http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-13693 what is my ip address Wed, 16 Sep 2009 07:09:11 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-13693 Thanks for wonderful post. Please direct me to a link with more information. thankya. Thanks for wonderful post. Please direct me to a link with more information. thankya.

]]> By: Robert http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-5153 Robert Tue, 13 Jan 2009 01:40:09 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-5153 the FSMO roles won't be affected by the change as long as it's performed according to the instructions. The Print server and DFS functions are also based on DNS (or WINS) name, not direct IP, so will also be unaffected. Your DHCP scope will have to be updated to reflect the new information, and any DNS client will have to be edited to point to the new IP. If every client is DHCP (printers, linux systems, etc.), then updating the DHCP scope is all you need to do. After you've updated the scope (at the end of the DNS change), reboot every device in the network so that it gets the new addresses (or do an "ipconfig /release && ipconfig /renew" on windows systems). the FSMO roles won’t be affected by the change as long as it’s performed according to the instructions. The Print server and DFS functions are also based on DNS (or WINS) name, not direct IP, so will also be unaffected.
Your DHCP scope will have to be updated to reflect the new information, and any DNS client will have to be edited to point to the new IP. If every client is DHCP (printers, linux systems, etc.), then updating the DHCP scope is all you need to do. After you’ve updated the scope (at the end of the DNS change), reboot every device in the network so that it gets the new addresses (or do an “ipconfig /release && ipconfig /renew” on windows systems).

]]> By: Dilesh http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-5023 Dilesh Fri, 09 Jan 2009 05:08:09 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-5023 Hi, I am planning to change the TCP IP address of the Windows 2003 Server Domain Controller having DNS,DHCP,DFS,Print Server. MY DC is replicating with another DC having all the 5 FSMO roles. What effect will it have on DNS and DHCP Scopes and reservation. Hi,

I am planning to change the TCP IP address of the Windows 2003 Server Domain Controller having DNS,DHCP,DFS,Print Server. MY DC is replicating with another DC having all the 5 FSMO roles. What effect will it have on DNS and DHCP Scopes and reservation.

]]> By: Robert http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1557 Robert Fri, 22 Aug 2008 05:04:18 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1557 If you want to remove a DC (format the HDD), you have to run DCPRomo again, but that will make a change to the whole domain. If it's a DNS server as well, you can, after DCPromoing it, put a standalone secondary DNS server in it's place. Otherwise, you'll have to make some changes to the DNS placement in your environment. If you want to remove a DC (format the HDD), you have to run DCPRomo again, but that will make a change to the whole domain. If it’s a DNS server as well, you can, after DCPromoing it, put a standalone secondary DNS server in it’s place. Otherwise, you’ll have to make some changes to the DNS placement in your environment.

]]> By: balan http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1490 balan Tue, 19 Aug 2008 04:56:07 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1490 how can format dc with don't any change in domain host infrastructure. how can format dc with don’t any change in domain host infrastructure.

]]> By: Robert http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1447 Robert Thu, 14 Aug 2008 23:06:15 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1447 Likely the proxy server is failing to authenticate your users, but without knowing the proxy product in use, it's nearly impossible to troubleshoot remotely. However, give us a call or email from the contact page, and we'll try to help you out! Likely the proxy server is failing to authenticate your users, but without knowing the proxy product in use, it’s nearly impossible to troubleshoot remotely. However, give us a call or email from the contact page, and we’ll try to help you out!

]]> By: balan http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1442 balan Thu, 14 Aug 2008 10:38:39 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1442 my server running 4 rolls (dc, dns ,proxy,web). Recently i faced one problem hosts connect any website display authentication required. Please tell my solution. my server running 4 rolls (dc, dns ,proxy,web). Recently i faced one problem hosts connect any website display authentication required. Please tell my solution.

]]> By: Robert http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1352 Robert Thu, 31 Jul 2008 04:14:22 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1352 When the client comes back, they'll remember the last lease (or few, depending on OS) they held (the last one period, whether a coffee shop, or home, or work) for that network card. The client will send a broadcast request to have that IP address again. If the request is invalid for the network, or has been handed out on the network, the DHCP server will send a "DHCPNACK" to the client, and the client will have to do a complete request cycle before an address will be assigned to the adapter. Some newer OSes will also, if DHCP fails completely, attempt to bind the last leased address to the card and test that configuration, to see if they *happen* to be in the last network, and the DHCP server just *happens* to be down. This is a feature, and not part of the DHCP RFC as I last read it. When the client comes back, they’ll remember the last lease (or few, depending on OS) they held (the last one period, whether a coffee shop, or home, or work) for that network card. The client will send a broadcast request to have that IP address again. If the request is invalid for the network, or has been handed out on the network, the DHCP server will send a “DHCPNACK” to the client, and the client will have to do a complete request cycle before an address will be assigned to the adapter.
Some newer OSes will also, if DHCP fails completely, attempt to bind the last leased address to the card and test that configuration, to see if they *happen* to be in the last network, and the DHCP server just *happens* to be down. This is a feature, and not part of the DHCP RFC as I last read it.

]]> By: Karl http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1342 Karl Tue, 29 Jul 2008 11:45:39 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1342 Hi Robert If a client on a network leases an IP and it expires while the client is away, the server will eventually lease it to another client. If the user that leased it in the first place plugs back into the network, will they then get a conflict, since the server has already leased it to another client? Hi Robert

If a client on a network leases an IP and it expires while the client is away, the server will eventually lease it to another client. If the user that leased it in the first place plugs back into the network, will they then get a conflict, since the server has already leased it to another client?

]]> By: Robert http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/comment-page-1/#comment-1337 Robert Tue, 29 Jul 2008 02:13:42 +0000 http://www.totalnetsolutions.net/2007/10/08/how-to-change-a-domain-controller-ip-address-multi-dcs/#comment-1337 The cleanup steps are required in a place where you're removing the old subnet. In my personal experience, removing an old subnet is one of the primary reasons for changing the IP of a DC. If your business is keeping the old subnet, what is the driving motivation to changing the DC address, rather than just adding a new routed subnet to the network, and adding the new subnet to the existing site in AD? If you need a DC in the new subnet, it's safe to say that the new subnet is in a new AD site (A site is a network connected to other networks by slow links). If that's the case, don't you still need a DC in the old site, and wouldn't it therefore be better to build a new DC entirely? So you're correct - don't perform the cleanup steps to *AD* if you're leaving clients in those subnets, but you DEFINATELY want to remove the unused IP addresses from the DC, so that it doesn't register those IP addresses in DNS, and send clients to an address that doesn't exist. On that note, i also don't suggest DCs with multiple bound IPs - buy networking equipment to handle networking and routing, and let your servers and hosts do serving and hosting. The cleanup steps are required in a place where you’re removing the old subnet. In my personal experience, removing an old subnet is one of the primary reasons for changing the IP of a DC. If your business is keeping the old subnet, what is the driving motivation to changing the DC address, rather than just adding a new routed subnet to the network, and adding the new subnet to the existing site in AD?
If you need a DC in the new subnet, it’s safe to say that the new subnet is in a new AD site (A site is a network connected to other networks by slow links). If that’s the case, don’t you still need a DC in the old site, and wouldn’t it therefore be better to build a new DC entirely?
So you’re correct – don’t perform the cleanup steps to *AD* if you’re leaving clients in those subnets, but you DEFINATELY want to remove the unused IP addresses from the DC, so that it doesn’t register those IP addresses in DNS, and send clients to an address that doesn’t exist. On that note, i also don’t suggest DCs with multiple bound IPs – buy networking equipment to handle networking and routing, and let your servers and hosts do serving and hosting.

]]>