fuckin internet connection has been slow as shit the past two days. i called att and of course its nothing on their end. when i ran the little test i am receiving 1538 kbps or some shit. anywho they had me delete my cookies and temporary internet files and its still running slow as hell. anyone know of anything else i can do to get it back to the speed it was a couple of days ago?
fuckin internet connection has been slow as shit the past two days. i called att and of course its nothing on their end. when i ran the little test i am receiving 1538 kbps or some shit. anywho they had me delete my cookies and temporary internet files and its still running slow as hell. anyone know of anything else i can do to get it back to the speed it was a couple of days ago?
i tried all of that. i can't even get my AOL email to pull up because it times out. same with my online banking. that link i tried to download im getting like 3kbs or whatever a second. i have the 1.5mb service.
well thats what i told the guy. my modem is getting the 1.5mb thats im supposed to receive but my computer takes forever to connect to anything. would i still be getting the strong signal and it not be fast? the guy on the phone was saying it has to be my computer however i haven't downloaded anything and my computer was fine a few days ago.
I was on my sons computer this evening and it was slow as hell.... when I complained about it, he said it always like that with IE.... thats why he installed Firefox.... when I opened FF, it was fast as hell... I haven't had time to figure out why there is so much difference but its something to consider...
i might try that... thing is though i dont know how ill get firefox on the computer. justs to download that program in this thread it took me about 20 min and it wasn't even a mb. i am going to see if its fixed sunday and if not im going to call att on monday and tell them either come to my house and fix it for free or cancel my service. im not on a contract so ill just have to find someone else i guess.
i might try that... thing is though i dont know how ill get firefox on the computer. justs to download that program in this thread it took me about 20 min and it wasn't even a mb. i am going to see if its fixed sunday and if not im going to call att on monday and tell them either come to my house and fix it for free or cancel my service. im not on a contract so ill just have to find someone else i guess.
yeah when i get there sunday if its still f'ed up ill tell them that. the other day though they told me if a tech comes out then i get charged, but i dont see how i can get charged if its their fault.... thats why im gunna tell them to cancel my contract if they say that.
If they do send a tech out they will test the condition of your cable pair and sync up with the dslam from your NID or Customer interface. If everything tests good then they will you charge you. Have you tried bypassing your router and hooking up directly to your modem? I'd double check all your stuff before you have them come out and charge you $100 for them to tell you that your gear is jacked, have a nice day....
Just my $.02 of course.
It's probably the plastic in the RJ11 connector. I've seen that before, it becomes condusive (sp?) and causes reflux problems with the built in bit bucket in the line modem.
alright guys. i switched out my modem with my parents old one and it seems like websites are downloading quicker but im still not able to download or watch youtube videos very well. is it looking like att's fault now? i really dont wanna call and them send someone out and everything be working fine.
alright guys. i switched out my modem with my parents old one and it seems like websites are downloading quicker but im still not able to download or watch youtube videos very well. is it looking like att's fault now? i really dont wanna call and them send someone out and everything be working fine.
Reply from 4.2.2.1: bytes=32 time=12ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=13ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Request timed out.
Reply from 4.2.2.1: bytes=32 time=13ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=12ms TTL=56
Reply from 4.2.2.1: bytes=32 time=12ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=13ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Ping statistics for 4.2.2.1:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 13ms
Reply from 4.2.2.1: bytes=32 time=12ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=13ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Request timed out.
Reply from 4.2.2.1: bytes=32 time=13ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=12ms TTL=56
Reply from 4.2.2.1: bytes=32 time=12ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=13ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Reply from 4.2.2.1: bytes=32 time=14ms TTL=56
Reply from 4.2.2.1: bytes=32 time=15ms TTL=56
Ping statistics for 4.2.2.1:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 13ms
ill do that when i get home. i connect directly to the modem. im going to try and get a virus scanner and see if anything pops up. i tried doing a system restore and that didn't fix anything either.
Virus scanner is always a good idea. You should not see any packet loss. It will slow your connection down considerably. Post up the results when you get home!
Do problems always start with inclimate weather? Rain, Thunderstorms? Do you have filters on all your phones? Do you have a monitored alarm system? The wiring in your house could be going bad. If you have a long enough line cord hook it up from your NID (customer interface) directly to the modem and see if that solves your problem. If it does you either have a filtering issue or the wiring inside your house is bad....
Yes I used to work for one of the phone companies....
ok if you call in a tkt and we come out and find there is no trouble at the SNI/NID the trouble is inside you will be billed. If the trouble is bad modem and your cool with the tech they may swap it for you for free instead of charging you for a new modem if the warrenty is out on it.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
DFW Mustang Forums
5.8M posts
29.7K members
Since 2000
A forum community dedicated to Dallas/Fort Worth area Mustang owners and enthusiasts. Come join the discussion about performance, modifications, classifieds, troubleshooting, maintenance, and more!