Switched from AT&T DSL to Uverse, minor issue

mikecLA

Weaksauce
Joined
Jan 20, 2011
Messages
101
I've been on uverse with an NVG510 modem for a few months, and I'm having an issue with the connection going down for about a millisecond or so every so often. You don't notice it when web browsing, but the problem is that I have an ODBC connection open in one of my Foxpro apps, and that millisecond it goes up and down is enough to make the ODBC connection vomit. Never had this issue with DSL. Any ideas?
 
Using that NVG510 as your switch too? I take it this connection is across your private LAN?
Was happy to see them start using Motorola gateways instead of the crappy 2Wire units like I have...but what I did was use my own router and DMZPlus it...effectively making the 2Wire just a bridged modem.
 
Using that NVG510 as your switch too? I take it this connection is across your private LAN?
No.

I forgot what the mode is called on the modem, but I basically bypassed the firewall and everything in it. The modem goes to a dedicated Untangle server, which goes to a ProCurve 1810 Switch.

Had it set up the same way on DSL with no issues.
 
So the ODBC connection is across your LAN using the HP ProCurve? Staying on the LAN side, right ? Not going out through some VPN tunnel or something?
FoxPro is chatty and quite dependent on name resolution working well...my first hunch would be to look at what's doing the name resolution on the LAN. Maybe subtle changes in DNS.
 
Yes, the ODBC connection is on the FoxPro Machine which is connected to the LAN, no tunnels. I'm not sure if a DNS lookup is even being done, the ODBC connection uses a static ip address to connect.
 
Apparently, the NVG510 has DNS issues that AT&T refuse to acknowledge or update via firmware. Googled it, and others have gotten around it by putting the modem into bridge mode via ip pass-through and using another router behind it.

I already had it set up this way with Untangle as my router, and it doesn't work (well, the setup works, but I still have the DNS issues). My logs are filled with entries like this:

2012-04-03T09:17:34-07:00 L3 dnsmasq[2180]: nameserver '68.94.156.1' is now responding
2012-04-03T09:17:34-07:00 L3 dnsmasq[2180]: no responses from nameserver '68.94.156.1'
2012-04-03T09:17:34-07:00 L3 dnsmasq[2180]: nameserver '68.94.156.1' is now responding
2012-04-03T09:23:26-07:00 L3 dnsmasq[2180]: no responses from nameserver '68.94.157.1'
 
My television uses that same NVgarbage510 modem, although I use comcast for ISP, and uverse IP TV has packet loss quite often resulting in jacked up picture. I am wondering if I can return this 2wire box and trade it for a moto box? I just use IPTV uverse, not internet.
 
Apparently, the NVG510 has DNS issues that AT&T refuse to acknowledge or update via firmware. Googled it, and others have gotten around it by putting the modem into bridge mode via ip pass-through and using another router behind it.

I already had it set up this way with Untangle as my router, and it doesn't work (well, the setup works, but I still have the DNS issues). My logs are filled with entries like this:

2012-04-03T09:17:34-07:00 L3 dnsmasq[2180]: nameserver '68.94.156.1' is now responding
2012-04-03T09:17:34-07:00 L3 dnsmasq[2180]: no responses from nameserver '68.94.156.1'
2012-04-03T09:17:34-07:00 L3 dnsmasq[2180]: nameserver '68.94.156.1' is now responding
2012-04-03T09:23:26-07:00 L3 dnsmasq[2180]: no responses from nameserver '68.94.157.1'

Why not set your router (Untangle) to use a decent DNS service like OpenDNS? 208.67.222.222 and 208.67.220.220 instead of ATT's crummy DNS servers.
 
Why not set your router (Untangle) to use a decent DNS service like OpenDNS? 208.67.222.222 and 208.67.220.220 instead of ATT's crummy DNS servers.

I had actually tried that with google (8.8.8.8) and it worked, but caused my asterisk server to drop calls after 20 seconds. Just tried it again with your OpenDNS settings and everything is working perfectly, thanks!

After an hour, my router log is empty. Will see how it looks tomorrow.
 
Well the DNS issues are solved, the modem logs have been empty for a while (they usually fill up in a few minutes), but the original issue of foxpro not maintaining a solid connection like I did with DSL is still there. The only other setting to screw with in the modem is MTU, which is defaulted to 1500
 
Back
Top