I keep getting an error with DHCP in XP, this is actually home edition. I am using a netgear rp614 router and when the computer tries to get an IP, it automatically says the IP cannot be renewed, I can see the IP flash up then go to 0's. The actual error in event viewer is.. "Your computer has detected that the IP address 192.168.0.6 for the Network Card with network address ... is already in use on the network. Your computer will automatically attempt to obtain a different address." However, when I look at the DHCP table of the router, this address is reserved for that computer. I am not sure why this happens, it has happened to me before and it took a couple of days, I guess when the lease ran out, then it could get a new IP. Also, I ran spybot and it said "running the necessary fix to you network adapter" I don't know if this had anything to do with it, but it has been giving me this error ever since I did that. Any help would be greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DHCP ERROR ALREADY IN USE
- Thread starter beetle10
- Start date
franklin97355
Technical User
Remove the reservation from the router and try again.
CTIEng2004
Technical User
Duplicate IP addresses from DHCP come from either more than one server offering up DHCP services or a DHCP address overlapping a static IP elsewhere in your LAN/WAN.
In both cases it boils down to ranges. You set the allowable ranges for your DHCP clients. Make sure if you have more than one distinct DHCP server that they are complimentary. But if you do have two, why no have a DHCP primary and backup instead?
I have seen the case where someone has a static IP that conflicts with a DHCP IP. Yes - you want to choke the sucker who configured it BUT the ranges of DHCP ought to be distinct enough so that no dunderhead would decide to plug one in for his/her convenience. If you have to locate the offending station, the finger utility was invented for such scenarios.
Finally I'll mention DHCP reservations. If the client cannot break the lease then go to the DHCP server and release the address. To make sure you come up cleanly unplug the Ethernet cable from your client. Then when the IP is freed, let it acquire a new lease. In your case, if more than one distinct DHCP server has the same range you should probab fix that first.
Good luck !
In both cases it boils down to ranges. You set the allowable ranges for your DHCP clients. Make sure if you have more than one distinct DHCP server that they are complimentary. But if you do have two, why no have a DHCP primary and backup instead?
I have seen the case where someone has a static IP that conflicts with a DHCP IP. Yes - you want to choke the sucker who configured it BUT the ranges of DHCP ought to be distinct enough so that no dunderhead would decide to plug one in for his/her convenience. If you have to locate the offending station, the finger utility was invented for such scenarios.
Finally I'll mention DHCP reservations. If the client cannot break the lease then go to the DHCP server and release the address. To make sure you come up cleanly unplug the Ethernet cable from your client. Then when the IP is freed, let it acquire a new lease. In your case, if more than one distinct DHCP server has the same range you should probab fix that first.
Good luck !
- Thread starter
- #5
Thanks guys, I think that the problem was someone has a router on my network that I don't know about and it is firing out IPs, I just changed the IPs to 192.168.10.* rather than 192.168.0.* so we will see if that works. The router has been locking up on me but I hope this will solve both of the problems, thanks again.
- Status
Similar threads
