ATT DSL Speed Test - - - a trick!
glacierp
the speed tester provided by ATT here - http://helpme.att.net/dsl/speedtest/
- It showed my speed was even way below the dial-up speed. Normally,
a button was enabled that will allow me to submit the network results
to ATT Support so that they can fix the problem. Well, yesterday ATT
disabled the button.. Today, I tried to do the dsl speed test
again.... it got worse.... everytime I go to the site, and press the
DSL Test Speed, my browser would automatically close. I think ATT has
been feeling the heat from the customers like me who are not happy
with the DSL service. They must have heard enough, and don't want to
listen to our complaints anymore.... Well, goodbye ATT as this is the
last straw for me to switch to another High-Speed Internet provider.
Larry
news:20ff3686-9121-4322...@b5g2000pri.googlegroups.com:
I guess you're at work at Oracle sending this. That's where your IP sent
me, anyways from your Giganews header....(c;
Have you done any reverse traceroutes back to your ATT box to see if it's
broken upstream somewhere? Usenetserver has a real fast one I'm only 9ms
from, here. Give it a go and see if the ping times don't pop up in one of
your links between them and you. That might help in your tech calls if you
will save the trace and email it to them.
http://monitor.usenetserver.com/cgi-bin/trace.pl
that will automatically trace right back to you. If you're using a router
or firewall to prevent answering pings, of course, it won't see you on the
end of the string and keep calling. If you shut down your firewall and
plug the computer straight into the modem without any router isolating that
box from the net, you can read your own ping response time and see if
you're system is missing any packets and is the cause of the problem.
My cable company got awful slow all of a sudden. But, before calling them
and them blaming my stuff for being slow, I had a stored "normal" reverse
trace from Usenetserver, then did a new trace for comparison. The idiot
DNS had routed everyone in Charleston, SC, through TWO USER ADDRESSES IN
FLORIDA! I was amazed I had any bandwidth at all! As soon as the talking
head came online to send out a tech, I stopped him from reading the script
and told him I'd email him the trace showing what's wrong. I even got a
thank you call from the supervisor of the operations department, saving him
lots of time. We're back to normal now, with the boxes lashed to the desk
to keep them from hopping around under the onslaught of data pouring in
from Usenetserver's server farm...(c;
Don't forget to save and print the trace you get so "they" can see it, too.
Might help with your problem...might not, but worth a try.