Discussion Locked

WinNT DHCP server

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi all,

We have 2 remote sites. Site A is connected to Site B via leased T1 line. Site A provides DHCP services to Site B over the WAN. Site A also provides Internet and Email services.

In a month, we will sever the link to Site A (companies are splitting into 2 entities). We want to install DHCP services on Site B. However, we would like this to be a smooth transition. We cannot do a hard cutover because there will be an interim period where clients still require access to some services at Site A. My question is, how do we do this so that we can bring up our DHCP server ahead of time? My plan was to copy the DHCP scope from Site A's server and put it on Site B's new server. I would then create the existing active leases as "active reservations" to avoid any conflicts. As the active leases timed out, the clients would pick up a new IP from the new DHCP server.

Does anyone see any flaws in my logic? Any suggestions would appreciated.

TIA,

2 replies

by ghstinshll

Immediately, reduce the range of available IPs on your current DHCP server to reflect the # of clients you need at that site. Then set up your DHCP at the new DHCP site with the range that you removed from the original site.

If you currently have enough IPs to service all your cleints, then this shuold go smoothly for you.

by ghstinshll

And I'm sure you'll want to have the new DHC site pay for the IP addresses that the other branch just gave them, so there'll need to be some kind of cross-billing for those...

This discussion is closed to new replies.