<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.kai-mai.com">
<channel>
 <title>Kai Mai&#039;s Blog - Take Back the Web - Nodes for tcp</title>
 <link>http://www.kai-mai.com/tags/tcp</link>
 <description>Nodes containing the tag tcp</description>
 <language>en</language>
<item>
 <title>WTF: 169.254.*.*(169.254) IPs Again</title>
 <link>http://www.kai-mai.com/node/107</link>
 <description>&lt;p&gt;
My Windows XP laptop&#039;s wireless card got 169.254.x.x IP address again at work, but the LAN connection still worked.
Then I came home.  Both wireless and LAN connections got 169.254.x.x IPs.  This kind of problem has happens like twice a year.
&lt;/p&gt;
&lt;p&gt;
The fix suggested by Josh Marlino&#039;s comment at &lt;a href=&quot;http://blog.aaltonen.us/2003/10/30/tip-fix-169254-ips/&quot;&gt;aaltonen.us&lt;/a&gt; seems to work by resetting winsock:
&lt;/p&gt;
&lt;pre&gt;

Start &amp;gt; run &amp;gt; cmd
ipconfig /release
ipconfig /flushdns
netsh int ip reset c:\tcp.txt
netsh winsock reset
then reboot.
&lt;/pre&gt;
&lt;p&gt;
But sometimes(like tonight), I had to restart my DSL modem, wireless router, and reboot my laptop multiple times to get back a valid IP.
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/134&quot;&gt;169.254&lt;/a&gt; &lt;a href=&quot;tags/135&quot;&gt;ip&lt;/a&gt; &lt;a href=&quot;tags/136&quot;&gt;tcp&lt;/a&gt; &lt;a href=&quot;tags/137&quot;&gt;winsock&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">169.254</category>
 <category domain="http://www.technorati.com/tag">ip</category>
 <category domain="http://www.technorati.com/tag">tcp</category>
 <category domain="http://www.technorati.com/tag">winsock</category>
 <pubDate>Tue, 02 Oct 2007 21:46:34 -0700</pubDate>
</item>
</channel>
</rss>

