Discussion Locked

Unable to release TCP/IP stack

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

6 replies

by doubledown

that address won't get released. its a special address that is automatically assigned (so that someone who knows nothing about networking can still network computers together)
i too, was previously baffled by this obscure address. all you need todo is obtain (renew) a dhcp address and you're fine. releasing it isn't necessary (and won't work anyway. it just stays there.)

by tony.colgrove

The 169.254.x.x is an APIPA (Automatic Private IP Address). Win98/SE/ME and Win2K use these addresses (the x.x are randomly generated) if they cannot contact a DHCP server (if the NIC is configured for DHCP). Answer 1 is correct that you cannot release this address, it is there because the DHCP requests it is generating are not being answered. You may want to try configureing the NIC with a static address, and see if you can ping the 192.168.0.1 address. If you cant it might be a wiring problem, or a bad NIC or NIC driver. Do you see the cable disconnected icon in the system tray?
I had a similar problem with a home built machine. The NIC just wouldn't work right, unless I used it in a specific PCI slot. You might want to make surethe NIC does not have any resource conflicts in the Device Manager, or even try a different NIC.

by 2ndchancepc

I had a ICS setup disk laying around and used it on the client pc in question nothing happen, then I did the wizard thing and still nothing happen, so I threw my hands up and said I quit. About a 1/2hr later I noticed my BlackIce was alerting me so out of curiousity I looked at it and lo and behold it was 192.168.0.2, I then marked the ip as trusted and ran to the pc hit IE and there in all its splender was the homepage, sniffle, sniffle! I immediately set out to thank the cyber gods and sacrificed a memory chip in their honor. Seriuosly I don't know if was coincidence(maybe the DHCP lease was up) or between the ICS setup disk and the internet connection wizard it was triggered to end the old lease. Needless to say I'm back in business. WAHOO! :)

This discussion is closed to new replies.