Unable to release TCP/IP stack - TechRepublic
General discussion
October 15, 2000 at 11:51 PM
2ndchancepc

Unable to release TCP/IP stack

by 2ndchancepc . Updated 25 years, 8 months ago

I have good news and bad. I went here for some additional advice http://win2000mag-asap.com/info/com.winntmag_winntmag_7882_7882.html?se=ink. The ICS section got me thinking because it kept referring to the ip 192.168.0.1 as being the autoconfiguration address of my internal NIC, however if you look at my ipconfig it has 169.254.92.65, so I assigned sharing to my internal NIC to see what would and a message popped up saying that my local connection1 will now be configured with 192.168.0.1, so when I saw that natural I reapplied the sharing back to the #1 connection(external NIC) and it reset my internal NIC to 192.168.0.1, I was able to release my one of my client
pc’s ip reboot and now it connects to the net. Here’s the bad part for thelife of me I cannot do the same for my other client pc. I have created an account on the host, removed the NIC(through device manager), rebuilt the TCP/IP stack and it still holds on to this obsure ip 169.254.221.218, it won’t release it. Now I needhelp in this direction. I want to thank everyone and this forum for the guidance.

This discussion is locked

All Comments