If you delete the database, Widnows wil start assigning addresses at the start of the pool (which may already be in use).Īs a result, teh addresss will get marked as bad. A client gets an address and keeps it till it expires (or is otherwise renewed). Lastly, if you delete the database as was suggested, you are only gong to create more problems. This way, neither device will overlap with the other.ģ. That is, if you have x.x.x.20 to x.x.x.100 as DHCP addresses, give the Windows server x.x.x.20 to x.x.x.50 and the network device as x.x.x.51 to x.x.x.100. If you want to have two systems offering DHCP, split teh available address pool between them. Eventually, Windows will end up marking all of the addresses that overlap with the router as bad and therefore not offer them up, even if they are free. If the router offers an address of x.x.x.1 for example, and the WIndows box DHCP range include x.x.x.1, then when Windows tests it, it will mark x.x.x.1 as bad.

In this message thread, two DHCP servers were being used at one point, one on the router, and the other on a Windows PC, and the scopes did not appear to exlcude the space of one another. In a normal course of business, it is a good practive to occasionally review any entries that show as BAD address and if they fail to repond to a ping, remove the entry from DHCP so that it can once agin be offered as needed.Ģ. Once DHCP tries an address and marks it bad, it will not try it again until the BAD_ADDRESS entry is removed. The BAD_ADDRESS entry is added by DHCP when it tries to offer an address, and does conflict detection to see the address is already in use. Wireshark 0.99.6a Download Now Released: Add info Size: 17.Looking over this tread, and I realize it is really old, but in case someone finds it looking for answers, let me correct the mistakes within it.ġ.

Wireshark windows 2008