06-06-2016 10:54 AM
Hey,
Got a new RV042. Several times per day I get trouble connecting to internet. Browser says trouble with DNS.
I have tried get automatic DNS and also set manually DNS.
I can resolve the problem temporary by just going into setting on the RV042 and the setup fro WAN connection. After I hit Save, Internet comes back on.
I have updated to last Firmware. Restarted everything. But this problem keep on coming.
Any idea why or how to troubleshoot more?
06-06-2016 12:18 PM
Here are a couple of questions and suggestions which might be helpful:
- is your DNS server an internal one or are you using a DNS server in the Internet?
- if your DNS server is internal is it possible that something is affecting its ability to access the Internet?
- if your DNS server is in the Internet then the next time this problem happens you might check for issues accessing the DNS server. Perhaps start with something like nslookup that will query the DNS server. You might also try a ping to the server address to verify basic IP connectivity.
- Is it possible that the problem with DNS is really a problem about getting to the Internet? When this problem occurs can you just check for Internet access by ping some Internet resource by name, and if that fails can you ping that resource by IP address? If you can ping by address but not by name then it does confirm that there is a problem with DNS name resolution. Note that you need to be prepared for this by recording some resource both by its name and by its IP address.
- you might also check for possible browser/DNS issues by trying to browse to some Internet resource using the normal name/URL and if that fails then try to browse to that resource using its IP address. This one is even more tricky to prepare for. You must not only know both the URL and the IP address, but you must make sure that this site will respond to a request to its IP address (quite a few sites I tested this with would not respond to http://<IPaddress>; or to https://<IPaddress>).
HTH
Rick
06-06-2016 02:24 PM
I can tracert an ip at google, but not do a nslookup when connection is lost.
All I have to do to get the connection back is to save setting in router without changing anything.
Add nslookup and tracert with connection and after lost.
There is nothing inside log on router either.
(edit) Oh, and I can ping IP but not url name.
06-09-2016 01:11 PM
Thanks for the additional information. It makes it pretty clear that when you experience the problem that you have IP connectivity to the Internet. So it does seem to be some issue specific to DNS.
When you experience the problem is the RV042 able to access the DNS server? ping by IP address? And when you experience the problem is a user PC able to access the DNS server? ping by IP address?
HTH
Rick
06-13-2016 02:43 AM
I did as gusgura7050 talked about. Rolled back from 4.2.3.07 to 4.2.2.08.
Now been three days. Have not had problem since then.
To bad a newer firmware is causing so much problem. Is there a way to inform Cisco about the problems with a firmware?
06-13-2016 08:46 AM
Thanks for posting back to the forum and letting us know that reverting the version of software seems to have resolved the problem. If your RV042 is covered by a maintenance agreement then you can open a case with Cisco TAC which is the best way to let them know that it does seem to be a bug in the newer version of code.
HTH
Rick
06-07-2016 01:14 AM
Hi again.
Even more info if it help.
The problem accurs on all devices. Wired and wireless. I have a switch between the RV042 and computer.
I have to rule this out. So one computer will be wired directly into the RV042. That way I can see if this also loses DNS when all other do.
But I'm afraid it does, since fiing the problem is only to save settings on the RV042 to get it up and running again for a half hour or so.
06-09-2016 11:04 AM
I have the same issue, but only after upgrade firmware to 4.2.3.07 from 4.2.2.08.
I'll try to downgrade to previous firmware, and see if it solve the problem...
06-13-2016 02:44 AM
I did this three days ago. No problem since then.
So earlier firmware is fixing this problem for me.
Thanks!
06-14-2016 04:08 PM
I did that but... (gasp)
I briked my router...
so now i don't have the problem but neither my router... :'(
06-15-2016 08:03 AM
Any information on what you did during the code rollback that broke your router?
HTH
Rick
08-12-2016 11:31 AM
Power failure.
Wasn´t connected to a nobreak, and a power cut occur...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide