QUOTE (eyeball @ Jul 20 2008, 04:58 AM)

try browsing to
http://66.249.81.99 on that pc and see what happens, Then we can be certain that DNS is the problem here.
QUOTE (eskimo427 @ Jul 19 2008, 07:24 AM)

If I enter a ip address for a site then it will go to the site
Like I said, a Wireshark capture would let us see exactly what's going on: if the requests are made properly, that the router gives proper answers and all that (for both IPv4 and IPv6 traffic). Then if it gets the right answers, and uses another IP, then we can blame windows for it.
Perhaps 192.168.1.1 is a server and he's running his own [misconfigured] DNS, some routers also send invalid replies to IPv6 devices (blame dproxy), etc. There's tons of possibilities here, and again, a Wireshark cap would let us know for sure if the problem is with the computer or the network, and propose solutions based on that instead of the current guessing game.
And indeed, since everything resolves to 1.0.0.0 it's not the hosts file (what's the odds of every web site being in there in the first place?)
Did I mention a Wireshark cap yet?