APIPA 169 254 and Reset Router

Windows XP again! Due to network problems on a desktop and two notebook computers, I enjoy the weekend with Windows XP. Not a question easily: no / etc / init.d / networking or / etc / network / interfaces there. I get a bonus: each finished changing a configuration and save it, I had time to chat, because the computer must be restarted. On desktop computers, network module failed to call DHCP and IP address set to 169.254.xy (the last two sections can vary.) Because it is connected to the router and the router is running DHCP request is successful, I suspect the DHCP client module problematic. Coupled with an active Internet Explorer itself every user login, I suspect leads to spyware. By comparing the practicality of repair desktop computers, I decided to do reinstall Windows XP. It's up to what the cause, the important computer owners can immediately use the machine to access the Internet. Opportunity also to immediately pair Mozilla Firefox and give an explanation to them for moving tools. It turns out the more troublesome issue come the next day. DHCP client on the two notebooks failed to get an IP address, and only have an allotted number of legendary 169 254! I run the free utility Ad-Aware and it appeared a few tens of files that are positively marked troubled by the Ad-Aware. This reminds me of a similar activity in the month of October and I was intrigued to actually fix a crippled network module only. As far as possible not to reinstall! My search results through Google about 169,254 IP addresses generate an explanation that the number is given if the computer is connected to a hub and there is no Internet connection, The computers are connected to a hub, and there is no Internet connection. In this configuration, the computers are assigned IP addresses Generally in the range of 169.254.xy, WHERE x and y are numbers between 1 and 254. - How to troubleshoot home networking in Windows XP, Microsoft Help and Support 169.254.xy IP address is provided by the IANA for Automatic Private IP Addressing (APIPA). Thereby avoiding possible conflicts of IP addresses. The problem: the Internet connection is clearly there and the existing DHCP server on the router worked fine. I check the table in the router's DHCP service request, even empty. Means the server does not accept requests from clients. Because I am sure that the DHCP server is working fine, I strongly suspected the problem of failure to get an IP address automatically is in notebooks - more precisely in Windows XP that run there. With the simple assumption that there are problems with the network module in Windows XP, I tried to fix with WinSockFix, let alone discussed the possibility of Internet connection failed because of wrong or deleted entries in the registry. There are no results as well. While looking for another solution, I set both the notebook with a static IP address, so the wearer can still work with an Internet connection. Indeed become less flexible, because it must be changed according to the rules used in the local network. While the wisdom for me: because the need to address DNS that is memorable for the purposes of this notebook repair, I finally put in the computer's DNS server GNU / Linux. I select from DJ Bernstein's djbdns. In the early days of using GNU / Linux I chose qmail instead of sendmail, so not too familiar with "style" Bernstein. Dnsmasq which has been my life - and only forward DNS requests to the ISP's DNS server - removed. I accidentally found an article written in the Help with Windows, because the exact same title used by the message that appears in one notebook, "Limited or no connectivity" Network Error. The solution is simple: you should reset the router! It's really ridiculous to me that you are sure there is no problem with the router. But the absurdity of it seems to still be forgiven: the author of the article is not to explain that this issue only appears in the notebook and there's no any disturbances on the computer desktop. Just like what I experienced: the computer desktop that is requesting service from the routers DHCP fine.