• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

We got DSL!!!

I just got it a few weeks ago. Been having slowdowns almost every morning at 7:00AM and in the evening around 7:00PM:
  • C:\Windows>time
    Current time is 6:37:43.31p
    Enter new time:


    Pinging www.yahoo.akadns.net [216.109.125.66] with 1024 bytes of data:

    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=113ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=113ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=120ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=113ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Request timed out.
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=119ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=1751ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=113ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=136ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=113ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Request timed out.
    Reply from 216.109.125.66: bytes=1024 time=143ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=117ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=116ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=120ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=124ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=113ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=114ms TTL=48
    Reply from 216.109.125.66: bytes=1024 time=115ms TTL=48

    Ping statistics for 216.109.125.66:
    Packets: Sent = 100, Received = 65, Lost = 35 (35% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 113ms, Maximum = 1751ms, Average = 91ms
Is that crap normal for DSL? The last nitwit I talked to at tech support was saying I should clear my cache, history and make sure my resources aren't dropping off!
rolleye.gif


I hope you have a better connection than I do! Damn, I want a rebate on my monthly bill! :disgust:
 
Ornery,

Packet loss like that is router inspired not on your end. I'm guessing you are using one of the baby bells?
 
Originally posted by: MartyTheManiak
Welcome to 3 years ago!
Click to expand...

Roger that.

Also, packet loss like that is very common. I had SWB DSL; direct thru Ma Bell herself, no third party nothing. I routinely failed every packet loss test on DSLreports, and about 25% of the time, never connected to a URL on the first try.

Cable rocks. 😎
 
Originally posted by: MichaelD
Originally posted by: MartyTheManiak
Welcome to 3 years ago!
Click to expand...

Roger that.

Also, packet loss like that is very common. I had SWB DSL; direct thru Ma Bell herself, no third party nothing. I routinely failed every packet loss test on DSLreports, and about 25% of the time, never connected to a URL on the first try.

Cable rocks. 😎
Click to expand...

Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
 
Originally posted by: rahvin
Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
Click to expand...

[brag]

3 Mbit cable for $29.99 cdn/month (~$20.30 USD)

😀

[/brag]
 
Originally posted by: rahvin
Originally posted by: MichaelD
Originally posted by: MartyTheManiak
Welcome to 3 years ago!
Click to expand...

Roger that.

Also, packet loss like that is very common. I had SWB DSL; direct thru Ma Bell herself, no third party nothing. I routinely failed every packet loss test on DSLreports, and about 25% of the time, never connected to a URL on the first try.

Cable rocks. 😎
Click to expand...

Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
Click to expand...


How nice for you. I pay $39.99 to TimeWarner. I have 2.0mbps/384kbps speed. And I see every bit of it.
 
Originally posted by: MichaelD
Originally posted by: rahvin
Originally posted by: MichaelD
Originally posted by: MartyTheManiak
Welcome to 3 years ago!
Click to expand...

Roger that.

Also, packet loss like that is very common. I had SWB DSL; direct thru Ma Bell herself, no third party nothing. I routinely failed every packet loss test on DSLreports, and about 25% of the time, never connected to a URL on the first try.

Cable rocks. 😎
Click to expand...

Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
Click to expand...


How nice for you. I pay $39.99 to TimeWarner. I have 2.0mbps/384kbps speed. And I see every bit of it.
Click to expand...

You also are prohibited from running server services, a VPN connection and being that they are a content provider there is the future possibility of them blocking access. I also wouldn't be supprised if your pings vary greatly along with strong periods of packet loss but I could be wrong as that may only be a comcast problem.

 
I'm shocked no one has commented on the fact that another lucky soul has been liberated from the evil clutches of AOL... :Q
 
Originally posted by: silverpig
Originally posted by: rahvin
Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
Click to expand...

[brag]

3 Mbit cable for $29.99 cdn/month (~$20.30 USD)

😀

[/brag]
Click to expand...

This is an outrage! 😀

I have to pay US $58 for Comcast Cable
 
Originally posted by: rahvin
Originally posted by: MichaelD
Originally posted by: MartyTheManiak
Welcome to 3 years ago!
Click to expand...

Roger that.

Also, packet loss like that is very common. I had SWB DSL; direct thru Ma Bell herself, no third party nothing. I routinely failed every packet loss test on DSLreports, and about 25% of the time, never connected to a URL on the first try.

Cable rocks. 😎
Click to expand...

Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
Click to expand...

Umm I had no problem with Bellsouth DSL. In the year that I had it, service only went down twice. Pings ranged from 30 to 60 MS and I received a discount on the price for having their local phone service. Why would the DSL through the Telco be any worse than a 3rd party provider? It uses the same lines and most of the time the same equipment.
 
Originally posted by: Millennium
Originally posted by: rahvin
Originally posted by: MichaelD
Originally posted by: MartyTheManiak
Welcome to 3 years ago!
Click to expand...

Roger that.

Also, packet loss like that is very common. I had SWB DSL; direct thru Ma Bell herself, no third party nothing. I routinely failed every packet loss test on DSLreports, and about 25% of the time, never connected to a URL on the first try.

Cable rocks. 😎
Click to expand...

Your mistake of course was buying from the telco. Through covad I have 0% packet loss, a 45ms ping to nearly anywhere on the net and a 1.5mbit download connection for $49.99 a month (taxes and surcharges included in that price)
Click to expand...

Umm I had no problem with Bellsouth DSL. In the year that I had it, service only went down twice. Pings ranged from 30 to 60 MS and I received a discount on the price for have their local phone service. Why would the DSL through the Telco be any worse than a 3rd party provider? It uses the same lines and most of the time the same equipment.
Click to expand...

Got that right. I use baby bell DSL and I have never had any problems. As a matter of fact I haven't had any failures to connect, ridiculous numbers of dropeed packets, or anything less than 95% of full advertised speed 🙂.
 
We pay 46$ I think for 1.544/256.(~196k/sec and 32k/sec, respectivly). I get pretty good pings.

H:\>tracert forums.anandtech.com

Tracing route to forums.anandtech.com [168.143.107.163]
over a maximum of 30 hops:

1 10 ms <10 ms 10 ms 10.140.0.1
2 10 ms <10 ms 11 ms 12.244.84.1
3 10 ms 10 ms 10 ms 12.244.72.42
4 10 ms 20 ms 10 ms gbr1-p70.st6wa.ip.att.net [12.123.44.57]
5 10 ms 10 ms 20 ms gbr3-p70.st6wa.ip.att.net [12.122.5.157]
6 * * * Request timed out. <--- this router's firewall must not allow pings
7 20 ms 20 ms 20 ms ggr1-p3100.sffca.ip.att.net [12.122.11.230]
8 30 ms 30 ms 30 ms p4-6-0-0.r00.plalca01.us.bb.verio.net [129.250.9.29]
9 30 ms 30 ms 30 ms p16-0-1-0.r20.plalca01.us.bb.verio.net [129.250.3.78]
10 80 ms 80 ms 80 ms p16-5-0-0.r02.mclnva02.us.bb.verio.net [129.250.2.193]
11 90 ms 91 ms 90 ms p16-7-0-0.r01.mclnva02.us.bb.verio.net [129.250.5.11]
12 80 ms 80 ms 91 ms p16-0-1-0.r21.asbnva01.us.bb.verio.net [129.250.2.181]
13 80 ms 90 ms 90 ms p16-4-0-0.r02.asbnva01.us.bb.verio.net [129.250.2.63]
14 90 ms 90 ms 90 ms ge-1-1.a00.asbnva01.us.ra.verio.net [129.250.26.97]
15 90 ms 90 ms 90 ms ge49.r1.vadc1.eicomm.net [168.143.105.78]
16 80 ms 90 ms 80 ms 168.143.107.163

Trace complete.
 
What specifically should I ask the next tech person I talk to? Some of them are sharp, and I can even ask to be transferred to the specialist team. Is it a known fact that DSL, especially from SBC, can be sporadic? Can I ask to be connected to a better server or something?

If my connection goes to hell, then I wait a few minutes and it picks back up to full speed, without me touching a thing, does that prove it's all good on my end? I'd hate to make a pest of myself, only to find that I have a bogus configuration here! Is there anything between them and myself that would leave neither of us at fault? SBC is also my phone service, so they're responsible for the line, no?
 
My SBC Yahoo! DSL 1.5mb/256mb was turned on last Friday. Using the Speed Test, I avg 763k. I formatted my main HD and reinstalled XP Pro and after that I now get a nice 1.173mb/245k on every test. I also removed the DSL Filter on that line and it might have seemed to help. Also The Phone companys switch is just a couple blocks from my house so thats kinda nice 😉
 
Originally posted by: Ornery
I just got it a few weeks ago. Been having slowdowns almost every morning at 7:00AM and in the evening around 7:00PM:
  • C:\Windows>time
    Current time is 6:37:43.31p
    Enter new time:


    Pinging www.yahoo.akadns.net [216.109.125.66] with 1024 bytes of data:

    ...


    Ping statistics for 216.109.125.66:
    Packets: Sent = 100, Received = 65, Lost = 35 (35% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 113ms, Maximum = 1751ms, Average = 91ms
Is that crap normal for DSL? The last nitwit I talked to at tech support was saying I should clear my cache, history and make sure my resources aren't dropping off!
rolleye.gif


I hope you have a better connection than I do! Damn, I want a rebate on my monthly bill! :disgust:
Click to expand...

Definatly not normal. I have DSL and always have an on connection. I have not lost my connection to AOL IM for over 2 days.
 
I just want to know how to approach this when I call next time. I can just picture them on the other end, rolling their eyes, knowing that I'm getting as good a service as I'm ever going to get. I'm thinking they aren't allowed to admit there are problems with it.

I'm 13,880' from the CO. Just wondering why it's blazing along nicely for several hours, then it takes a sh|t for a 15 or 20 minutes, then it's blazing along again with no changes at all on my part. It stays connected, just slug, slow. I've had occasions where I tried to ping them and got the response, "Unknown host www.yahoo.com". Powering off their ADSL modem for a few minutes, then powering back on does the trick. That's mentioned in their help page. Most of the time though, it just slows to a crawl for no apparent reason.

One tech gal, who seemed pretty with it, asked if there were any TV or radio stations nearby. She said they could be doing massive up or downloads, causing my trouble. I thought that only effected cable?

Would switching to a different provider do the trick? It would suck to go through all the bitching, canceling and switching to another one, only to find it all working the same sporadic way!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top