The Little Guy Posted August 28, 2012 Share Posted August 28, 2012 Every 5 - 10 minutes while I am on Chrome, I have to wait for Chrome for about 20+ seconds after I click on a link or type in a URL, and at the bottom of the page (where the urls display) it says: "Sending Request..." After that happens I can browse for 5 - 10 minutes perfectly fine then it does it again, and I have to wait for 20+ seconds for it to send the request. I have dealt with it for a few months and now it is just getting annoying. I have been searching the internet for a solution but have yet to find one. Some things I have tried: - Re-install Chrome - Changed my DNS to: Google Public DNS Has anyone here had this problem and gotten fixed? Quote Link to comment Share on other sites More sharing options...
xyph Posted August 28, 2012 Share Posted August 28, 2012 Is it only chrome? Could be bad network hardware. Quote Link to comment Share on other sites More sharing options...
The Little Guy Posted August 28, 2012 Author Share Posted August 28, 2012 Yeah, it seems to only be chrome. Quote Link to comment Share on other sites More sharing options...
xyph Posted August 28, 2012 Share Posted August 28, 2012 Hard to say. Use something like wireshark to check your network traffic when that happens, see if the request is leaving your machine when it gets held up. Quote Link to comment Share on other sites More sharing options...
Philip Posted August 28, 2012 Share Posted August 28, 2012 Possibly one of your extensions? I'd also suggest a traffic inspector (I prefer fiddler2) to see (a) what it is sending, and (b) what the response codes are. Quote Link to comment Share on other sites More sharing options...
The Little Guy Posted August 28, 2012 Author Share Posted August 28, 2012 I disabled the extensions and it still happens I'll try fiddler though, I didn't see much with wireshark, there was too much happening. Quote Link to comment Share on other sites More sharing options...
The Little Guy Posted August 28, 2012 Author Share Posted August 28, 2012 I wasn't doing anything, then randomly these show up in fiddler: http://kysfwnqysl/ http://oiakxvmdlk/ http://iipuinmiwn/ http://cbgumcmwub/ http://sbxejjexrz/ http://njraamgbcs/ They also have large dns times: 10227ms Quote Link to comment Share on other sites More sharing options...
Christian F. Posted August 28, 2012 Share Posted August 28, 2012 Hmm... That is quite worrisome, or at least without any further information they seem quite worrisome. Do you know what applications sent those requests? If not, then figure it ASAP. You might be infected by something, or it might be some bug with Chrome (or any other software). Might even be Conficker or something similar, considering the DNS servers it used were closed down not too long ago. Quote Link to comment Share on other sites More sharing options...
The Little Guy Posted August 28, 2012 Author Share Posted August 28, 2012 I closed Chrome and those gibberish urls stopped, once I opened Chrome they started again. Quote Link to comment Share on other sites More sharing options...
The Little Guy Posted August 28, 2012 Author Share Posted August 28, 2012 Here is why the gibberish urls are in there: https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-discuss/F70-k_PGhEg If you type in a single-word search query, chrome needs to send a DNS request to check if this might be a single-word host name: For example, "test" might be a search for "test" or a navigation to "http://test". If the query ends up being a host, chrome shows an infobar that asks "did you mean to go to 'test' instead". For perf reasons, the dns query needs to be asynchronous. Now some ISPs started showing ads for non-existent domain names ( http://en.wikipedia.org/wiki/DNS_hijacking ), meaning chrome would always show that infobar for every single-word query. Since this is annoying, chrome now sends three random DNS requests at startup, and if they all resolve (to the same IP, I think), it now knows not to show the "did you mean" infobar for single-word queries that resolve to that IP. Quote Link to comment Share on other sites More sharing options...
Christian F. Posted August 28, 2012 Share Posted August 28, 2012 Ah, good to know. Thanks for reporting back on what they were. Unfortunately, it doesn't help with the problem at hand. Quote Link to comment Share on other sites More sharing options...
xyph Posted August 28, 2012 Share Posted August 28, 2012 Using an alternate DNS server could possibly help, couldn't it? OpenDNS works well, assuming you turn off their guide/block pages. Quote Link to comment Share on other sites More sharing options...
The Little Guy Posted August 28, 2012 Author Share Posted August 28, 2012 OpenDNS works well, assuming you turn off their guide/block pages. That is the one I am using Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.