mers2
Premium,MVM
join:2004-03-20
USA
clubs: | reply to David
Re: We got some news!-05/06/09 Slow Web Page Loading
This fix has been promised for a long, long time. It would be nice if it actually got fixed. |
|
coldrider
@sbcglobal.net | reply to David
I'm still waiting for the fix also... How much longer should I have to pay for service not being provide..... |
|
limpy
@sbcglobal.net | reply to David
Seeing that ATT is in the middle of their Phase2 upgrade for Uverse TV, I'd be surprised if this issue gets fixed anytime soon.  |
|
kinneyr2
join:2002-01-24
Carlsbad, CA | reply to David
Yeah frustrating. I switch back and forth from OpenDNS just to see if the fix has been implemented. |
|
wassy
join:2003-09-05
Fort Lauderdale, FL
| reply to David
I'm waiting too... but I may have a different issue altogether. OpenDNS or not, I notice NO difference.
my issue is usually in Safari (mac 10.5.7) loading a series of bookmark pages, say 10 pages.. the spinning wheel keeps going for quite a while. sometimes it's faster than others..
when opening home page, cnn.com, it's blazing ONLY if Safari already opened. when opening safari for 1st time since reboot, there is a delay, as with all programs accessing the web for whatever reason..
this probably should have been posted in the general section, so I apologize in advance. |
|
wileyhodges
Premium
join:2007-11-11
San Mateo, CA
| reply to David
I'm a new U-verse customer in the past couple of weeks, but I noticed the same problem with slow page loading, as well as the solution using OpenDNS.
I have a 2Wire 2800 HGV-B gateway, running system version 5.29.105.94.
Setting the local DNS servers to OpenDNS on my Macs solves the issue, but I look forward to a system fix. |
|
vcuares
join:2004-09-12
Minneapolis, MN | reply to David
Any updates yet, I thought it was June, I'm frustrated with AT&T. My openDNS workaround works on my Macbook Air and Mac Pro. However, openDNS screws up my Mac Pro and I can't see other computers in my LAN. |
|
digitaltrade
join:2004-09-07
Rowlett, TX | reply to David
Its amazing that something that affects so many users is being essentially ignored. I was trying to be patient but then June passed by without any solution. Any updates? |
|
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs:
 ·DIRECTV
 ·magicjack.com
 ·AT&T Midwest
1 edit | said by digitaltrade  :Its amazing that something that affects so many users is being essentially ignored. I was trying to be patient but then June passed by without any solution. Any updates? Got one today, It's a setback.
The code failed the test. When they implemented it, it caused the RG to reboot every 1 to 3 days. So at that point it's back to the drawing board. Now they are looking at addressing this with maybe a firmware revision. No ETA on that one as of yet.
Right now the quick fix for the problem seems to be to hard code the DNS in the PC's, routers and such.
For at&t's anycast DNS the IP's are:
68.94.156.1 and 68.94.157.1.
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!
|
|
kakeh
@sbcglobal.net | reply to David
I tried setting the DNS to those but not luck for me. I just started getting this problem here in Indiana just last saturday. hopefully they fix it soon. I am paying for the "high speed internet" of course haha |
|
limpy
@sbcglobal.net
| reply to David
ATT and 2Wire need to get of of their collective a$$es and start treating this issue seriously. This problem seems to be getting worse as more people are beginning to discuss this on different forums. I personally have been watching my page loading getting slower and slower and nothing has changed on my connection stats. Matter of fact, I got better performance from my old ATT DSL than I'm getting from Uverse, hard coding DNS has little or no effect.  |
|
mhetterm
join:2001-11-01
Altadena, CA | And, why did this post get un-stickied? It's certainly not resolved ... |
|
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs: | reply to David
Well it's not that they are not taking it seriously, the fact that it was reproduceable and they tried one solution and failed already.
I think the next fix they have in mind is going to fix the problem permanently (a firmware revision). |
|
fleish
join:2009-06-19
San Francisco, CA
| I've been fighting with AT&T support on this issue off and on since we got Uverse ~4 months ago. And we're a business account which didn't seem to help much. After 157 minutes on the phone with support yesterday, I was ready to throw in the towel. Can't believe I missed these threads until now.
An easy solution to implement in the faulty 2wire boxes would be to allow them to set alternate or secondary dns servers to be pushed to the dhcp clients. Most all major home network boxes provide this. Our 2wire box (3800HGV-B) seems to know about the 2 sbcglobal dns server ip's (68.94.156.1, 68.94.156.2) ... but doesn't push them to the clients. |
|
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs: | I thought the other DNS was 68.94.157.1 |
|
limpy
@sbcglobal.net
| reply to David
The thing is, no one knows when this "permanent fix" will be implemented, 1 month, 3 months, 6 months or if will even work. I'm on the 6/1 tier and some pages load like it was dial up! As it stands now, their high speed internet is not all that high speed and if they don't resolve this issue soon they're going to start losing customers. |
|
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs: | and that's with the DNS in the pc? |
|
MyDogHsFleas
Premium
join:2007-08-15
Austin, TX | reply to limpy
said by limpy :
I'm on the 6/1 tier and some pages load like it was dial up! But... the fix is ridiculously easy... simply put the DNS addresses into the TCP/IP definition on the PC. |
|
dave006
join:1999-12-26
Boca Raton, FL
 ·AT&T U-Verse
| reply to David
said by David :I thought the other DNS was 68.94.157.1 Yes the suggested pair is 68.94.156.1 and 68.94.157.1 as they sit on different network segments. However, 68.94.156.2 will answer as dnsr3.
Dave |
|
mhetterm
join:2001-11-01
Altadena, CA | Still wondering why this thread was un-stickied ... |
|
