CHANGER L'IP d'un controleur de domaine Windows 2003
1 réponse
news microsoft
Bonjour, je vais devoir changer l'ip de mes serveurs qui sont controleurs de
domaine, serveur dns, etc.. je suis sous windows 2003 server SP1 sur l'un,
et windows 2003 server R2 sur le second, quelle est la manière de procéder?
1. Check to make sure A + PTR record exist in DNS for current IP for DC 2. Check to see if current IP address of server exists in delegated zone in root DC in DNS. If so will need to update with new IP 3. Run REPLMON to check for replication errors 4. If server is WINS server remove replication partner from gp2kic08 (hub WINS server) and vice versa 5. Remove WINS from server 6. Check to make sure no other DC is pointing to its IP address for DNS and or WINS resolution 7. If server is also DHCP Network folks will need to update router and switches to reflect new IP address 8. If server is also DHCP server authorize server with new IP address 9. If server is also DHCP server Network folks will need to change global scope options for new IP for DNS/WINS 10. Change IP address on server to new IP (Note: You lose connectivity when you do this remotely) Need alternative 11. Check to see what IP address server is using for Primary DNS. Should be pointing to 10.49.32.138 12. Change secondary DNS to point to its new IP address 13. Execute IPCONFIG /FLUSHDNS 14. Execute IPCONFIG /REGISTERDNS 15. Stop and restart the Netlogon service 16. In DNS check to make sure A and PTR records updated with new IP address 17. In DNS make sure (same as Parent folder) updated with new IP address 18. "In DNS on properties page check to see that ""Listen on IP address"" reflected new IP" 19. Check local replication between DC's in that region where the IP address was changed 20. Install WINS on DC 21. In WINS under general tab make sure default back path has been created (c:winntsystem32wins) 22. Setup replication between itself and gp2kic08 (hub WINS server) and vice versa 23. Backup WINS database 24. Bring up DHCP console. Wont connect due to trying to use old IP 25. Delete old IP address from list out of DHCP Manager 26. Add server back to list with new IP address 27. In bindings section in DHCP check to make sure server is pointing to new IP 28. Execute IPCONFIG /RELEASE and /RENEW on token ring and ethernet clients to make sure picking up address with new IP 29. Check to make sure Network has updated global and scope options reflecting new IP
Cordialement, Olivier
"news microsoft" <rze> wrote in message news:
Bonjour, je vais devoir changer l'ip de mes serveurs qui sont controleurs de domaine, serveur dns, etc.. je suis sous windows 2003 server SP1 sur l'un, et windows 2003 server R2 sur le second, quelle est la manière de procéder?
merci d'avance
LIONEL
Bonjour,
Voici un article Microsoft concernat le changement d'IP d'un serveur DC.
1. Check to make sure A + PTR record exist in DNS for current IP for DC
2. Check to see if current IP address of server exists in delegated zone in
root DC
in DNS. If so will need to update with new IP
3. Run REPLMON to check for replication errors
4. If server is WINS server remove replication partner from gp2kic08 (hub
WINS
server) and vice versa
5. Remove WINS from server
6. Check to make sure no other DC is pointing to its IP address for DNS and
or WINS
resolution
7. If server is also DHCP Network folks will need to update router and
switches to
reflect new IP address
8. If server is also DHCP server authorize server with new IP address
9. If server is also DHCP server Network folks will need to change global
scope
options for new IP for DNS/WINS
10. Change IP address on server to new IP (Note: You lose connectivity when
you do
this remotely) Need alternative
11. Check to see what IP address server is using for Primary DNS. Should be
pointing to 10.49.32.138
12. Change secondary DNS to point to its new IP address
13. Execute IPCONFIG /FLUSHDNS
14. Execute IPCONFIG /REGISTERDNS
15. Stop and restart the Netlogon service
16. In DNS check to make sure A and PTR records updated with new IP address
17. In DNS make sure (same as Parent folder) updated with new IP address
18. "In DNS on properties page check to see that ""Listen on IP address""
reflected
new IP"
19. Check local replication between DC's in that region where the IP address
was
changed
20. Install WINS on DC
21. In WINS under general tab make sure default back path has been created
(c:winntsystem32wins)
22. Setup replication between itself and gp2kic08 (hub WINS server) and vice
versa
23. Backup WINS database
24. Bring up DHCP console. Wont connect due to trying to use old IP
25. Delete old IP address from list out of DHCP Manager
26. Add server back to list with new IP address
27. In bindings section in DHCP check to make sure server is pointing to new
IP
28. Execute IPCONFIG /RELEASE and /RENEW on token ring and ethernet clients
to make
sure picking up address with new IP
29. Check to make sure Network has updated global and scope options
reflecting new IP
Cordialement,
Olivier
"news microsoft" <rze> wrote in message
news:uUEb7jy0GHA.4796@TK2MSFTNGP06.phx.gbl...
Bonjour, je vais devoir changer l'ip de mes serveurs qui sont controleurs
de domaine, serveur dns, etc.. je suis sous windows 2003 server SP1 sur
l'un, et windows 2003 server R2 sur le second, quelle est la manière de
procéder?
1. Check to make sure A + PTR record exist in DNS for current IP for DC 2. Check to see if current IP address of server exists in delegated zone in root DC in DNS. If so will need to update with new IP 3. Run REPLMON to check for replication errors 4. If server is WINS server remove replication partner from gp2kic08 (hub WINS server) and vice versa 5. Remove WINS from server 6. Check to make sure no other DC is pointing to its IP address for DNS and or WINS resolution 7. If server is also DHCP Network folks will need to update router and switches to reflect new IP address 8. If server is also DHCP server authorize server with new IP address 9. If server is also DHCP server Network folks will need to change global scope options for new IP for DNS/WINS 10. Change IP address on server to new IP (Note: You lose connectivity when you do this remotely) Need alternative 11. Check to see what IP address server is using for Primary DNS. Should be pointing to 10.49.32.138 12. Change secondary DNS to point to its new IP address 13. Execute IPCONFIG /FLUSHDNS 14. Execute IPCONFIG /REGISTERDNS 15. Stop and restart the Netlogon service 16. In DNS check to make sure A and PTR records updated with new IP address 17. In DNS make sure (same as Parent folder) updated with new IP address 18. "In DNS on properties page check to see that ""Listen on IP address"" reflected new IP" 19. Check local replication between DC's in that region where the IP address was changed 20. Install WINS on DC 21. In WINS under general tab make sure default back path has been created (c:winntsystem32wins) 22. Setup replication between itself and gp2kic08 (hub WINS server) and vice versa 23. Backup WINS database 24. Bring up DHCP console. Wont connect due to trying to use old IP 25. Delete old IP address from list out of DHCP Manager 26. Add server back to list with new IP address 27. In bindings section in DHCP check to make sure server is pointing to new IP 28. Execute IPCONFIG /RELEASE and /RENEW on token ring and ethernet clients to make sure picking up address with new IP 29. Check to make sure Network has updated global and scope options reflecting new IP
Cordialement, Olivier
"news microsoft" <rze> wrote in message news:
Bonjour, je vais devoir changer l'ip de mes serveurs qui sont controleurs de domaine, serveur dns, etc.. je suis sous windows 2003 server SP1 sur l'un, et windows 2003 server R2 sur le second, quelle est la manière de procéder?
