Its not DNS
please see below I followed some of the instructions I found on other sites maybe that will put some light on this problem,
and be aware that this does not resolve this issue as this still comes back after reboot (i have ommited certain entries and wil use different collors to make reading easy:
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Nina-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-19-66-08-49-30
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Lease Obtained. . . . . . . . . . : 31 sierpnia 2009 23:20:46
Lease Expires . . . . . . . . . . : 1 września 2009 23:20:51
Default Gateway . . . . . . . . . : 0.0.0.0
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 194.204.159.1
217.98.63.164
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Windows\system32>
ping 213.25.2.22 (this is the gateway of my router)
Pinging 213.25.2.22 with 32 bytes of data:
Reply from 192.168.1.4: Destination host unreachable.
C:\Windows\system32>
ping 216.239.59.104 (this is IP adress of google site)
Pinging 216.239.59.104 with 32 bytes of data:
Reply from 192.168.1.4: Destination host unreachable.
C:\Windows\system32>
route print
===========================================================================
Interface List
11...00 19 66 08 49 30 ......NVIDIA nForce Networking Controller
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
(I marked with red the invalid entry. It sends all traffic meant for gateway to on-link which I think is just my computer it self, in green is the right entry which I later re add)
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 On-link 192.168.1.4 20 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.4 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 192.168.1.4 30
169.254.255.255 255.255.255.255 On-link 192.168.1.4 276
192.168.1.0 255.255.255.240 On-link 192.168.1.4 276
192.168.1.4 255.255.255.255 On-link 192.168.1.4 276
192.168.1.15 255.255.255.255 On-link 192.168.1.4 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.4 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.4 276
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
1 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
C:\Windows\system32>
route delete 0.0.0.0
OK!
(this is to delete the invalid routing entry)
C:\Windows\system32>
route print
===========================================================================
Interface List
11...00 19 66 08 49 30 ......NVIDIA nForce Networking Controller
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 192.168.1.4 30
169.254.255.255 255.255.255.255 On-link 192.168.1.4 276
192.168.1.0 255.255.255.240 On-link 192.168.1.4 276
192.168.1.4 255.255.255.255 On-link 192.168.1.4 276
192.168.1.15 255.255.255.255 On-link 192.168.1.4 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.4 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.4 276
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
1 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
C:\Windows\system32>
route add 0.0.0.0 mask 0.0.0.0 192.168.1.1 if 11 (and this is to re add the entry that i deleted by accident)
OK!
C:\Windows\system32>
ping 216.239.59.104
Pinging 216.239.59.104 with 32 bytes of data:
Reply from 216.239.59.104: bytes=32 time=89ms TTL=50
C:\Windows\system32>
ping www.google.com
Pinging
www.l.google.com [74.125.39.105] with 32 bytes of data:
Reply from 74.125.39.105: bytes=32 time=72ms TTL=49
as you see above the invalid routing table entry in windows 7 creates this problem
after deleting this entry and readding correct route to gateway it works ok.
after i rebooted my gf comuter problem came back
i will write a script so she can double click and it will run the comands to delete the entry but this is not the kind of sollution I want