|
|||||||
 |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
08-22-2000, 04:37 PM
|
#1 |
|
Member (10 bit)
Join Date: Jun 1999
Location: Denver, Colorado / USA
Posts: 545
|
Hello all,
An upcoming project requires to rebuild the IP settings of a single domain. The company is currently using real life IP addresses and everything shall be transfered into 'dummy' IP addresses (192.168.xxx.xxx). Now I am looking for the easiest and best way to do it. My plan is as follows: Configuring a second DHCP server with the new scope - delivering the new IP addresses to the clients. At the end of the day shutting down all clients and disabling the original DHCP server and activating the new one that will offer the new IP addresses. Then changing the static IP addresses. As the last step booting all clients. If I am right the clients will be out looking for a DHCP server, they do not find the original one therefore they cannot continue their leases. They will get a response from the new DHCP server and that will submit new IP addresses to my domain. The domain name will not change. I just need to push out new (dummy) IP addresses and a new default gateway. The DNS servers are on a different network anyway. Would this be the best way or does anyone of you knows a better way to do it?! Let me know!! Thanks in advance!! |
|
|
|
08-22-2000, 05:55 PM
|
#2 |
|
Member (5 bit)
Join Date: Apr 1999
Posts: 18
|
I just went through a similar and very painful transition of 4 servers and 350 workstations. 30 servers and 30 printers to go... These things go smoothly in theory. Only in theory. If you are using WINS, make sure you delete the whole database before converting. And make sure your DHCP lease is short enough that the clients will need to renew before the users come back in. Be careful of losing trusting/trusted domains. If you have none, great. Good luck.
|
|
|
|
|
08-23-2000, 04:09 AM
|
#3 |
|
Member (10 bit)
Join Date: Jun 1999
Location: Denver, Colorado / USA
Posts: 545
|
Thanks for the answer. I have WINS and was planning on cleaning that out. Good advice anyway. I do not have any trust relationships - so, I guess my biggest problem will be that the clients release the old IP address.
Again - Thanks!! |
|
|
|
|
08-23-2000, 08:34 AM
|
#4 |
|
Member (12 bit)
Premium Member
Join Date: Mar 1999
Location: LA, CA
Posts: 2,227
|
Add a private address to DHCP server.
Create a superscope with private range. Disable old range. Reboot clients No need for second server. |
|
|
|
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Linear Mode
