IP Address Not release after expiration
This is a discussion about IP Address Not release after expiration in the Windows Networking category; We have a DHCP server, but recently we find it doesn't release the IP address leased after expiration
We have a DHCP server, but recently we find it doesn't release the IP address leased after expiration
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Oct 28
Oct 29
0
2 minutes
Responses to this topic
1. Event log errors? warnings?
2. Are leases returned when the client is forced to remove its lease .... ipconfig /releaseall
3.
Quote:We have a DHCP server so that is what OS and servicepack level?
2. Are leases returned when the client is forced to remove its lease .... ipconfig /releaseall
3.
Quote:We have a DHCP server so that is what OS and servicepack level?
is the pc that has the ip still in the network? I may be wrong but I believe
when the lease runs up and the pc is still in the network it will first request the ip that it already has and when it is available it gets the same ip address again. If, for example, the pc was shutdown, and is then booted it will only get a new address if the "old" ip is already given to another pc...then again...this could all be a load of crap : )
when the lease runs up and the pc is still in the network it will first request the ip that it already has and when it is available it gets the same ip address again. If, for example, the pc was shutdown, and is then booted it will only get a new address if the "old" ip is already given to another pc...then again...this could all be a load of crap : )
THis may be caused by having the exact amount of IP addresses as your computers
So for instance you have IPs of 192.168.0.1 - 192.168.0.10
and you have ten machines then when an IP is released by a machine, and its IP goes back into the pool, it asks for another which happens to be the same one it released, thus getting back the same IP
If the lease times are set for example a 24 hour period each machine is probably on a different schedule, so no 2 machines release at the same time.
So for instance you have IPs of 192.168.0.1 - 192.168.0.10
and you have ten machines then when an IP is released by a machine, and its IP goes back into the pool, it asks for another which happens to be the same one it released, thus getting back the same IP
If the lease times are set for example a 24 hour period each machine is probably on a different schedule, so no 2 machines release at the same time.
We had a similar problem on a NT4 server, more IPs than machines. But the damn DHCP server would not release the IPs. Sometimes we were having problems because new machines could not get an IP. All the IPs were in use, well not really. We needed to release them manually in the DHCP manager. We never found why, and then upgraded to 2000....
http://www.jsiinc.com/SUBG/TIP3300/rh3312.htm
As an after thought. We can't do much more without you supplying your configs. 8)
As an after thought. We can't do much more without you supplying your configs. 8)
