hugoschuil / namebench

Automatically exported from code.google.com/p/namebench
Apache License 2.0
0 stars 0 forks source link

NAMEBENCH Stuck Or Stop Working or Not Responding During Sending 250 queries to 11 servers... [...../2750] Error Fix #241

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Your Namebench Stop Working Or Stuck During "Sending 250 queries to 11 
servers... [...../2750]" Do Following Steps
1.Download Python & Download Namebench Who Requires Python , Extract & Open 
file "namebench" its about 2.41kb, cmd window will open after that Namebench 
Will start (namebench is running through python) Click on "Start Benchmark" 
namebench start working & you can see its all process in CMD window keep your 
eye on the process , if your namebench starting to stuck you can see error like 
this "All nameservers have warning: www.facebook.com appears incorrect: 
star.c10r.facebook.com (likely a false positive)" if that kind of error comes 
during process namebench surely stuck, Copy that error line & paste in Notepad 
& save as textfile
Now Open Task Manager & End Namebench Process.     
2.Ok So You Have To Know Namebench use Your Browser's History For Its Processes 
So You Should Browse & Make History In Your All Browsers For Example If You 
Have 3 Browsers Internet Explorer, Chrome & Firefox So You Have To Browse 
Atleast 20 To 30 Pages From Your Each Browser. Now Open textfile where you 
copied that errorline Next you have to browse website which is giving in that 
error line for Example All nameservers have warning: www.facebook.com appears 
incorrect: star.c10r.facebook.com (likely a false positive)in this error you 
have WWW.FACEBOOK.COM so you have to browse & make Heavy History of 
www.Facebook.com for your Browser so you have to browse Facebook for atlest 50 
times" if there is twitter or paypal or anyother website just browse that 
website too many times & make that website history in your browsers
3. After That Start namebench it will work perfectly
4.I do This in Windows XP SP3 its work perfectly

Original issue reported on code.google.com by pradeep....@gmail.com on 26 Sep 2013 at 6:47