Ok, nothing untoward in the hosts file, so can rule that out. Tried all the steps above and no joy. Some info below. The trace goes awry at hop 9, and the ping is pinging the wrong IP address for Google.
This from another PC on the same network:
TRACERT
1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 29 ms 28 ms 217.47.187.122
3 29 ms 29 ms 28 ms 217.47.187.161
4 38 ms 41 ms 40 ms 213.1.69.154
5 37 ms 37 ms 38 ms 213.120.157.22
6 39 ms 37 ms 37 ms 213.120.157.178
7 48 ms 37 ms 37 ms 109.159.250.90
8 47 ms 47 ms 48 ms core2-te0-13-0-0.ilford.ukcore.bt.net [109.159.250.11]
9 45 ms 44 ms 45 ms 109.159.254.62
10 44 ms 44 ms 44 ms 195.99.126.58
11 47 ms 47 ms 45 ms 209.85.255.175
12 47 ms 45 ms 48 ms 209.85.251.202
13 46 ms 45 ms 45 ms 74.125.230.148
Trace complete.
Google.com
NSLOOKUP
C:\Documents and Settings\D>nslookup google.com
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1
Non-authoritative answer:
Name: google.com
Addresses: 74.125.230.114, 74.125.230.116, 74.125.230.112, 74.125.230.115
74.125.230.113
PING
Pinging google.com [74.125.230.147] with 32 bytes of data:
Reply from 74.125.230.147: bytes=32 time=43ms TTL=52
Reply from 74.125.230.147: bytes=32 time=43ms TTL=52
Reply from 74.125.230.147: bytes=32 time=44ms TTL=52
Reply from 74.125.230.147: bytes=32 time=42ms TTL=52
Ping statistics for 74.125.230.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 44ms, Average = 43ms
This from the problematic PC:
TRACERT
1 <1 ms <1 ms <1 ms 192.168.0.1
2 111 ms 65 ms 34 ms 217.47.187.122
3 * 29 ms 29 ms 217.47.187.161
4 47 ms 55 ms 45 ms 213.1.69.154
5 177 ms 123 ms 185 ms 213.120.157.22
6 142 ms 119 ms 98 ms 213.120.157.178
7 39 ms 106 ms 41 ms acc1-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.100]
8 43 ms 43 ms 44 ms core1-te0-12-0-4.ealing.ukcore.bt.net [109.159.250.5]
9 45 ms 80 ms 45 ms core3te-0-3-0-0.telehouse.ukcore.bt.net [62.172.102.1]
10 44 ms 66 ms 73 ms 10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
11 144 ms 142 ms 148 ms 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92.241]
12 206 ms 176 ms 241 ms 10gigabitethernet5-3.core1.lax1.he.net [72.52.92.226]
13 251 ms 239 ms 276 ms 10gigabitethernet1-3.core1.lax2.he.net [72.52.92.122]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Google.com
NSLOOKUP
C:\Documents and Settings\Marble Slab>nslookup google.com
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1
Non-authoritative answer:
Name: google.com
Addresses: 74.125.230.145, 74.125.230.146, 74.125.230.144, 74.125.230.148
74.125.230.147
PING
Pinging google.com [204.152.194.252] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 204.152.194.252:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),