NT DHCP problem
|
Original Message
|
Name: Siv
Date: January 17, 2001 at 03:54:39 Pacific
Subject: NT DHCP problem
|
Comment: Hi I'm going to exchange an old NT server with a new one. The one will have all the same settings of the old including same name, ip, dhcp settings and so on... Now here is the problem: The old server has handed out some ip-addresses for it's clients (within the scope of this server). When I exchange this with the new server it doesn't know about which client has a given ip-address (because it it not contained in it's dhcp-database!!). I'm wondering - if I shut down my old server (and the new one is also shut down) - then copy the file c:\winnt\system32\dhcp\dhcp.mdb from the old server to the new server and then startup the new server (additionally change the name and ip-address and so on...) - would this work?? I have a small program which allows me to copy the dhcp.mdb while in "dos" mode - I'm just wondering if there is more to it? Can anyone assist me? Kind regards Siv
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: Tony
Date: January 17, 2001 at 07:35:48 Pacific
|
Reply: (edit)Why not make the new server a BDC
then promote it. Also remember DCHP uses broadcast, so when the leases run out the client will take a new addresses from whomever answers first.
 Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: ned
Date: January 17, 2001 at 08:54:44 Pacific
|
Reply: (edit)Siv,
That's supposed to work.
If the new server is the same name and ip as the old, I don't think there will be a problem unless you are using reservations in DHCP, in that case your idea will take care of that (reservations). Otherewise, if it's all setup the same, the clients ought to renew ok and it'll just remake the dhcp db. Any problems with a client machine try rebooting it (client).
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: hasa
Date: January 17, 2001 at 23:43:42 Pacific
|
Reply: (edit)well...config the DHCP IN the the new server to sign addresses every hour .stop the OLD server DHCP service [just in case you foregot :))]and shut the old server down-fore sure.shut down all the station -wait the hour...take asmoke.reboot all station -that works for me in dhcp problem.
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: Siv
Date: January 19, 2001 at 02:22:05 Pacific
|
Reply: (edit)Hi again I don't use reservations only dynamic IP-addresses... I don't see how first making it a BDC and then promoting it solves the problem I describe (I was going to install as BDC first anyway!!)... The problem is as I see it that the new server doesn't know of the IP-addresses the old server has handed out... Take this example: If a client has an IP-address which it has leased from server A. When this address expires it will try to contact server A for a new one. When this server is shut down in the mean time it will of cause contact another DHCP-server to get a new IP-address and if this server doesn't handle this request correctly (because it might try to give the client the same address again - which now might be some other clients address!!!) - then you have a problem. That's why I was wondering if I made a hardcopy of the DHCP.mdb file at the moment I made the switch between the servers - I thought I might get around any potential problems... I actuallt have had one problem with this as I have just exchanged a BDC as well and this resulted in (up til now!!!) an addressconflict between two clients!!! Kind regards Siv
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
