1. The same complaint was noted for the other versions of Windows.
You can use any number of methods to have it forcefully release the IP info.
2. Some install firewalls that block pings. What happens next is that the DHCP server can't check to see that the IP is in use. Your complaint is typical and I wish you the best of luck educating that blocking pings is going to cause issues in some enviroments.
I'm the network assistant at a small college, and we've noticed a trend with Windows XP boxen. It seems that two strange behaviors are occuring with some frequency:
1. Many students report that their connection stops working. When they restart the computer, it retains expired DHCP information, rather than releasing it and getting a new lease. All that is required is to unplug the network cable so that Windows resets the device, and they work again, automagically.
2. Other students report the same thing. Upon investigation, their ports have been marked unusable in the DHCP tables. The reason this happens is that there is an IP conflict, and our theory is this: that Windows, failing to release the old IP, requests a new lease. The DHCP server pings the IP before it gives it out, but the ping comes back as active because Windows has failed to release the IP address. Hence, DHCP detects a conflict and marks the port unusable.
Has anyone else dealt with similar problems, and, if so, how did you solve it? I noticed that SP1 fixes a few DHCP issues, but this didn't seem to be among them. Any help, &c. Thanks.