dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
share rss forum feed


mlerner
Premium
join:2000-11-25
Nepean, ON
kudos:5
reply to MrMazda86

Re: [DSL] Hell Telecom (formerly Bell) + AOHell

If you can pull the line stats, post them here and we can check but 51-248 ms could mean her line is on interleave, maybe line quality or distance issues but interleave does help maintain a stable connection at the expense of latency. Then again it could also mean the server you're pinging has QoS applied with lower priority for ICMP response.

As far as diagnostics, Bell could probably fix up line quality but it won't make the login work as whatever endpoint it is Bell or AOL, it ain't taking that login on their end.

MrMazda86

join:2013-01-29
Kitchener, ON

1 edit
Here is a direct copy & paste of the command prompt when I ran the test. The result is even more frightening today. My next step is going to be to switch her out for the 2Wire 2701HG-G modem so that I can take a look at the actual physical line information and see if it will get her better speeds and/or get her a better ping response. The following was kinda frightening:

quote:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\eh>ping -n 100 10.3.212.1

Pinging 10.3.212.1 with 32 bytes of data:
Reply from 10.3.212.1: bytes=32 time=48ms TTL=248
Reply from 10.3.212.1: bytes=32 time=46ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=54ms TTL=248
Reply from 10.3.212.1: bytes=32 time=55ms TTL=248
Reply from 10.3.212.1: bytes=32 time=49ms TTL=248
Reply from 10.3.212.1: bytes=32 time=83ms TTL=248
Reply from 10.3.212.1: bytes=32 time=51ms TTL=248
Reply from 10.3.212.1: bytes=32 time=45ms TTL=248
Reply from 10.3.212.1: bytes=32 time=42ms TTL=248
Reply from 10.3.212.1: bytes=32 time=43ms TTL=248
Reply from 10.3.212.1: bytes=32 time=50ms TTL=248
Reply from 10.3.212.1: bytes=32 time=71ms TTL=248
Reply from 10.3.212.1: bytes=32 time=192ms TTL=248
Reply from 10.3.212.1: bytes=32 time=80ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=49ms TTL=248
Reply from 10.3.212.1: bytes=32 time=44ms TTL=248
Reply from 10.3.212.1: bytes=32 time=45ms TTL=248
Reply from 10.3.212.1: bytes=32 time=86ms TTL=248
Reply from 10.3.212.1: bytes=32 time=237ms TTL=248
Reply from 10.3.212.1: bytes=32 time=117ms TTL=248
Reply from 10.3.212.1: bytes=32 time=120ms TTL=248
Reply from 10.3.212.1: bytes=32 time=285ms TTL=248
Reply from 10.3.212.1: bytes=32 time=250ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=42ms TTL=248
Reply from 10.3.212.1: bytes=32 time=116ms TTL=248
Reply from 10.3.212.1: bytes=32 time=117ms TTL=248
Reply from 10.3.212.1: bytes=32 time=117ms TTL=248
Reply from 10.3.212.1: bytes=32 time=52ms TTL=248
Reply from 10.3.212.1: bytes=32 time=57ms TTL=248
Reply from 10.3.212.1: bytes=32 time=122ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=423ms TTL=248
Reply from 10.3.212.1: bytes=32 time=245ms TTL=248
Reply from 10.3.212.1: bytes=32 time=118ms TTL=248
Reply from 10.3.212.1: bytes=32 time=42ms TTL=248
Reply from 10.3.212.1: bytes=32 time=69ms TTL=248
Reply from 10.3.212.1: bytes=32 time=57ms TTL=248
Reply from 10.3.212.1: bytes=32 time=43ms TTL=248
Reply from 10.3.212.1: bytes=32 time=120ms TTL=248
Reply from 10.3.212.1: bytes=32 time=117ms TTL=248
Reply from 10.3.212.1: bytes=32 time=118ms TTL=248
Reply from 10.3.212.1: bytes=32 time=40ms TTL=248
Reply from 10.3.212.1: bytes=32 time=77ms TTL=248
Reply from 10.3.212.1: bytes=32 time=75ms TTL=248
Reply from 10.3.212.1: bytes=32 time=211ms TTL=248
Reply from 10.3.212.1: bytes=32 time=118ms TTL=248
Reply from 10.3.212.1: bytes=32 time=52ms TTL=248
Reply from 10.3.212.1: bytes=32 time=133ms TTL=248
Reply from 10.3.212.1: bytes=32 time=139ms TTL=248
Reply from 10.3.212.1: bytes=32 time=45ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=57ms TTL=248
Reply from 10.3.212.1: bytes=32 time=774ms TTL=248
Reply from 10.3.212.1: bytes=32 time=306ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=502ms TTL=248
Reply from 10.3.212.1: bytes=32 time=138ms TTL=248
Reply from 10.3.212.1: bytes=32 time=119ms TTL=248
Reply from 10.3.212.1: bytes=32 time=119ms TTL=248
Reply from 10.3.212.1: bytes=32 time=152ms TTL=248
Reply from 10.3.212.1: bytes=32 time=48ms TTL=248
Reply from 10.3.212.1: bytes=32 time=59ms TTL=248
Reply from 10.3.212.1: bytes=32 time=59ms TTL=248
Reply from 10.3.212.1: bytes=32 time=47ms TTL=248
Reply from 10.3.212.1: bytes=32 time=121ms TTL=248
Reply from 10.3.212.1: bytes=32 time=48ms TTL=248
Reply from 10.3.212.1: bytes=32 time=45ms TTL=248
Reply from 10.3.212.1: bytes=32 time=122ms TTL=248
Reply from 10.3.212.1: bytes=32 time=215ms TTL=248
Reply from 10.3.212.1: bytes=32 time=119ms TTL=248
Reply from 10.3.212.1: bytes=32 time=131ms TTL=248
Reply from 10.3.212.1: bytes=32 time=59ms TTL=248
Reply from 10.3.212.1: bytes=32 time=210ms TTL=248
Reply from 10.3.212.1: bytes=32 time=284ms TTL=248
Reply from 10.3.212.1: bytes=32 time=48ms TTL=248
Reply from 10.3.212.1: bytes=32 time=46ms TTL=248
Reply from 10.3.212.1: bytes=32 time=49ms TTL=248
Reply from 10.3.212.1: bytes=32 time=64ms TTL=248
Reply from 10.3.212.1: bytes=32 time=85ms TTL=248
Reply from 10.3.212.1: bytes=32 time=128ms TTL=248
Reply from 10.3.212.1: bytes=32 time=111ms TTL=248
Reply from 10.3.212.1: bytes=32 time=60ms TTL=248
Reply from 10.3.212.1: bytes=32 time=66ms TTL=248
Reply from 10.3.212.1: bytes=32 time=71ms TTL=248
Reply from 10.3.212.1: bytes=32 time=54ms TTL=248
Reply from 10.3.212.1: bytes=32 time=48ms TTL=248
Reply from 10.3.212.1: bytes=32 time=63ms TTL=248
Reply from 10.3.212.1: bytes=32 time=77ms TTL=248
Reply from 10.3.212.1: bytes=32 time=70ms TTL=248
Reply from 10.3.212.1: bytes=32 time=57ms TTL=248
Reply from 10.3.212.1: bytes=32 time=57ms TTL=248
Reply from 10.3.212.1: bytes=32 time=131ms TTL=248
Reply from 10.3.212.1: bytes=32 time=48ms TTL=248
Reply from 10.3.212.1: bytes=32 time=65ms TTL=248

Ping statistics for 10.3.212.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 774ms, Average = 105ms

C:\Users\eh>

Any ideas on what this means or where I should be thinking of taking things from this point? I already know that I'm going to have to get AOHell involved and rattle some cages there because she's currently having to use my TSI login to be able to do such things as send her rent money to her landlord.

@TSI: In a situation like this where this kind of issue exists (or even in general for that matter), is there a policy against using a TSI login from a non TSI connection? Also, would using a TSI login on a non TSI connection constitute a terms of service violation or anything else along those lines that wouldn't be desirable?


TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33
Pinging a BAS & receiving these types of stats would indicate congestion at the BAS. This would require the ISP to open a slow speed ticket & see if Bell would return back with a Pattern issue.

This is not a normal response rate from the BAS.

MrMazda86

join:2013-01-29
Kitchener, ON
Thank you... I'm on it