Re: A little FYI
From: Mitch4949 (mkaften_at_att.invalid)
Date: 11/25/03
- Next message: Debbie: "Anyone here from the UK?"
- Previous message: Pete Smith: "Re: Firewall config for Speedtouch 510"
- In reply to: Duane Arnold: "Re: A little FYI"
- Next in thread: Duane Arnold: "Re: A little FYI"
- Reply: Duane Arnold: "Re: A little FYI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 25 Nov 2003 11:56:52 GMT
The 169.XXX address is simply the MS "autoconfigure" address. The address is
assigned to a network adapter when it is configured to receive an assigned
address but no address is available for whatever reason...no DHCP server, no
addresses left...whatever. The address is not routable on the internet. When
you straighten out your DHCP situation, or manually assign your NIC an IP
address, the "problem" will go away. Yes, sometimes in Win9x you have to
reboot to correct the situation. See the following link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;310524&Product=winxp
"Duane Arnold" <notme@notme.com> wrote in message
news:Xns943E27CACED28darnold92insightbbco@204.127.199.17...
: "Wayne McGlinn" <wayne.mcglinn@nospam.didata.com.au> wrote in
: news:3fc2f211$0$31752$c30e37c6@lon-reader.news.telstra.net:
:
: >
: > "Iceman©" <iceman@cool.net> wrote in message
: > news:bprfmn$1rl8sr$1@ID-132761.news.uni-berlin.de...
: >>
: >> "Duane Arnold" <notme@notme.com> wrote in message
: >> news:Xns9427E46EA93D6darnold92insightbbco@63.240.76.16...
: >> > 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.
: > <snip>
: >
: > Duane, you're totally wrong about this. Getting a 169.254.0.0 /16
: > address simply means that the adapter is set to DHCP for IP addressing
: > and that no DHCP server is available. *Or* that there is no
: > connection. It does *not* mean your TCP/IP stack is hosed! If you
: > want to turn off Automatic Private IP Addressing (APIPA) then try
: > http://www.petri.co.il/disable_apipa.htm for details. Also try these
: > links:
: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dniph/
: > html/pnpip.asp
: > http://www.microsoft.com/windowsxp/home/using/productdoc/en/default.asp
: > ?url=/WINDOWSXP/home/using/productdoc/en/sag_TCPIP_pro_AutoConfig.asp
: > (url may wrap)
: > The 169.254.0.0 /16 network is reserved by IANA http://www.iana.org
: > for "link local", it doesn't belong to Microsoft. Refer to RFC3330 for
: > details of all the reserved addresses, including the private ip
: > addresses referred to in RFC1918.
: > Recommending to people to edit their registry to "uninstall" TCP/IP is
: > uneccessary and bad advice.
: >
: > Wayne McGlinn
: > Brisbane, Oz
: >
: >
: >
:
: Well,
:
: I don't even know where you're coming up with this 169.xxx is not an Auto
: assigned IP number when the machine cannot get a valid IP due to some time
: out situation. I got the 169 IP on few occasions and even doing an
IPCONFIG
: /release and /renew would not release TCP/IP.
:
: Yes, you correct that the is not a MS IP. It's is an IP issued by IANA for
: this particular circumstance, since IANA controls the usage IP(s). But the
: fact remains that the machine could not get a valid IP and the MS O/S on
: all occasions that I have encountered that 169.xxx IP being assigned would
: would not release it.
:
: That IP will allow the machine connected to a LAN to communicate with
other
: machines on the LAN. But the machine cannot access the Internet with the
IP
: being assigned.
:
: http://www.newschool.edu/ac/doc/pubs/faq.html
:
:
: Yes, you're correct again that TCP/IP is not corrupted when the 169.xxx IP
: is assigned. But the fact still remains that one cannot release the IP
: using IPconfig on Windows 9'X to Win XP nor can it be released by using
: XP's utility to fix TCP/IP through the NIC's properties.
:
: So, where does that leave one? Either, one has to rebuild the machine to
: get it to release the 169.xxx IP or one has to get creative and go to
: Google and find out how to go to the registry and fix the situation
without
: taking it any further.
:
: This information on the TCP/IP Stack rebuild was passed to me when I got
: the 169.xxx IP on Win 2k machines and it fixed it without me having to
: rebuild the machine, which I did rebuild the machine when I first
: encountered the problem not knowing how to get out of the situation. I
have
: given this advise to others to get them out of the situation and it has
: work for them when they were stuck on what to do next.
:
: And it happened to me on the Windows XP O/S recently.
:
: Do you know what this kind of advise is called? It is called a *Work
: Around*.
:
: It is *solid* advise for anyone looking to get out of the situation of the
: 169.xxx IP being assigned and the machine will not release the 169.xxx IP.
:
: Thank you for you response, but you are wrong. It is not bad advise, if it
: helps someone get out of a bad situation, which this has done for me and
: others I have passed the info along too.
:
: Duane :)
:
- Next message: Debbie: "Anyone here from the UK?"
- Previous message: Pete Smith: "Re: Firewall config for Speedtouch 510"
- In reply to: Duane Arnold: "Re: A little FYI"
- Next in thread: Duane Arnold: "Re: A little FYI"
- Reply: Duane Arnold: "Re: A little FYI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
