Windows 2003 AD Server with DHCP. We connect windows 7 Professional Machines to the network and DHCP fills up with Bad Addresses. So far 3 different windows 7 Professional PC's have done this. All are Brand new HP Desktops. We have 2 Windows 7 Ultimate on new HP Desktops with no problems as well as some laptops with windows 7 pro without any incident. So far we have tried a secondary Nic in the machines, same result a few days later. We have reformatted the machines, same result a few days later.

Usually BAD ADDRESS temporary leases are created by the DHCP server when an IP conflict is detected. Are you sure that those addresses are not in use. Can you verify by using the PING Tool to see if there are any ICMP responses? Using Conflict Detection in DHCP http://www.anitkb.com/2010/03/using-conflict-detection-in-dhcp.html If that checks out OK, have you also verified that the Windows systems encountering the problem all have the correct NIC drivers installed? Visit: anITKB.com, an IT Knowledge Base.

Hi, The error can be seen on the DHCP server side. This may means the IP Address is not leased successfully. You may check if there is any error encountered in Event Log on the server side. Also, in order to clarify the issue more clearerly, I would like to ask the following questions: 1. Are there any devices on the network that have static IP addresses that have not been excluded from the DHCP scope? 2. Check the DHCP server MMC to see if there is a shortage of IP address lease availability. 3. Are there roaming DHCP clients or laptops on the network that are using standard length IP address leases? 4. Are you using multiple DHCP servers to provide IP address fault tolerance? regards, Sabrina TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Yes im sure they are not in use. even the mac addresses look wierd. we are looking into the use of other drivers also

Yes im sure they are not in use. even the mac addresses look wierd. we are looking into the use of other drivers also We added a new external nic also and still had the issue

I will Check the even log the next time that happens . i believe i did last time but will verify again 1) No, we do static ips outside the range or reservations. 2) normally we have over 330 ip addresses available, 3) we have a few Roaming laptops but they get the standard setting per site they log into. This problem only happens at my site location where we are in the process of setting up the systems for the end users. 4) only 1 DHCP Server per site and there is no cross site vailidation happening. We have firewall rules per site that prevent cross validation of IP's.

330 IP avilable, Its means you have more than 1 seagment. And always happen in one place. I think maybe the route or switch you connected have a wrong setting.

we are using 172.16.0.0 /21 each site uses eg . 172.16.8.*-172.16.15.* 255.255.248.0. Ip ranges vary 172.16.8.20-254 & 172.16.9.100-200 Routers are fine. Its only when we connect some windows 7 machines on our network. not all windows 7 machines, I have 2 that i use which has no issues at all 1 Ult 64bit and 1 Pro 32 bit. I know of at least 1 other that has no issues. the hardware varies on all 3 machines that have no issues.

I set the conflict detection. will see how that works in the next few days

Hi, Thank you for your update. If there is any result, please let us know. If you would like further assistance, please do not hesitate to let me know. It is my pleasure to help. :) Regards, Sabrina TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Usually BAD ADDRESS temporary leases are created by the DHCP server when an IP conflict is detected. Are you sure that those addresses are not in use. Can you verify by using the PING Tool to see if there are any ICMP responses? Using Conflict Detection in DHCP http://www.anitkb.com/2010/03/using-conflict-detection-in-dhcp.html If that checks out OK, have you also verified that the Windows systems encountering the problem all have the correct NIC drivers installed? Visit: anITKB.com, an IT Knowledge Base. This seems to have worked. Since i activated this we no longer get the bad addresses on our DHCP server

Conflict Detection should always be used, in my opinion. Glad to hear you resolved your issue.Visit: anITKB.com, an IT Knowledge Base.

I'm seeing this same issue with a 2003 file server that has conflict detection enabled for DHCP. This only occurs for a Win7 Domain laptop that is a roaming user that connects to the network. The Laptop shows an IP Conflict error and repeatedly trys to pull a DHCP address, in the event logs you can see it sequentially grabbing for IP addresses. We have a large scope but needless to say this is eating up addresses fast. I'm concerned as we are deploying more Win7 images to field users soon. Drivers were updated on the machine, NIC disabled and re-enabled. If we were to assign it a static in our printer IP range that would work for just this site, the problem is the user needs to travel and pull DHCP where ever they are at. Any thoughts and ideas would be appreciated. Thanks! FYI: This only seems to be occurring at one of our Hospitals in that region so it may be a simple server side setting that could be adjusted. Given some more time I'm sure we will encounter this again as we are just starting to deploy Win7 Laptops and Desktops but I hope to head this issue off before it becomes a real problem.

I'm seeing this same issue with a 2003 file server that has conflict detection enabled for DHCP. This only occurs for a Win7 Domain laptop that is a roaming user that connects to the network. The Laptop shows an IP Conflict error and repeatedly trys to pull a DHCP address, in the event logs you can see it sequentially grabbing for IP addresses. We have a large scope but needless to say this is eating up addresses fast. I'm concerned as we are deploying more Win7 images to field users soon. Drivers were updated on the machine, NIC disabled and re-enabled. If we were to assign it a static in our printer IP range that would work for just this site, the problem is the user needs to travel and pull DHCP where ever they are at. I am seeing it here as well, even after enabling Conflict Detection in the 2003 DHCP Server. I have it on 2 Lenovo Notebooks so far, both joined to my AD domain.