Printable View
Does anyone have any idea what makes NIC's hold on to an IP address and not release it. We have an NT network using DHCP and we have had NIC's grab an IP address and not release it. Even cutting off the computer won't release it. It has happened with both Intel and 3Com cards. Any ideas?
I have seen the same problem if you should find an answer please let me know.
SJ
[email protected]
I actually did find out 2 things. Microsoft TechNet says there is a bug in DHCP that will cause it to give out the same IP twice. Contact MS for a fix because they dont give out the service pack to just anyone. That wasnt our problem however. Ours was the NIC holding on to the IP. If we set the NIC to a static IP and setup the DNS and Gateway, and got it working with the static IP, when we switched it back over to DHCP it would start working again. Hope this helps.
HOW ABOUT USING THE WNTIPCFG COMMAND TO RELEASE AND RENEW IP ADDRESS'S
CLICK START RUN TYPE IN THE OPEN BOX WNTIPCFG
TOMR
The problem you are having is due to the DHCP server holding the IP addresses until it's lease expires. A DHCP server will assign an IP address as each computer logs on. This address will stick in the DHCP server database until the lease is up. As far as the WNTIPCFG....I'll get back, I've never heard of this particular command. If I'm wrong about this command, please let me know.
J.
There is the IPCONFIG command which you can run from the dos command window.
"c:\>ipconfig /?" will display the command's usage parameters.
Among these are release and renew options.
[This message has been edited by houseisland (edited December 30, 1999).]