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

digiweb all over the place

  • 13-05-2007 11:52am
    #1
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭


    hi all,had lots of probs with them b4 but has been great 4 a couple of months now.
    last few days at any time of the day i'm getting lag spikes to any site/game server.
    look at these plz and does any1 have any ideas on what it could be.
    just formatted drive so not virus/spyware.
    thx in advance

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Owner>ping -n 50 yahoo.co.uk

    Pinging yahoo.co.uk [217.12.6.29] with 32 bytes of data:

    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=22ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=30ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=45ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=44ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=43ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=28ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=22ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=43ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=32ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=22ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=105ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=45ms TTL=250
    Request timed out.
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=73ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=34ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=44ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=53ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=45ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=92ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=47ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=44ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=34ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=33ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=32ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=20ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=34ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=35ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=53ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=35ms TTL=250
    Request timed out.

    Ping statistics for 217.12.6.29:
    Packets: Sent = 50, Received = 41, Lost = 9 (18% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 105ms, Average = 36ms

    C:\Documents and Settings\Owner>ping -n 50 yahoo.co.uk

    Pinging yahoo.co.uk [217.12.6.29] with 32 bytes of data:

    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=28ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=27ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=26ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=61ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=57ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=27ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=54ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=51ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=1923ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=22ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=33ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=26ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=26ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=22ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=28ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=26ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=26ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=1230ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=1023ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=46ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=43ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=29ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=21ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=46ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=37ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=3772ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=24ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=23ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=85ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=26ms TTL=250
    Reply from 217.12.6.29: bytes=32 time=27ms TTL=250
    Request timed out.
    Reply from 217.12.6.29: bytes=32 time=25ms TTL=250

    Ping statistics for 217.12.6.29:
    Packets: Sent = 50, Received = 44, Lost = 6 (12% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 3772ms, Average = 209ms


Comments

  • #2
    Sponge Bob
    Banned (with Prison Access) Posts: 25,234 ✭✭✭✭Sponge Bob


    metro or adsl ?

    have you dsl line stats ?

    if metro are you on 3rock ?


  • #3
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    sorry should have said.on metro 3meg and presume its 3rock.
    even web pages are slow/timing out loading now.
    ty


  • #4
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    now its worse.it is losing connection totally now.have 2 reset modem and put in the initial scan frequency manually to have any chance of it syncing up.


  • #5
    nd
    Registered Users, Registered Users 2 Posts: 1,855 ✭✭✭nd


    my digiweb has been terrible at random parts of the day over the last 3 or 4 weeks......

    this is my current ping
    =============================
    Reply from 217.114.163.194: bytes=32 time=158ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=168ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=167ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=161ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=168ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=162ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=165ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=178ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=174ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=175ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=188ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=175ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=180ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=183ms TTL=124

    Ping statistics for 217.114.163.194:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 158ms, Maximum = 188ms, Average = 171ms

    =============================================

    it goes like this for a few hours everyday then returns back to averaging about 20 ms ping ....which is what it used to be all the time before.


  • #6
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    hi ND.
    do you get packet loss?
    does the modem restart itself? (this is my 2nd one)
    my highest ping to digiweb.ie today was 6000+(didnt think that was possible)


  • Advertisement
  • #7
    nd
    Registered Users, Registered Users 2 Posts: 1,855 ✭✭✭nd


    occasionally but not that often......and about 5 minutes ago my ping returned to normal.

    this is it now
    ===============

    Reply from 217.114.163.194: bytes=32 time=27ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=24ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=19ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=22ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=21ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=19ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=19ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=22ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=21ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=19ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=25ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=23ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=26ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=23ms TTL=124

    Ping statistics for 217.114.163.194:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 27ms, Average = 22ms
    ==========================


    this has happed everyday for the last few weeks....it's strange.


  • #8
    nd
    Registered Users, Registered Users 2 Posts: 1,855 ✭✭✭nd


    oh and no my modem doesn't restart itself.


  • #9
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    this cant be contention at this time of the day
    tests on irishisptest i'e just done

    13/05/2007 23:46 1879 kbps (230 KB/s) 496 kbps (61 KB/s) 53 % 22 ms 360 ms
    13/05/2007 23:46 2350 kbps (287 KB/s) 488 kbps (60 KB/s) 66 % 36 ms 348 ms
    13/05/2007 23:45 2790 kbps (341 KB/s) 494 kbps (61 KB/s) 83 % 44 ms 102 ms


  • #10
    nd
    Registered Users, Registered Users 2 Posts: 1,855 ✭✭✭nd


    I've been with them probably over a year and was very happy with them all along....just this has satarted happening everyday for a few hours.........oh I'm on their dsl rather than metro.........idk if that's relevant.


  • #11
    watty
    Registered Users, Registered Users 2 Posts: 32,417 ✭✭✭✭watty


    DSL uses eircom bitstream unless you have LLU DSL Totally unrelated to Metro.

    ping ftp.heanet.ie also to elimate if the problem is "local" or elsewhere. Some sites I get stable 24ms pings and other further sites pings from 300 to 1900ms. If ANY sites are stable low ping, then the problem is congestion/problems outside of your own ISP.


  • Advertisement
  • #12
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    thx watty, its weird its ok tonight but but it dosen't matter if it playing up or not i get better pings to london than dublin.
    alas i may as well be banging my head off my screen cos there support is as about as useful as an ashtray on a motorbike and trust me i've spent alot of wasted time dealing with them


  • #13
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    hi all.
    just been on to support(first chance i got since it started).

    the usual cr@p was said "we will put you on monitor for 24hs" (never find anything)

    "blaming trees blocking line of sight" (yeah its funny that trees can move as in good 1 day bad another)

    "it looks fine on our side" (haha what side are they on?)

    "i will ring you back tomorrow at this time" (no breath holding from me)

    so as you can see i'm a little bit bitter when it comes to there support.i would have left them but who else is there that is actually good for online gaming?
    i already been with ibb,clearwire and eircom.

    watty i pinged heanet and got just now and got this
    Pinging heanet.ie [193.1.219.0] with 32 bytes of data:

    Reply from 193.1.195.139: bytes=32 time=30ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=16ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=17ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=26ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=36ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=17ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=10ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=17ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=16ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=17ms TTL=252
    Request timed out.
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=207ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=14ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=14ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=13ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=175ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=13ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=14ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=13ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=13ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=12ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=13ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=14ms TTL=252
    Reply from 193.1.195.139: bytes=32 time=22ms TTL=252

    Ping statistics for 193.1.219.0:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% lo
    Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 207ms, Average = 27ms


  • #14
    watty
    Registered Users, Registered Users 2 Posts: 32,417 ✭✭✭✭watty


    Are you wired direct to Modem or using WiFi or Router?

    It looks like periodic bursts of interference either on Metro link or WiFi or Router.

    When I had all four ethernet ports and 5 users on Wifi in use at same time I was seeing that kind of ping oddity on my own lan between two PC on wired ethernet (Usually < 1ms, but spikes to 45 or 200ms). I added a switch, a Linux Router and use the wifi now as only an Access Point (Only one LAN ethernet port in use and no WAN ethernet).

    However local outdoor interference near coax (12MHz to 21Mhz or 490MHz band) or on Microwave path (10.2GHz or 10.55GHz approx) occasionally would cause it. If Microwave it would be near you as other people don't seem to be affected.


  • #15
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    watty wrote:
    Are you wired direct to Modem or using WiFi or Router?

    direct to modem.


  • #16
    watty
    Registered Users, Registered Users 2 Posts: 32,417 ✭✭✭✭watty


    Must be local intermittant interference then.
    local outdoor interference near coax (12MHz to 21Mhz or 490MHz band) or on Microwave path (10.2GHz or 10.55GHz approx) occasionally would cause it. If Microwave it would be near you as other people don't seem to be affected.


  • #17
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    thanks for the info watty.
    sorry but a little confused,what can cause this and is there anything i can do?


  • #18
    watty
    Registered Users, Registered Users 2 Posts: 32,417 ✭✭✭✭watty


    Is there NTL cable anywhere near your modem to Outdoor Radio Set cable or Satellite Dish anywhere near your radio set.

    How far is your outdoor Radio away from the road?

    Email support a much longer ping -t to heanet.ie


  • #19
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    watty wrote:
    Is there NTL cable anywhere near your modem to Outdoor Radio Set cable or Satellite Dish anywhere near your radio set.

    How far is your outdoor Radio away from the road?

    Email support a much longer ping -t to heanet.ie

    I have a coaxial cable connected to a tv card in my pc running from a ntl digital box downstairs.nothing has changed with the setup.
    theres is no dish near the radio set.
    i will be talking to support tomorrow and will mail them the long ping but all they usually only want screen shots from there site's speedtest
    the radio is near the road but in an estate not a busy road

    thanks again


  • #20
    watty
    Registered Users, Registered Users 2 Posts: 32,417 ✭✭✭✭watty


    It's unlikely, but not impossible that if the NTL cable goes anywhere near the Digiweb Modem or coax that you could get interference. Also NTL are changing the frequencies and services on their cable, so you could get interference when it was OK before.

    it's hard to tell as your problem looks quite intermittent.


  • #21
    game4it70
    Registered Users, Registered Users 2 Posts: 2,125 ✭✭✭game4it70


    well all i can say is "i'm shocked"
    actually got a call back from a guy i was dealing with in support.
    they can see the fluctuations in my signal.
    he reckons trees are blocking my line of sight. hehe still blaming those poor trees that plant themselves in my way one day and move another.

    i have to wait till late next week for a service call.not happy about the wait.by then this will be about 2 weeks of this cr@p but at least the admit there is a fault. (took week last time for them to admit)

    will post again when i get call out.

    thx again watty

    keith.


  • Advertisement
Advertisement