Re: A little FYI

From: David (davidwnh_at_adelphia.net)
Date: 11/03/03


Date: Mon, 03 Nov 2003 11:41:03 GMT

It usually has nothing to do with a corrupt TCP/IP stack. When someone
uses DHCP assigned addresses and the initial DHCP registration times out
Windows will do what they call automatic address assignment, and this is
the range of addresses they use(169.254.0.0/16). So now-a-days the
problem is usually either misconfiguration of ones adapter settings,
router or AP DHCP server settings, or a misconfigured firewall which is
blocking the the DHCP registration traffic.

Duane Arnold wrote:
> I am making this post here, because time and time again as I goto various
> NG(s), I keep seeing people post on this issue of getting a 169.xxx IP
> and they cannot connect to the Internet. Some times getting the 169.xxx
> IP when doing IPCONFIG could be due to a bad DHCP device such as a bad
> router. But most of the time, it's due to the user dong something on the
> machine to courrpt the TCP/IP Stack on the machine. Many people don't
> seem to know how to come around it.
>
> The other part of this post is about installing the WPC11 on a XP
> machine, which is HELL, but a piece of cake on an Win 2k machine.
>
> The post is mostly about how to correct the TCP/IP Stack and the 169.xxx
> IP.
>
> <snip>
>
> My machine use to be Win2k pro with Linksys WPC11 v3 network card and I
> upgraded it to XP pro. And that's when all HELL broke loose. It started
> with the 169.xxx IP number being assigned to the wired and wireless NIC's
> -- to the DAMN utility program for the wireless is not worth 2 cents.
>
> I got the WPC11 running on XP pro and there are somethings I would like
> to share on how you get the DAMN thing to work, if anyone is interested.
> One thing I'll tell you is forget the WPC11 Utility to setup the card.
> One must go to the Device Manager off of Control Panel to install the
> driver and configure the card.
>
> For that 169.xxx IP, it means that the TCP/IP stack is hosed and for Win
> 9'x to Win 2k to rebuild the stack , one deletes Winsock and Winsock2
> entries out of the registry, delete everything out the NIC's Property Box
> and reboot the machine, which will rebuild the stack. Then one installs
> everything back in the NIC's property box.
>
> For an XP machine, you don't touch the Winsock and Winsock2 registry
> entries. You can go to the NIC's Property Box and uninstall everything,
> but you cannot uninstall TCP/IP. You should not reboot the machine on
> each uninstall.
>
> You must follow what's in the link below to reset TCP/IP on an XP
> machine.
>
> http://www.petri.co.il/reinstall_tcp_ip_xp.htm
>
> And then one reboots the machine to get everything corrected. And then
> you install stuff back again.
>
> If one has deleted the Winsock out of the registry, the TPC\IP must be
> reinstalled. I did that and I just took to path of reinstalling the O/S
> to correct it. But twice after the install the TCP/IP stack became bad
> and I could only get the 169.xxx IP. The method above corrected it each
> time and the machine was able to get a valid IP from the router.
>
> You should also be careful of using XP's wireless setup (another piece of
> crap) with WEP and WAP. One wrong move and one can turn them on or off,
> causing problems with the connection.
>
> <snip>
>
> I hope this helps on someone encountering the 169.xxx Default MS IP being
> assigned, becuase the machine couldn't get a valid IP.
>
> Duane :)



Relevant Pages

  • DHCP client on PIC Micro
    ... The hardware is a PIC18F6620 and the TCP/IP stack was ... The second router sent a 'bad DHCP ... I compared the DHCP discover packet with the one sent ... out on my windows machine and could find no real difference, ...
    (comp.arch.embedded)
  • Re: Faulty Port 25 (SMTP)?!?!
    ... In the meantime I found out that the TCP/IP stack is actually a ... >>> which is linked to the SAME Router AND ISP as well. ... Are you using DHCP or manually set ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: tcp/ip registry tweak not working
    ... Apparently your Registry change attempts with the TCP/IP Stack ended up partially trashing the stack. ... Using the process above is safer since it is the software that interact with the Registry rather then an individual using the registry Editor. ... tcp stack didnt work might as well try and reset the winsock...and it ... http://www.speedguide.net/analyzer.php to verify the tcp receive window value ...
    (microsoft.public.windowsxp.network_web)
  • Re: A little FYI
    ... simply means that the adapter is set to DHCP for IP addressing and that no ... mean your TCP/IP stack is hosed! ... If you want to turn off Automatic Private ...
    (comp.security.firewalls)
  • Re: Dan...
    ... I had a problem similar to this once, and it had to do with the TCP/IP stack ... not having all the proper settings in the registry. ... > profile as well as uninstalling and reinstalling outlook ...
    (microsoft.public.exchange.connectivity)

Quantcast