<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Are wireless Mini-Cards reliable?</title>
	<atom:link href="http://verizonmininotebook.com/are-wireless-mini-cards-reliable/feed/" rel="self" type="application/rss+xml" />
	<link>http://verizonmininotebook.com/are-wireless-mini-cards-reliable/</link>
	<description>New Verizon Mini Notebook Tricks &#038; Reviews</description>
	<lastBuildDate>Sun, 29 Nov 2009 16:48:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arthur Brain</title>
		<link>http://verizonmininotebook.com/are-wireless-mini-cards-reliable/comment-page-1/#comment-297</link>
		<dc:creator>Arthur Brain</dc:creator>
		<pubDate>Sat, 31 Oct 2009 01:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://verizonmininotebook.com/are-wireless-mini-cards-reliable/#comment-297</guid>
		<description>&lt;a href=&quot;http://www.verizonmininotebook.com&quot;&gt;Verizon Mini Notebook&lt;/a&gt;


I used to have a Dell laptop and I used to have intermittent trouble connecting wirelessly via a D-Link access point to the internet.
 
For ages I blamed the wireless card, or the access point, until one day I figured it out it was actually Windows XP being stupid:
 
Next time you are having trouble connecting, do this:
Start
RUn
cmd
ipconfig /flushdns
 
And try connecting again.
 
The problem with XP is not that it won&#039;t connect (try connecting to an IP address instead of a Name on the internet somewhere and it will be fine), but that it decides it can&#039;t translate names to IP addresses sometimes.
[technically: it caches negative DNS responses].
 
If you create a .bat file on your desktop with the ipconfig /flushdns command in it, you can quickly run it anytime you like. (run notepad, put the line in, then save it as .bat instead of .txt).
 
It is also possible to edit your registry to tell XP to NOT cache negative DNS responses if you want to get really on top of it.</description>
		<content:encoded><![CDATA[<p><a href="http://www.verizonmininotebook.com">Verizon Mini Notebook</a></p>
<p>I used to have a Dell laptop and I used to have intermittent trouble connecting wirelessly via a D-Link access point to the internet.</p>
<p>For ages I blamed the wireless card, or the access point, until one day I figured it out it was actually Windows XP being stupid:</p>
<p>Next time you are having trouble connecting, do this:<br />
Start<br />
RUn<br />
cmd<br />
ipconfig /flushdns</p>
<p>And try connecting again.</p>
<p>The problem with XP is not that it won&#8217;t connect (try connecting to an IP address instead of a Name on the internet somewhere and it will be fine), but that it decides it can&#8217;t translate names to IP addresses sometimes.<br />
[technically: it caches negative DNS responses].</p>
<p>If you create a .bat file on your desktop with the ipconfig /flushdns command in it, you can quickly run it anytime you like. (run notepad, put the line in, then save it as .bat instead of .txt).</p>
<p>It is also possible to edit your registry to tell XP to NOT cache negative DNS responses if you want to get really on top of it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

