Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Should I choose NTL?

  • 21-03-2006 3:18pm
    #1
    Chr1s
    Closed Accounts Posts: 17 ✭


    I am using eircom home plus, I want to change to NTL for the cheaper rent. So I wish somebody could give me some advices on that.

    if you are a NTL customer, would you please run "cmd" and paste the result of "ping www.yahoo.com -t" and the result of "ping www.sina.com.cn -t". press ctrl+c to stop pinging. I want to see if any packet has been lost.

    and can I use p2p download software such like BT and eMule? can I have a high-id? that means if I could get the port can be accessed by other people.


    thanks


Comments

  • #2
    DingDong
    Closed Accounts Posts: 1,438 ✭✭✭DingDong


    Here you go.You can use BT no problem and emule. I never could get a high ID on emule but I probably didnt have it setup right. Ntl does come with free access to newsgroups which is way better than most p2p programs.

    C:\>ping yahoo.com -t

    Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=176ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=174ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=178ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=175ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=195ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=176ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=176ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=197ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=187ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=191ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=179ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=194ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=207ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=171ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=175ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=174ms TTL=52
    Reply from 216.109.112.135: bytes=32 time=172ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=185ms TTL=51
    Reply from 216.109.112.135: bytes=32 time=173ms TTL=51

    Ping statistics for 216.109.112.135:
    Packets: Sent = 49, Received = 49, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 171ms, Maximum = 207ms, Average = 176ms


    C:\>ping www.sina.com.cn -t

    Pinging antares.sina.com.cn [218.30.13.38] with 32 bytes of data:

    Reply from 218.30.13.38: bytes=32 time=480ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=480ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=480ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=491ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=481ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=480ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=480ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=511ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=481ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=480ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=503ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=479ms TTL=42
    Reply from 218.30.13.38: bytes=32 time=478ms TTL=42

    Ping statistics for 218.30.13.38:
    Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 478ms, Maximum = 511ms, Average = 481ms


  • #3
    Diabolus
    Registered Users, Registered Users 2 Posts: 820 ✭✭✭Diabolus


    I got the same response times on NTL 3Mbit


  • #4
    capistrano
    Registered Users, Registered Users 2 Posts: 510 ✭✭✭capistrano


    I'm on the NTL 2Mb package. 
    $ ping yahoo.com

Pinging yahoo.com [66.94.234.13] with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=198ms TTL=52
Reply from 66.94.234.13: bytes=32 time=184ms TTL=52
Reply from 66.94.234.13: bytes=32 time=163ms TTL=52
Reply from 66.94.234.13: bytes=32 time=170ms TTL=51

Ping statistics for 66.94.234.13:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 163ms, Maximum = 198ms, Average = 178ms

    $ ping sina.com.cn

Pinging sina.com.cn [202.108.33.32] with 32 bytes of data:

Reply from 202.108.33.32: bytes=32 time=574ms TTL=232
Reply from 202.108.33.32: bytes=32 time=618ms TTL=232
Reply from 202.108.33.32: bytes=32 time=574ms TTL=232
Reply from 202.108.33.32: bytes=32 time=616ms TTL=232

Ping statistics for 202.108.33.32:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 574ms, Maximum = 618ms, Average = 595ms


  • #5
    DonkeyStyle \o/
    Closed Accounts Posts: 7,145 ✭✭✭DonkeyStyle \o/


    Could ye ping www.jolt.co.uk ?


  • #6
    Drapper
    Registered Users, Registered Users 2 Posts: 3,814 ✭✭✭Drapper


    Pinging www.jolt.co.uk with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=45ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=25ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=25ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=25ms TTL=50

    Ping statistics for 82.133.85.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 45ms, Average = 30ms


  • Advertisement
  • #7
    DonkeyStyle \o/
    Closed Accounts Posts: 7,145 ✭✭✭DonkeyStyle \o/


    mmm not bad... averaging 33ms on esatbt


  • #8
    Drapper
    Registered Users, Registered Users 2 Posts: 3,814 ✭✭✭Drapper


    DonkeyStyle \o/ wrote:
    mmm not bad... averaging 33ms on esatbt

    where are you living bud?


  • #9
    Scruff
    Registered Users, Registered Users 2 Posts: 4,225 ✭✭✭Scruff


    DingDong wrote:
    Ntl does come with free access to newsgroups which is way better than most p2p programs.

    thats very interesting, didnt know that. which ones?


  • #10
    DonkeyStyle \o/
    Closed Accounts Posts: 7,145 ✭✭✭DonkeyStyle \o/


    Drapper wrote:
    where are you living bud?
    bout 2 clicks from whitehall exhange
    bah, haven't even checked if they're doing it in my area

    Hey I was reading on their site that there's a 1GB per day transfer limit... which is a bit naff because some days I'd do 2gigs, other days I'd hardly do 200megs... is this actually enforced or still in effect? Seems a bit crap tbh.


  • #11
    paulm17781
    Closed Accounts Posts: 4,858 ✭✭✭paulm17781


    DonkeyStyle \o/ wrote:
    Hey I was reading on their site that there's a 1GB per day transfer limit... which is a bit naff because some days I'd do 2gigs, other days I'd hardly do 200megs... is this actually enforced or still in effect? Seems a bit crap tbh.

    I've only heard of it being enforced when people are downloading a huge amount and it is affecting their neighbours connection speeds.


  • Advertisement
  • #12
    zuma
    Closed Accounts Posts: 1,685 ✭✭✭zuma


    They basically dont want people downloading between 18:00 and 22:00...simple as that.

    Its due to the way cable connections operate through a single node or something and everyone suffers if one person goes torrent happy.

    If you start a "download" at 23:00 and turn off your "download" in the morning I would find it a very difficult prospect to harm the network as most people would be in bed.

    The US is blighted with this problem and speeds drop to half of usual during the peak hours so they view DSL as a slower but more stable...but also more expensive option!


Advertisement