NTL Broadband over phone line? Is it possible?

Jedi_IRL

Hi,

I'm really struggling to get decent pings with Eircom at the moment. I've tried 1meg, 3meg and 7 meg and all of them are very poor ping wise to UK. This is being caused by 30ms delay to from my router to the first eircom switch. I've tried everything to lower this, including gettting there tech support to set to low interleaving.

There technical support have said there is nothing more they can do to improve it the latency problems.

My questions is do NTL supply Broadband over phone line or is it just cable?

I heard that the pings with NTL are almost half those of eircom at the moment.

Look forward to hearing from you.

Thanks

dub45

Jedi_IRL wrote: »

Hi,



My questions is do NTL supply Broadband over phone line or is it just cable?
Look forward to hearing from you.

Thanks

Only cable.

Jedi_IRL

Thanks

CutzEr

Perhaps buy a new router? I would have done that in the first place :P

I don't see how Eircom could help you anyways, if it's the fault of your router.

PogMoThoin

CutzEr wrote: »

Perhaps buy a new router? I would have done that in the first place :P

I don't see how Eircom could help you anyways, if it's the fault of your router.

How? A new router won't solve anything, its Eircoms network at fault

dub45

PogMoThoin wrote: »

How? A new router won't solve anything, its Eircoms network at fault

How is the network at fault? No isp gives guarantees about ping levels and the op has given no information at all about line stats or the internal set up.

PogMoThoin

dub45 wrote: »

How is the network at fault? No isp gives guarantees about ping levels and the op has given no information at all about line stats or the internal set up.

What I mean is that telling him to buy a new router is definitely not going to solve the op's problems. There was meant to be an if in that last post but I had one eye on the aftermatch analysis

watty

30ms from OPs router to an eircom switch someplace (that probably deprioritised ICMP anyway).

OP
do a ping then tracert to heanet. gives a better idea. Internal network switches don't respond well to pings. You can see this in the tracert, where the overall ping to heanet is only 18ms but ping to a switch is 30ms

C:\Documents and Settings\watty>ping  www.heanet.ie

Pinging samhain.heanet.ie [193.1.219.57] with 32 bytes of data:

Reply from 193.1.219.57: bytes=32 time=18ms TTL=60
Reply from 193.1.219.57: bytes=32 time=16ms TTL=60
Reply from 193.1.219.57: bytes=32 time=18ms TTL=60
Reply from 193.1.219.57: bytes=32 time=20ms TTL=60

Ping statistics for 193.1.219.57:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 20ms, Average = 18ms

C:\Documents and Settings\Watty>tracert [url]www.heanet.ie[/url]

Tracing route to samhain.heanet.ie [193.1.219.57]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    11 ms    11 ms    11 ms  83.147.171.1
  3    18 ms    18 ms    20 ms  gi-5-1.dub-deg-br1.net.digiweb.ie [83.147.162.22]
  4    18 ms    18 ms    15 ms  te0-0-0-1-cr2-cwt.hea.net [193.242.111.16]
  5    25 ms    33 ms    17 ms  te5-1-blanch-sr1.services.hea.net [193.1.236.2]

  6    15 ms    30 ms    17 ms  samhain.heanet.ie [193.1.219.57]

Trace complete.

Of course Mobile or Ripwave is 100ms to 2000ms and Satellite 790ms.

Jedi_IRL

Here are the pings I get when i try www.heanet.ie.

Pinging samhain.heanet.ie [193.1.219.57] with 32 bytes of data:
Reply from 193.1.219.57: bytes=32 time=28ms TTL=58
Reply from 193.1.219.57: bytes=32 time=28ms TTL=58
Reply from 193.1.219.57: bytes=32 time=28ms TTL=58
Reply from 193.1.219.57: bytes=32 time=28ms TTL=58
Ping statistics for 193.1.219.57:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 28ms, Average = 28ms

C:\Documents and Settings\Tom & Elaine>tracert [URL="http://www.heanet.ie/"]www.heanet.ie[/URL]
Tracing route to samhain.heanet.ie [193.1.219.57]
over a maximum of 30 hops:
  1     1 ms     1 ms     1 ms  192.168.1.254
  2    26 ms    38 ms     *     b-ras1.cld.dublin.eircom.net [159.134.155.22]
  3    27 ms    28 ms    27 ms  159.134.127.77
  4    26 ms    27 ms    26 ms  86.43.244.153
  5    28 ms    31 ms    27 ms  te0-0-0-1-cr2-cwt.hea.net [193.242.111.16]
  6    27 ms    28 ms    27 ms  te5-1-blanch-sr1.services.hea.net [193.1.236.2]
  7    28 ms    30 ms    28 ms  samhain.heanet.ie [193.1.219.57]
Trace complete.

PogMoThoin

Not a whole lot wrong with 28ms, I game online and my pings higher, 28ms to Heanet is acceptable IMO

Pinging samhain.heanet.ie [193.1.219.57] with 32 bytes of data:
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=32ms TTL=56
Reply from 193.1.219.57: bytes=32 time=33ms TTL=56

Ping statistics for 193.1.219.57:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 32ms

Where are the servers You play on hosted? Have You ran a treceroute to these servers? Can You post some ping times

Have You checked Your line stats? Can these be improved by unplugging other devices in Your house? Post Your stats by logging into Your router on 192.168.1.254, click expert mode and they'll be under dsl statistics

watty

Yes 28ms to heanet is excellent. You can't really tell latenency at all pinging an internal network router/switch as I explained before. They even especially design them now to respond slowly to pings to avoid DDOS attacks.

Nothing wrong with your connection. Many people on DSL have higher pings, especially the ADSL 7.6Mbps package!