01-28-2014 5:41 PM
Solved by: Go to Solution.
01-28-2014 5:50 PM
01-30-2014 12:32 PM
Ive had this issue for 7 months now heading to 8
They have changed my ports, wiring, and outside wiring and router box more than twice each.
I keep showing this issue i will post below i bet you get the same thing right if you check your log file on your router page under diagnosis.
You want a fix? Switch from uverse to TWC or anything else that cost a bit more because atleast you get internet that doesnt drop or act really really slow.
Or does att neeed to send more techs and you be bothered by all this. I just sent them a message giving one more shot on this issue if they fail again im done and out and going to TWC because its been 2 years of people having this issue and it is just crazy.
Even though they ended the year with the most subrcribers to there services im sure this year they will end with the most subcribers lost if this keeps up still
2014-01-29T14:18:19-08:00 L1 sdb: nm_ipv6_add_firewall: (4) The last message was repeated 2 times. 2014-01-29T14:18:22-08:00 L5 cwmp: Post SetParameterValuesResponse 2014-01-29T14:18:22-08:00 L5 cwmp: Receive GetParameterValues 2014-01-29T14:18:22-08:00 L5 cwmp: Post GetParameterValuesResponse (chunk-length - 1737) 2014-01-29T14:18:22-08:00 L4 cwmp: Continue GetParameterValuesResponse (chunk-length - 0) 2014-01-29T14:18:23-08:00 L5 cwmp: Closing connection on HTTP 204 2014-01-29T14:18:23-08:00 L5 cwmp: (SSL) Closing Connection: cwmp.c01.sbcglobal.net 2014-01-29T14:18:39-08:00 L3 sdb: Wi-Fi: Client 70:73:cb:2e:5b:2e joined ATT624. 2014-01-29T14:18:39-08:00 L3 sdb: Wi-Fi: Number of clients associated 2 2014-01-29T14:19:17-08:00 L3 sdb: Wi-Fi: Client 2c:b0:5d:8b:ce:a2 joined ATT624. 2014-01-29T14:19:17-08:00 L3 sdb: Wi-Fi: Number of clients associated 3 2014-01-29T14:23:11-08:00 L3 sdb: Wi-Fi: Client 20:02:af:8d:11:8e left ATT624 2014-01-29T14:23:11-08:00 L3 sdb: Wi-Fi: Number of clients associated 2 2014-01-29T14:31:53-08:00 L3 dnsmasq: no responses from nameserver '18.104.22.168' 2014-01-29T14:31:58-08:00 L3 dnsmasq: nameserver '22.214.171.124' is now responding 2014-01-29T14:35:55-08:00 L3 dnsmasq: no responses from nameserver '126.96.36.199' 2014-01-29T14:35:55-08:00 L3 dnsmasq: nameserver '188.8.131.52' is now responding 2014-01-29T14:37:47-08:00 L3 dnsmasq: no responses from nameserver '184.108.40.206' 2014-01-29T14:37:47-08:00 L3 dnsmasq: nameserver '220.127.116.11' is now responding 2014-01-29T14:39:26-08:00 L3 dnsmasq: no responses from nameserver '18.104.22.168' 2014-01-29T14:39:26-08:00 L3 dnsmasq: nameserver '22.214.171.124' is now responding 2014-01-29T14:40:46-08:00 L3 dnsmasq: no responses from nameserver '126.96.36.199' 2014-01-29T14:40:46-08:00 L3 dnsmasq: nameserver '188.8.131.52' is now responding
01-30-2014 12:39 PM
Yes, the NVG 510 has a DNS issue. There are two simple work arounds:
1) Set the DNS manually on your end devices to 184.108.40.206 or any other publically available DNS of your choice
2) Get your own router, install it behind the RG, put it in DMZplus mode and configure the DNS of your choice in it
01-30-2014 12:50 PM
We should not have to do either of thoses two.
We should not be expected to buy another router on top of what we bought from them to make our service work, they should fix it not us.
secondly Many people have tried as my self changing the dsn to googles and nothing changes, plus that would require to change it for all items, and consoles and tv that uses internet which again shouldnt be needed.
Att should fix this on there end by either issuing new better working modems (for free for thoses with nvg510) that do not have this issue.
We been paying all theses months for service promised that we are not receiving. This should be fixed by them, and not by our expense.
01-30-2014 2:06 PM
I understand your point that this modem has a firmware issue that should have long ago been addressed. Eventually the model will be replaced with something better.
But, if you want it to work NOW...
01-30-2014 2:17 PM
This isnt an issue that has barely came up this issue dates back about two years, and time after time they have issued firmware upgrades and have not adressed this issue, when they come to homes for people with this issue they do not adress this issue. People have had this problem and still for 9+ months now
and still waiting?
Att has to adress this asap!
We dont need a quick fix (mainly because many still that are not too experiences as most dont know this is a nvg510 issue, let alone be able to apply this fix or willing to try in fear of messing something up)
This is a big issue affecting many people on a daily bases frequently.
Its great you are providing people with theses fix (though many have, and you can check the forums, do not work or hardly show any improvement) But this issue has been here for way too long, people are done with thoses fixes, we need a permant one that doesnt cost us any money seeing its not an issue on ourside
or something out of the comfort zone or level of modifying router settings or computing setting that some have issues with.
01-30-2014 2:37 PM
I'm not going to debate when AT&T should have address this issue or when they might.
Normally users get this when the forwarded DNS request has to fight to get out over bad line conditions. People with perfect lines don't seem to have this issue very much. If you've fought the good fight over your line condition/bandwidth and haven't gotten the DNS issue to go away, I don't know what to tell you.
01-30-2014 6:55 PM
01-30-2014 7:20 PM
When searching for wired interference, I can't recommend this post by SomeJoe7777 highly enough:
I wish I could give it another Kudo.
01-30-2014 7:35 PM
02-01-2014 5:49 AM
What did you find that was causing your interference?
02-03-2014 9:03 PM
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.