Discussion on:

MS DHCP Bad_address release

At a site we are having issues with the current DHCP server running on a 'special' machine.
Because there is noting more to do for this machine except DHCP we want to replace this with a DHCP server running on a Win2003 server.

In the network there are aprox. 450 clients running DHCP.
I only want to change the DHCP relay in the network so i'll have to re-use the current scopes.
To prevent duplicate IP's i'll enable Conflict address detection on the MS DHCP.

If a client will ask for a new address it will check if the address is used, that will probably be the case so it will be marked as a bad_address. And it will take a bit of time before a good addres is found.

Now my question: what will happen if a client wants to renew it's address and this address already has been marked as a bad_address?

Will the server give the client the address it had before and make a 'valid'address of the bad address or will it issue a 'new' address out of the scope of addresses not marked as a bad_address?

If the address stays marked as a bad_address untill it's removed or the lease time has expired i'll run out of addresses in no time..

Does anyone know if the server can re-issue a bad_address within the lease time. Or does anyone have another idea?

It works pretty much the same regardless of what is the DHCP server.

A client always asks for the address to which it was previously assigned. If it isn't available, it gets an unused address from the pool.