"DNS lookup failed" error message while using Google Chrome

Reset was completed successfully and lspfix found no missing modules. ipconfig and nslookup data attached.
 

Attachments

  • TCP.txt
    1.5 KB · Views: 2
  • lookup3.log
    148 bytes · Views: 1
the dns provided by your ISP is not operational as
it doesn't answer PING and
C:\Documents and Settings\Jeff>nslookup google.com. 200.1.104.36
Server: ns2.flowtrinidad.com
Address: 200.1.104.36

*** ns2.flowtrinidad.com can't find google.com.: Query refused
that address is registered correctly to
Checking IP: 200.1.104.36...
Name: ns2.flowtrinidad.com
IP: 200.1.104.36
Domain: flowtrinidad.com
I can penetrate only two levels(#17 & #18) into that domain before there's problems internally with flowtrinidad.com
16 130 ms 130 ms 127 ms 63.245.68.70
17 128 ms 131 ms 130 ms 200.1.111.62
18 131 ms 130 ms 130 ms 200.1.111.60

19 * * * Request timed out.

One last attempt try nslookup google.com. 8.8.8.8
the third parameter is the google dns and causes your system to use the google dns just for this time
 
using that last example, you might also try accessing the OpenDNS servers
# 208.67.222.222 (resolver1.opendns.com)
# 208.67.220.220 (resolver2.opendns.com)
 
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Name: google.com
Addresses: 74.125.229.48
74.125.229.52
74.125.229.51
74.125.229.50
74.125.229.49


Server: resolver1.opendns.com
Address: 208.67.222.222

Name: google.com
Addresses: 74.125.229.49
74.125.229.52
74.125.229.48
74.125.229.50
74.125.229.51


Server: resolver2.opendns.com
Address: 208.67.220.220

Name: google.com
Addresses: 74.125.229.49
74.125.229.48
74.125.229.52
74.125.229.50
74.125.229.51
 
that looks good - - let's put the OpenDSN server addresses into the TCP settings manually as
  • 208.67.222.222
  • 208.67.222.220

then run these
ipconfig /flushdns
net stop "dns client"
net start "dns client"


disconnect the system from the router/modem; wait 30 secs and then reconnect

nslookup google.com. should respond with
C:\Documents and Settings\Jeff>nslookup google.com.
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: google.com
Addresses: 74.125.224.48, 74.125.224.52, 74.125.224.49, 74.125.224.51
74.125.224.50

and a tracert google.com should look nearly like
C:\Documents and Settings\Jeff>tracert google.com

Tracing route to google.com [74.125.224.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 12 ms 12 ms 76.172.xxx.yyy
3 13 ms 14 ms 10 ms 76.167.22.189
4 13 ms 12 ms 12 ms ae5.vnnyca2-rtr1.socal.rr.com [66.75.147.38]
5 21 ms 23 ms 23 ms be13-lsanca4-rtr1.socal.rr.com [66.75.147.3]
6 17 ms 19 ms 18 ms ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
7 20 ms 19 ms 18 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
8 19 ms 19 ms 19 ms 72.14.198.73
9 18 ms 19 ms 15 ms 64.233.174.238
10 18 ms 18 ms 19 ms 64.233.174.188
11 28 ms 28 ms 28 ms 64.233.174.205
12 28 ms 28 ms 28 ms 209.85.250.65
13 26 ms 28 ms 25 ms 64.233.174.109
14 26 ms 28 ms 28 ms google.com [74.125.224.113]

Trace complete.
and your browser should now access http : // google.com/
just fine
 
Sorry to disappoint but the results don't look good:

C:\Windows\system32>nslookup google.com.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 208.67.222.222

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Windows\system32>tracert google.com

Tracing route to google.com [74.125.229.49]
over a maximum of 30 hops:

1 * * Client-PC.flowtrinidad.com [190.213.84.86] reports: Dest
ination host unreachable.

Trace complete.
 
Sorry to disappoint but the results don't look good:

C:\Windows\system32>nslookup google.com.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 208.67.222.222
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

Just the last test for OpenDNS was just fine
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: google.com
Addresses: 74.125.229.49
74.125.229.52
74.125.229.48
74.125.229.50
74.125.229.51
but even worse, is the status of YOUR PC
C:\Windows\system32>tracert google.com

Tracing route to google.com [74.125.229.49]
over a maximum of 30 hops:

1 * * Client-PC.flowtrinidad.com [190.213.84.86] reports: Destination host unreachable.

Trace complete.
I firmly believe the DNS setting is fine and the problem is in your PC.

Just for clarification, if you're having such a time with this system, how is it you can
access Techspot to post these results?
 
Between the dns and the timeout errors I can access websites, although the speed is very limited. I sit on this page and f5 every so often.

Until recently, I've been using a desktop machine on this connection and I've been having the same issues for over a month. Also, I occasionally use this laptop on another internet connection with the same ISP without any problems. On those occasions though, I used wi-fi.
 
Updated my driver but sadly, no improvement. Pinging google.com still results in lost packets and tracert still reports "Destination host unreachable".
 
man - - I'm at the end of my rope. Your system has issues and I can only guess it's a virus or trojan.
 
I think the problem is due to Dell's remote access utility. When I disabled IPv6 with the Microsoft fix, upon restart I got a message saying the Advanced Network Service wasn't running and the utility could not be started. For the duration of that session my internet worked fine. Today I got the same message and my internet seems fine for now.

I found that a few people had connectivity issues when this service is running. Is it's okay to disable this service permanently, and if so, how?
 
my goodness!

To control Services you need to get a command prompt,
then enter runas /user:xxx cmd
were xxx is a login with admin privileges

in the new window, enter services.msc

the list is in Name Order, so scroll to Advanced Network Service
double click the name and STOP it.
change the Startup type to DISABLE.

click apply, click ok
 
tommy38

I have had this problem for a few weeks and I carefully worked through all possible reasons ,, i went on lots of trouble-shooting sites to research their answers , I HAVE SOLVED THIS PROBLEM FOR ME ANYWAY, :) the answer is ,,,,,, (drum roll here..lol) make double sure there are no updates waiting to be installed on your machine, pending updates will cause this problem.
IT was black and white for me, I was struggling to get on the internet at all . then 10 mins later after I updated the problem was totally gone,and i was back to my speedy internet as normal ,I know this sounds unlikely compared to all the technical answers above and elsewhere, but please try it and post back , after all it cant do any harm can it?
 
Same problem after deleteing files

Is there a file in hard drive C that can mess with DNS if deleted because after deleteing some files errors popped up then i turned the computer off and back on it said it was deleteing corrupted files and recovering others it went back to normal but now it says DNS lookup failed
 
Back