Hi Everyone,
For: sssj408 - Re: "DNS Not Verified" Error Message
This network error's interesting from a technical angle.
PDANet Version 3.02 generates the above error on my XP SP2 PC, tethered via USB cable using a HTC Wildfire Android Phone (Version 2.2.1).
I'm guessing Optimus S phones use a similar android operating system, but you'll have to forgive me guys since I'm no expert in "droid" phones. My background's in programming and PC support.
Okay, firstly - "DNS not verified" only appeared after I upgraded to PDANet 3.02. This error message is generated by PDANet itself, not XP, not the Android O/S. Unfortunately, "June Fabrics" who appear to be the company making PDANet Adapter do not list a solution for this error message on their website. To be fair, they do have an option to contact them via email, so I would suggest anyone with the paid version of PDANet contact them direct via this means. (Please post their reply here if you can, I'd be interested to know what the makers have to say...)
I read sssj408's post carefully. It looks to me like he/she has some fundamental issues with the network configuration (client side) and possibly, the dreaded "drop outs" that all wireless phones can experience. I say this, because "DNS not verified" is not a critical error. I can still obtain internet access.
DNS itself (in most cases) means we use Google Public DNS Servers to resolve (or translate) the websites we visit. Domain Name System serves as phone book for the Internet by translating human-friendly computer hostnames into IP addresses. Two types of IP addresses are resolved:
192.0.32.10 (IPv4) - old style
2620:0:2d0:200::10 (IPv6) - new style
In practice, this means our client software (the network TCP stack that sits on our main PC) needs IPv4 and IPv6 installed. PDANet installs its own "broadband" adapter, however, I noticed IPv4 and IPv6 protocols do not appear to be installed as part of the PDANet TCP stack... Curious, no?
The good news is... we can improve and test the network configuration easily on modern PCs. There's also a very simple way to boost signal strength on droid phones upto 200 % (thus, almost banishing dreaded "dropouts" that sssj408 appears to be experiencing.
Okay - here are the instructions to quickly test your TCP/IP configuration on your XP laptop, or PC (I'm certain later versions of windows will have similar
Network Diagnostics)
Step 1:
Go to> Start > Help & Support > Network Diagnostics > Scan Your System (Ensure scan options set to all) Post results here if you have time.
Step 2:
Add DNS Google Public Servers to your PDANet Adapter settings (TCP/IP stack).
In Control Panel > Network Connections:
Find
PDANet Broadband Adapter
Right Click Select: "Properties" from pulldown menu.
A new window will pop up. Double-click on "Internet Protocol TCP/IP "
or "Internet Protocol Version 4 (TCP/IPv4)" (if installed).
Another new window pops up. Leave "Obtain IP address automatically" SELECTED.
Look at the lower grouping of greyed-out boxes. Select the radio button for "Use the following DNS server addresses:".
Type 8.8.8.8 into the preferred DNS server slot.
Type 8.8.4.4 into the alternate server.
Click "OK" on the properties window.
Boost Your Phone Antenna Signal By 100-200 %
Okay, this solution sounds bizarre, but its been proven to work on the Net. I think the guy who discovered it is a scientist or engineer... Anyway, its very low-cost, easy to implement and easy to measure.
After tethering and starting PDANet on the phone side, sit your phone in a small aluminum pot. Yes! A saucepan will do. The pot acts like a satellite dish, collecting and amplifying the signal sent from your ISP mast. (I get no dropouts at all using this method). On fast servers, I've noticed speeds of 240 kbps can be achieved. Pretty good for a barebones connection.
Other little tweaks: Use firefox or chrome as your browser. I go with firefox since it can "customized" to render webpages faster. (Many guides exist online to show you how).
Where I Am Now...
Using network diagnostics, I get a single FAILED statement:
DNSServerSearchOrder (FAILED) - However, the secondary Google DNS Server (8.8.4.4) is reported as working, so it seems to be a non-critical error.
I still need to install IPv6 and IPv4 protocols as part of the PDANet Adapter "stack". I'll report back here if this solution works or not.
Flush and check your DNS Cache Resolver easily with these commands:
From command prompt > run > cmd.exe > Type ipconfig /all (shows current network config status)
Type in the command "ipconfig /flushdns"
Result : Successfully flushed DNS Cache Resolver (clears bad results).
Kind Regards, OldSchoolTechHead
