<?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: &#8220;wiki does not exist&#8221; Error</title>
	<atom:link href="http://www.catuira.com/wiki-does-not-exist-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.catuira.com/wiki-does-not-exist-error/</link>
	<description>The Official Website of Mike Anthony Catuira</description>
	<lastBuildDate>Thu, 12 Jan 2012 12:26:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Natetron</title>
		<link>http://www.catuira.com/wiki-does-not-exist-error/comment-page-1/#comment-33830</link>
		<dc:creator>Natetron</dc:creator>
		<pubDate>Mon, 18 Jul 2011 17:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.catuira.com/?p=755#comment-33830</guid>
		<description>SOLUTION:
 
Everything has been absolutely trouble-free since I manually took the router address out of my DNS server list two days ago. I&#039;m satisfied that the DNS proxy dis-service that is built into the WRT160N v3 is entirely responsible for the screwy DNS issues described above.
  
It&#039;s bad enough when a DNS query fails to resolve, but at least the outcome is 404s, blank webpages, or red-X broken graphics everywhere. But when DNS returns an IP that is ENTIRELY WRONG, such that a query for facebook.com returns the IP of myspace.com and we end up on the WRONG SITE (a true example experienced by more than one of us), that is not just a failure, it&#039;s a security vulnerability as dangerous as a hacked Hosts file. LinksysByCisco needs to do more than just take it seriously, they need to FIX IT.
 
In the meantime, I suggest everyone take these steps to work around the problem:
1) Open a commant prompt and run IPCONFIG /ALL . Notice that your active network adapter shows your WRT160N&#039;s address (mine is 192.168.1.1) is listed as the first DNS server. This is the problem and we are about to do something about it.
2) You should also see at least two more DNS server addresses following the router&#039;s address. If not, then log into your router and go to the Status page and look at the DNS servers listed there.
3) In Windows, go to your network adapter settings and edit its TCP/IP properties as follows:
4) Change the DNS from automatic to manual, and enter the two DNS servers from step 2. Do not include your router&#039;s address here! (Optional: if you have more than two DNS servers then you can click the Advanced button to add them to the DNS list.)
5) Apply/OK all the changes, then run IPCONFIG /ALL again to confirm that your router&#039;s address is no longer in the list of DNS servers.
6) Enjoy the wonders of the internet thanks to DNS that works as expected.
7) Wonder when Linksys is going to fix it.</description>
		<content:encoded><![CDATA[<p>SOLUTION:</p>
<p>Everything has been absolutely trouble-free since I manually took the router address out of my DNS server list two days ago. I&#8217;m satisfied that the DNS proxy dis-service that is built into the WRT160N v3 is entirely responsible for the screwy DNS issues described above.</p>
<p>It&#8217;s bad enough when a DNS query fails to resolve, but at least the outcome is 404s, blank webpages, or red-X broken graphics everywhere. But when DNS returns an IP that is ENTIRELY WRONG, such that a query for facebook.com returns the IP of myspace.com and we end up on the WRONG SITE (a true example experienced by more than one of us), that is not just a failure, it&#8217;s a security vulnerability as dangerous as a hacked Hosts file. LinksysByCisco needs to do more than just take it seriously, they need to FIX IT.</p>
<p>In the meantime, I suggest everyone take these steps to work around the problem:<br />
1) Open a commant prompt and run IPCONFIG /ALL . Notice that your active network adapter shows your WRT160N&#8217;s address (mine is 192.168.1.1) is listed as the first DNS server. This is the problem and we are about to do something about it.<br />
2) You should also see at least two more DNS server addresses following the router&#8217;s address. If not, then log into your router and go to the Status page and look at the DNS servers listed there.<br />
3) In Windows, go to your network adapter settings and edit its TCP/IP properties as follows:<br />
4) Change the DNS from automatic to manual, and enter the two DNS servers from step 2. Do not include your router&#8217;s address here! (Optional: if you have more than two DNS servers then you can click the Advanced button to add them to the DNS list.)<br />
5) Apply/OK all the changes, then run IPCONFIG /ALL again to confirm that your router&#8217;s address is no longer in the list of DNS servers.<br />
6) Enjoy the wonders of the internet thanks to DNS that works as expected.<br />
7) Wonder when Linksys is going to fix it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arniceous</title>
		<link>http://www.catuira.com/wiki-does-not-exist-error/comment-page-1/#comment-5657</link>
		<dc:creator>Arniceous</dc:creator>
		<pubDate>Wed, 04 Aug 2010 18:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.catuira.com/?p=755#comment-5657</guid>
		<description>i have it again and cant get rid of it when i go to amazon.com it came from wikimedia when you lsiten to music with java plugin. some sort of exploit that attacks via crossed linked scripting on web pages</description>
		<content:encoded><![CDATA[<p>i have it again and cant get rid of it when i go to amazon.com it came from wikimedia when you lsiten to music with java plugin. some sort of exploit that attacks via crossed linked scripting on web pages</p>
]]></content:encoded>
	</item>
</channel>
</rss>

