IP conflicts and BAD addresses on server 2003 DHCP scope

Does not look like it is re-starting. However, I had to manually delete some addresses to free up space in the scope. Could these machines  still be thinking that they still have a lease and this to be causing the conflict? Lease time used to be 8 days, and the scope would get filled up to 100%. I reduced the lease to 12 hrs. Can I expect the issue to disappear after a week or so?

It is possible that some devices are still using the older lease time. If that is the case they would be freed up in the 8 days.

Should I do anything about the BAD ADDRESSES? If I try to delete them they keep coming back.

I changed the default setting "Number of times the DHCP server should try conflict detection for an IP address before the server leases the address to a client"  from 0 to 3. Would that help?

I see now most BAD ADDRESSES (all but 2) heve the blue   i  icon. Does that mean they are inactive and the lease is expired? Or is it only expired according to the server and the client stuill thinks it has an active lease, because at the time it acquired it was set at 8 days?

I don't think anything you do at the server side will help in this case except maybe excluding those addresses temporarily till everything shakes out. Can you get the clients to try a renew from their side or is there too many?

Too many - 300 random users (students) go through  the building over a 24 hr period, with personal laptops, not domain machines. I will try excluding every bad address as it comes up and bring them back in a month or so. Thanks for the tip Rick!

question, not sure if this is relevant: there is an option in DHCP server to dymamically update DNS and PTR records, as opposed to wait for a request from client, which is the default option. Would that have any bearing at all?

Thanks!