dhcp release question 1

[bcardona]

is there a way to force client pc's to relase dhcp without having to goto every pc and do a release/renew.

 

[jfp23]

depends on the size of your network, in a smaller network you could power down your switches on XP that would cause the pc's to go back to the default IP, and than when you turned the switches back on they would go to the DHCP server to get an address.

 

[Davetoo]

What are you trying to accomplish? Perhaps if we knew that we could provide a game plan to help.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
The poster formerly known as lander215

 

[bcardona]

we have an old nt box that we wanted to replace for some time now, it currently runs our wins and dhcp, when we replace it with a 2003 box that will run our dhcp/wins from the network our concern was that the nt and yes 98 pc's would have to manually be renewed, i was wondering if we could force the pc's to release/renew instead of manually running around to do it.

 

[jfp23]

forcing a release/renew on 98 is doubtful, but you may be able to force a reboot.

 

[Davetoo]

If you have enough available IP's, the simplest way would be to reduce the scope on the NT box, then bring up the new DHCP server with the remaining available IP's then disable DHCP on the NT box. The systems will then get their IP's from the new box when it's time for them to renew.

You have set a relatively short expiration for leases haven't you? I've always used 3 days.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
The poster formerly known as lander215

 

[WhoKilledKenny]

Davetoo is correct. Just replace the DHCP server. Win2k and Win2K3 will not give out addresses that are already used by the clients, so you won't get any IP conflicts. What you will see in your address leases are BAD_ADDRESS, which indicates the new DHCP server recoginized that the address it was going to lease out is in use. You can manually clear these entries, eventually they will go away when all your clients have renewed with the new server.

 

[bcardona]

thanks guys, i was thinking that i would wait till it was time to renew, but thats a great idea of shrinking the scope. yes 3 days also.

 

[ADB100]

You could enable the 'Conflict Detection' feature on the new Windows 2003 DHCP Server, shut the old one down and just bring the new one into service with the same DHCP scopes. This way the new DHCP server attempts to ping an IP address 'x' number of times before issueing a lease.

HTH

Andy

 

[bcardona]

ADB100,

if is shutdown the nt box lets call it dhcp1, and bring the new 2003 box say dhcp2, the nt and 98 pc's would look to renew with the nt box and we would have to force a manual release/renew is that correct or would they just broadcast to any new dhcp server and pick up the new one?