12-31-2012 07:35:21 PM - edited 12-31-2012 07:37:23 PM
Hello intelligent people,
I've been with ATT for a very long time. My pre-Uverse setup was 2 phone lines coming into the home. One was used for voice, and the other was voice/data however rarely used for voice. Each with their own phone number.
Recently I upgraded from ATT DSL 6Mbps to Uverse 12Mbps with VOIP telephone. During this upgrade, I also terminated the old voice line.
(Mid Sept. - My self install date)
A very nice tech came to the door and told me that he needed access to the box on the side of the house. Apparently there was a problem within the line.
20 minutes later, he returned to the door and apologized that there was indeed a problem with the line, and he had to have a 'line man' come out and fix the problem.
He gave me his card, and told me to call him if I had any problems.
Late the following day, I call the tech to verify that it was okay for me to go ahead and install the gateway. I was told the 'line man' should have already been there, and to go ahead and connect everything.
I did as he instructed, and nothing worked. I waited until I returned from work the following day to see if things were turned on and they still were not working.
I called the tech once again and left a message.
I believed that my new service would be connected to the line that was already or previously the ATT DSL line. Out of curiosity, while waiting for the tech to call back, I plugged into the old voice line connection.
With in a few moments, things were up and I was very happy. The tech, however never returned my call. So I called him back and left a second message about what I had found.
I never received a return call. Guess if it's working, there's no need.
However, over the last 30 to 40 days, my speed has been running extremely slow by comparison to what it was in mid Sept.
I've gone through all the steps in the ATT Trouble Shoot and Resolve program on my computer, and I've not seen any improvement.
Using the Speedtest.net website returns speeds average to what I was getting before switching to Uverse.
Over the last day, I've been using the tracking of Testmy.net on Auto Test and got this average.
After reading tons of post here, I'm crossing my fingers that someone can tell me what to do next. OR more importantly, what to say to someone on the phone. I don't really get or understand the lingo, and to quite honest I get a bit forgetful when talking to folks on the phone. (guess I get nervous with this stuff - I just want it to work right)
As requested in many areas here, here are my UV Realtime v18.104.22.168 images.
Thanks in advance for any help you can share, in addition.. please excuse my long winded post.
P.S. Happy New Year
01-01-2013 07:46:40 AM
Your bitloading graph looks fairly normal, though I'll bet you have an AM radio station tower nearby (1380 Khz, maybe).
Since you'd only been collecting for 10 minutes when you snapped that error page, I'd suggest you use your line for a day, then snap a copy of the error and bitloading tab then just to be sure the line stays as clean as it looks here.
Are the speeds you're reporting for wired or wireless? If wireless, can you also get tests for wired for comparison.
Please be sure that you're not otherwise using your Internet connection when running speed tests if you want accurate numbers.
01-01-2013 12:25:57 PM
Thanks JefferMC for your reply.
I do indeed have an A.M. Radio station just 3 miles up the street from me. (1360Khz)
My entire setup is wired. I only use the wireless side for my android based phone, and some of the extra features associated with my blu-ray player. (not turned on during tests)
I'm confused why my speeds are so much slower, compared to the speeds I was getting back in Sept.
I'll wait a couple of days, and post additional copies of the above images for comparison.
01-04-2013 07:39:09 PM
Okay, it's been a couple days and I don't really see any changes to my previously posted images. And still, my internet speed is very slow.
So, a question about the bitloading graph.
On many of the one's posted here, the vertical side corrisponds with the users max download speed (or so it seems). If that is true, why does mine stop at 6, when it should be at 12?
Question about the screen below:
Under the "Power Level", Downstream = 21.8 but it's yellow in color. In addition, the upstream side is a negative number. Looks unusual compared to other's here, was just wondering what the "power level" is.
And finally, I saw someone do a traceroute with the 3-5 hop timed out. I have the same problem, no matter what destination I try. Could this have anything to do with my reduced speed?
Tracing route to disney.com [22.214.171.124]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 33 ms 51 ms 40 ms 75-53-176-3.lightspeed.mdstca.sbcglobal.net [75.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 31 ms 30 ms 31 ms 126.96.36.199
7 32 ms 31 ms 30 ms gar23.sffca.ip.att.net [188.8.131.52]
8 32 ms 29 ms 29 ms 184.108.40.206
9 31 ms 30 ms 38 ms vlan70.csw2.SanJose1.Level3.net [220.127.116.11]
10 31 ms 29 ms 30 ms ae-71-71.ebr1.SanJose1.Level3.net [18.104.22.168]
11 43 ms 42 ms 41 ms ae-2-2.ebr3.LosAngeles1.Level3.net [22.214.171.124]
12 39 ms 44 ms 50 ms ae-63-63.csw1.LosAngeles1.Level3.net [126.96.36.199
13 39 ms 39 ms 39 ms ae-61-61.ebr1.LosAngeles1.Level3.net [188.8.131.52
14 45 ms 49 ms 44 ms ae-1-4.bar1.LasVegas1.Level3.net [184.108.40.206]
15 44 ms 44 ms 44 ms 220.127.116.11
16 46 ms 45 ms 44 ms WALT-DISNEY.car1.LasVegas1.Level3.net [4.71.176.
17 * * * Request timed out.
18 44 ms 44 ms 44 ms 18.104.22.168
Thanks for your help.
01-05-2013 04:12:32 PM
Only enough bits to carry the assigned VDSL profile are allocated (plus some reserve bits with certain models of the 2Wire gateway). Because you are an Internet-only customer, your line profile has been selected at a lower value (13,200/1528) than people with IPTV service. The lower line profile allocates less bits, so your vertical axis shows fewer bits allocated.
The power levels are normal for your distance from the VRAD. The yellow downstream power level indicates that the power is lower than expected, but since there are no errors to speak of in your error table, this is not a concern.
Many AT&T nodes in the U-Verse portion of the network do not respond to ICMP echo (ping) packets. That is normal and has nothing to do with your speed.