BBrayton
asked on
How to change your Domain controllers static IP
We are going to be moving a server to a new Location and the IP address on the server needs to change.
What would be the steps to take on the server when you have to change it to another IP address.
I found these steps online. Can you let me know it this is accurate?
[b]To perform this procedure, you must be a member of the Domain Admins group in the domain of the domain controller whose IP address you are changing.
To change the static IP address of a domain controller
Log on locally (also known as interactively) to the system console of the domain controller whose IP address you want to change. If you are not able to log on to the domain controller by using the domain, you may have to start the domain controller in Directory Services Restore Mode (DSRM). For more information, see Restart the domain controller in Directory Services Restore Mode locally (https://lazyadminblog.wordpress.com/2015/04/11/restart-the-domain-controller-in-directory-services-restore-mode-locally/).
On the desktop, right-click My Network Places, and then click Properties.
In theNetwork Connections dialog box, right-click Local Area Connection, and then click Properties.
In theLocal Area Connection Properties dialog box, double-click Internet Protocol (TCP/IP).
In theInternet Protocol (TCP/IP) Properties dialog box, in the IP address box, type the new address.
In theSubnet mask box, type the subnet mask.
In theDefault gateway box, type the default gateway.
In thePreferred DNS server box, type the address of the DNS server that this computer contacts.
In theAlternate DNS server box, type the address of the DNS server that this computer contacts if the preferred server is unavailable.
If this domain controller uses WINS servers, clickAdvanced and then, in the Advanced TCP/IP Settings dialog box, click the WINS
If an address in the list is no longer appropriate, click the address, and then clickEdit.
In theTCP/IP WINS Server dialog box, type the new address, and then click OK.
Repeat steps 11 and 12 for all addresses that need to be changed, and then clickOK twice to close the TCP/IP WINS Server dialog box and the Advanced TCP/IP Settings dialog box.
ClickOK to close the Internet Protocol (TCP/IP) Properties dialog box.
After you change the IP address of a domain controller, you should run the ipconfig /registerdns command to register the host record and dcdiag /fix command to ensure that service records are appropriately registered with DNS. For more information, see Dcdiag Overview and subordinate topics for additional information about the Dcdiag tool (https://lazyadminblog.wordpress.com/2015/04/11/dcdiag-overview/).
Changing the IP settings of a server does not affect the share resources or shared permissions on that server, if the name resolution structure DNS and WINS settings are correctly configured. However, if network drives or passive connections (connections that are made manually from a command prompt or run line) are mapped using the IP address, an update is required. For example, if a client computer has G: drive mapped using the following command net use g: \\192.168.0.199\data and the IP address of the server that hosts the Data shared folder is changed from 192.168.0.199 to 192.168.1.200, the new G: drive mapping command should be changed to net use g: \\192.168.1.200\data. A better solution would be to ensure that DNS name resolution is working properly and to use the server name, as opposed to the IP address, in the command. For example, if the server name is DC1, the command to map a G: drive to the Data share on the server is net use g: \\dc1\data. It changes only if the server name changes; it is not affected if the IP address of the server changes.
What would be the steps to take on the server when you have to change it to another IP address.
I found these steps online. Can you let me know it this is accurate?
[b]To perform this procedure, you must be a member of the Domain Admins group in the domain of the domain controller whose IP address you are changing.
To change the static IP address of a domain controller
Log on locally (also known as interactively) to the system console of the domain controller whose IP address you want to change. If you are not able to log on to the domain controller by using the domain, you may have to start the domain controller in Directory Services Restore Mode (DSRM). For more information, see Restart the domain controller in Directory Services Restore Mode locally (https://lazyadminblog.wordpress.com/2015/04/11/restart-the-domain-controller-in-directory-services-restore-mode-locally/).
On the desktop, right-click My Network Places, and then click Properties.
In theNetwork Connections dialog box, right-click Local Area Connection, and then click Properties.
In theLocal Area Connection Properties dialog box, double-click Internet Protocol (TCP/IP).
In theInternet Protocol (TCP/IP) Properties dialog box, in the IP address box, type the new address.
In theSubnet mask box, type the subnet mask.
In theDefault gateway box, type the default gateway.
In thePreferred DNS server box, type the address of the DNS server that this computer contacts.
In theAlternate DNS server box, type the address of the DNS server that this computer contacts if the preferred server is unavailable.
If this domain controller uses WINS servers, clickAdvanced and then, in the Advanced TCP/IP Settings dialog box, click the WINS
If an address in the list is no longer appropriate, click the address, and then clickEdit.
In theTCP/IP WINS Server dialog box, type the new address, and then click OK.
Repeat steps 11 and 12 for all addresses that need to be changed, and then clickOK twice to close the TCP/IP WINS Server dialog box and the Advanced TCP/IP Settings dialog box.
ClickOK to close the Internet Protocol (TCP/IP) Properties dialog box.
After you change the IP address of a domain controller, you should run the ipconfig /registerdns command to register the host record and dcdiag /fix command to ensure that service records are appropriately registered with DNS. For more information, see Dcdiag Overview and subordinate topics for additional information about the Dcdiag tool (https://lazyadminblog.wordpress.com/2015/04/11/dcdiag-overview/).
Changing the IP settings of a server does not affect the share resources or shared permissions on that server, if the name resolution structure DNS and WINS settings are correctly configured. However, if network drives or passive connections (connections that are made manually from a command prompt or run line) are mapped using the IP address, an update is required. For example, if a client computer has G: drive mapped using the following command net use g: \\192.168.0.199\data and the IP address of the server that hosts the Data shared folder is changed from 192.168.0.199 to 192.168.1.200, the new G: drive mapping command should be changed to net use g: \\192.168.1.200\data. A better solution would be to ensure that DNS name resolution is working properly and to use the server name, as opposed to the IP address, in the command. For example, if the server name is DC1, the command to map a G: drive to the Data share on the server is net use g: \\dc1\data. It changes only if the server name changes; it is not affected if the IP address of the server changes.
Hello
You should also review AD Sites and Services.
If its a new sub net, The new subnet should be added in AD sites and services.
The subnet can be mapped to an existing AD site or can be added to a new AD site - according to your plan.
Cheers !
Shaba
To be clear, you are talking about the LAN IP address, not the WAN IP address... correct? If it is just the WAN IP address, much simpler.
Assuming that you're changing LAN IP here:
If anyone address the server by IP address (as a share, for example), you'll have to change those IP addresses (better to use server name instead, though).
If any devices have static IPs (printers, switches, WAPs, cameras, computers, etc.), they'll have to change, too. I try to avoid local static IPs and assign them with reservations in DHCP instead (I call that "quasi-static").
This is a good opportunity to assess how you assign LAN IP address to make them more manageable in the future.
Assuming that you're changing LAN IP here:
If anyone address the server by IP address (as a share, for example), you'll have to change those IP addresses (better to use server name instead, though).
If any devices have static IPs (printers, switches, WAPs, cameras, computers, etc.), they'll have to change, too. I try to avoid local static IPs and assign them with reservations in DHCP instead (I call that "quasi-static").
This is a good opportunity to assess how you assign LAN IP address to make them more manageable in the future.
ASKER
I found these instructions online and it worked perfectly
Change the IP address
In this example, I’m going to change the IP address of a Windows Server 2012 DC. The server is additionally configured as the domain’s only DNS server.
Open a command prompt by right-clicking the PowerShell icon on the desktop Task Bar and select Run as Administrator.
Run DCDIAG and make sure the DC passes all the tests. If any problems are identified, they should be resolved before proceeding any further.
Right-click the network icon in the bottom right of the Task Bar and select Open Network and Sharing Center from the menu.
In the Network and Sharing Center, click Change adapter settings.
On the Network Connections screen, right-click the network adapter for which you want to change the IP address and select Properties from the menu.
In the Ethernet Properties dialog box, scroll down the list and double-click Internet Protocol Version 4 (TCP/IPv4).
In the TCP/IPv4 dialog box, change the IP address (and subnet mask if required). In this example I will also change the primary DNS server entry to the DC’s new static IP address, as the DC is also the only DNS server in the domain. Click OK to continue.
Click OK in the Ethernet Properties dialog box and then close the Network and Sharing Center.
Register the domain controller’s new IP address
Now the IP address has been changed, we need to empty the local DNS cache and register the DC’s new IP address in DNS.
In the PowerShell box, run ipconfig /flushdns to remove any cached DNS entries created by the local DNS resolver.
Run ipconfig /registerdns to ensure the new IP address is registered by the DNS server.
Run dcdiag /fix to update Service Principal Name (SPN) records and check that all the tests are passed successfully.
Change DC IP address
DHCP settings will need to be changed if the DC is also a DNS server to make sure domain members pick up the DNS server’s new IP address. Don’t forget that you’ll either need to clear the local DNS cache on all member servers and clients joined to the domain or reboot them so that they resolve the new IP address to locate the DC.
If you have a distributed DNS infrastructure, you may need to wait for DNS information to replicate or force a replication. If present, subnet information in AD Sites and Services should be updated if the subnet addressing scheme is also modified. As with any major change you make to your production servers, you should test the procedure in a preproduction environment using servers with the same configuration as your production systems.
Change the IP address
In this example, I’m going to change the IP address of a Windows Server 2012 DC. The server is additionally configured as the domain’s only DNS server.
Open a command prompt by right-clicking the PowerShell icon on the desktop Task Bar and select Run as Administrator.
Run DCDIAG and make sure the DC passes all the tests. If any problems are identified, they should be resolved before proceeding any further.
Right-click the network icon in the bottom right of the Task Bar and select Open Network and Sharing Center from the menu.
In the Network and Sharing Center, click Change adapter settings.
On the Network Connections screen, right-click the network adapter for which you want to change the IP address and select Properties from the menu.
In the Ethernet Properties dialog box, scroll down the list and double-click Internet Protocol Version 4 (TCP/IPv4).
In the TCP/IPv4 dialog box, change the IP address (and subnet mask if required). In this example I will also change the primary DNS server entry to the DC’s new static IP address, as the DC is also the only DNS server in the domain. Click OK to continue.
Click OK in the Ethernet Properties dialog box and then close the Network and Sharing Center.
Register the domain controller’s new IP address
Now the IP address has been changed, we need to empty the local DNS cache and register the DC’s new IP address in DNS.
In the PowerShell box, run ipconfig /flushdns to remove any cached DNS entries created by the local DNS resolver.
Run ipconfig /registerdns to ensure the new IP address is registered by the DNS server.
Run dcdiag /fix to update Service Principal Name (SPN) records and check that all the tests are passed successfully.
Change DC IP address
DHCP settings will need to be changed if the DC is also a DNS server to make sure domain members pick up the DNS server’s new IP address. Don’t forget that you’ll either need to clear the local DNS cache on all member servers and clients joined to the domain or reboot them so that they resolve the new IP address to locate the DC.
If you have a distributed DNS infrastructure, you may need to wait for DNS information to replicate or force a replication. If present, subnet information in AD Sites and Services should be updated if the subnet addressing scheme is also modified. As with any major change you make to your production servers, you should test the procedure in a preproduction environment using servers with the same configuration as your production systems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's very accurate. Simpler: Start > Run > ncpa.cpl
Also, WINS is probably not used anyway. You can skip these steps.
If you have other DC's, do this steps at the same time, to save you troubleshooting later on (Press the last OK screen at the same time).