1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Massive laggs and cant find any reason.

Discussion in 'Archive' started by m0rph3u5, Dec 4, 2012.

Thread Status:
Not open for further replies.
  1. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    hello.

    starting from 22.11.2012 i am experiencing massive lags every day.

    since that i have confirmed that it is not a computer problem. i have 2 pc and 1 laptop. all have same problem. i have tried to reinstall windows and game and still same. i have tried to play from my friends internet using my laptop and didn't had any problem. we both use same internet service provider but he live in another area. so i started to check my internet connection.

    pinging l2.geo.eu [78.46.105.147] with 32 bytes of data:
    reply from 78.46.105.147: bytes=32 time=23ms ttl=55
    reply from 78.46.105.147: bytes=32 time=17ms ttl=55
    reply from 78.46.105.147: bytes=32 time=35ms ttl=55
    reply from 78.46.105.147: bytes=32 time=40ms ttl=55

    tracing route to l2.geo.eu [78.46.105.147]
    over a maximum of 30 hops:

    1 3 ms 7 ms 2 ms 10.254.48.1
    2 6 ms 5 ms 9 ms brhm-core-2a-ae3-1333.network.virginmedia.net [213.106.228.81]
    3 8 ms 4 ms 9 ms brhm-bb-1a-ae8-0.network.virginmedia.net [62.253.174.73]
    4 5 ms 6 ms 7 ms nrth-bb-1b-ae2-0.network.virginmedia.net [62.253.185.85]
    5 5 ms 7 ms 2 ms nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]
    6 8 ms 4 ms 2 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    7 9 ms 8 ms 8 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    8 74 ms 70 ms 82 ms decix-gw.hetzner.de [80.81.192.164]
    9 36 ms 66 ms 59 ms hos-bb1.juniper1.rz12.hetzner.de [213.239.240.251]
    10 40 ms 46 ms 63 ms hos-tr2.ex3k11.rz12.hetzner.de [213.239.228.172]
    11 41 ms 47 ms 37 ms internethosting.at [78.46.105.147]

    trace complete.

    speedtest.net shows 20mb/s down 1,5mb/s up

    looks fine for me. everything else works just perfect. fast web browsing torrents etc. but still i called my internet service provider and they came to check everything. they could not find any real problem but they adjusted power levels hoping that it will help. it didn't.

    so now i am at the last part in this chain... lineage 2 server connection or something else that can generate this problem for lineage 2 only.

    it is not possible to play with 5-10 second lags on every move. i have 2 accounts and my girlfriend have 3 almost all of them are pa. strange thing is that there is a chance to get lucky and when we load all accounts maybe 1 will go without any lags... :confused: others in same time will lag and get dc after some time. it is like random... sooner or later it will start to lag as well but at least can play for few hours.

    any ideas? for me it looks strange... i have tried everything that i could. :(
     
  2. Razzly

    Razzly Banned

    Joined:
    17.12.11
    Messages:
    2,463
    Likes Received:
    253
    i guess you use connect to your router wireless. can you try to connect your laptop/pc to a router using cable?

    my internet provider gave me terrible router which is called livebox. if i connect to it with a cable - no problem. but i have lag festival using wireless.

    another thing - you can try to change a channel which your router use to send a signal.

    sample from my router:

    [​IMG]

    tip: try to find channell which is used least in your area. you have to get additional program for it.
     
  3. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    2 pc connected with cabel. 1 laptop connected over wifi. it makes no diference in this case. :( thx for try anyway. and it started exactly at 22.11.2012. before that never had any lags and i play since 1st day of this server :)
     
  4. masteroforion

    masteroforion User

    Joined:
    11.09.12
    Messages:
    35
    Likes Received:
    1
    check packet loss
     
  5. Razzly

    Razzly Banned

    Joined:
    17.12.11
    Messages:
    2,463
    Likes Received:
    253
    try to download battleping and launch it in demo mode. if its go smooth then it might be your provider problem
     
  6. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    masteroforion ping is perfect no time outs no lost packets.

    razzly virginmedia engineers checked everything today. they came to check exactly this problem because i explained to them that i can't play lineage 2 anymore and everything except lineage works fine. as i wrote in first post they found only to high downstream power level and adjusted it. if you will look at my trace route what i posted you will see almost ideal response. i will check that battleping and post results. ty
     
  7. Razzly

    Razzly Banned

    Joined:
    17.12.11
    Messages:
    2,463
    Likes Received:
    253
  8. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    03/12/2012 23:18:54.24

    windows ip configuration

    host name . . . . . . . . . . . . : agentlv-pc
    primary dns suffix . . . . . . . :
    node type . . . . . . . . . . . . : hybrid
    ip routing enabled. . . . . . . . : no
    wins proxy enabled. . . . . . . . : no

    ethernet adapter local area connection:

    connection-specific dns suffix . :
    description . . . . . . . . . . . : realtek pcie gbe family controller
    physical address. . . . . . . . . : 48-5b-39-a7-3a-f3
    dhcp enabled. . . . . . . . . . . : yes
    autoconfiguration enabled . . . . : yes
    link-local ipv6 address . . . . . : fe80::e183:a2f6:ae25:fbd%10(preferred)
    ipv4 address. . . . . . . . . . . : 192.168.0.5(preferred)
    subnet mask . . . . . . . . . . . : 255.255.255.0
    lease obtained. . . . . . . . . . : 03 december 2012 20:09:12
    lease expires . . . . . . . . . . : 04 december 2012 20:09:12
    default gateway . . . . . . . . . : 192.168.0.1
    dhcp server . . . . . . . . . . . : 192.168.0.1
    dhcpv6 iaid . . . . . . . . . . . : 239622969
    dhcpv6 client duid. . . . . . . . : 00-01-00-01-17-2a-1e-cc-48-5b-39-a7-3a-f3
    dns servers . . . . . . . . . . . : 194.168.4.100
    194.168.8.100
    netbios over tcpip. . . . . . . . : enabled

    ethernet adapter vmware network adapter vmnet1:

    connection-specific dns suffix . :
    description . . . . . . . . . . . : vmware virtual ethernet adapter for vmnet1
    physical address. . . . . . . . . : 00-50-56-c0-00-01
    dhcp enabled. . . . . . . . . . . : no
    autoconfiguration enabled . . . . : yes
    link-local ipv6 address . . . . . : fe80::dc6e:46e3:d322:5a91%15(preferred)
    ipv4 address. . . . . . . . . . . : 192.168.73.1(preferred)
    subnet mask . . . . . . . . . . . : 255.255.255.0
    default gateway . . . . . . . . . :
    dhcpv6 iaid . . . . . . . . . . . : 352342102
    dhcpv6 client duid. . . . . . . . : 00-01-00-01-17-2a-1e-cc-48-5b-39-a7-3a-f3
    dns servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    netbios over tcpip. . . . . . . . : enabled

    ethernet adapter vmware network adapter vmnet8:

    connection-specific dns suffix . :
    description . . . . . . . . . . . : vmware virtual ethernet adapter for vmnet8
    physical address. . . . . . . . . : 00-50-56-c0-00-08
    dhcp enabled. . . . . . . . . . . : no
    autoconfiguration enabled . . . . : yes
    link-local ipv6 address . . . . . : fe80::5530:bcce:662d:d0b8%16(preferred)
    ipv4 address. . . . . . . . . . . : 192.168.202.1(preferred)
    subnet mask . . . . . . . . . . . : 255.255.255.0
    default gateway . . . . . . . . . :
    dhcpv6 iaid . . . . . . . . . . . : 369119318
    dhcpv6 client duid. . . . . . . . : 00-01-00-01-17-2a-1e-cc-48-5b-39-a7-3a-f3
    dns servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    netbios over tcpip. . . . . . . . : enabled

    tunnel adapter isatap.{ed496b5e-fe8d-447b-8902-9df4c7ce7b26}:

    media state . . . . . . . . . . . : media disconnected
    connection-specific dns suffix . :
    description . . . . . . . . . . . : microsoft isatap adapter
    physical address. . . . . . . . . : 00-00-00-00-00-00-00-e0
    dhcp enabled. . . . . . . . . . . : no
    autoconfiguration enabled . . . . : yes

    tunnel adapter teredo tunneling pseudo-interface:

    media state . . . . . . . . . . . : media disconnected
    connection-specific dns suffix . :
    description . . . . . . . . . . . : teredo tunneling pseudo-interface
    physical address. . . . . . . . . : 00-00-00-00-00-00-00-e0
    dhcp enabled. . . . . . . . . . . : no
    autoconfiguration enabled . . . . : yes

    tunnel adapter isatap.{4ba87acd-e74a-48a0-82fa-baf7675e7933}:

    media state . . . . . . . . . . . : media disconnected
    connection-specific dns suffix . :
    description . . . . . . . . . . . : microsoft isatap adapter #2
    physical address. . . . . . . . . : 00-00-00-00-00-00-00-e0
    dhcp enabled. . . . . . . . . . . : no
    autoconfiguration enabled . . . . : yes

    tunnel adapter isatap.{ea97fa85-3ed2-48c5-acba-f247b45514bd}:

    media state . . . . . . . . . . . : media disconnected
    connection-specific dns suffix . :
    description . . . . . . . . . . . : microsoft isatap adapter #3
    physical address. . . . . . . . . : 00-00-00-00-00-00-00-e0
    dhcp enabled. . . . . . . . . . . : no
    autoconfiguration enabled . . . . : yes

    windows ip configuration

    successfully flushed the dns resolver cache.

    tracing route to cdn.inn.eu [109.105.154.6]
    over a maximum of 30 hops:

    1 6 ms 6 ms 5 ms 10.254.48.1
    2 7 ms 7 ms 7 ms brhm-core-2a-ae3-1333.network.virginmedia.net [213.106.228.81]
    3 7 ms 7 ms 6 ms brhm-bb-1a-ae8-0.network.virginmedia.net [62.253.174.73]
    4 13 ms 13 ms 11 ms nrth-bb-1b-ae2-0.network.virginmedia.net [62.253.185.85]
    5 109 ms 11 ms 10 ms nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]
    6 13 ms 13 ms 12 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    7 23 ms 23 ms 49 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    8 34 ms 31 ms 31 ms gw-br02.frankfurt.telindus.lu [80.81.194.209]
    9 35 ms 35 ms 35 ms static-31-204-89-1.telindustelecom.lu [31.204.89.1]
    10 35 ms 55 ms 34 ms static-31-204-88-150.telindustelecom.lu [31.204.88.150]
    11 34 ms 31 ms 31 ms 109.105.154.6

    trace complete.

    tracing route to frostsecurity.net [109.105.154.4]
    over a maximum of 30 hops:

    1 7 ms 5 ms 6 ms 10.254.48.1
    2 7 ms 6 ms 7 ms brhm-core-2a-ae3-1333.network.virginmedia.net [213.106.228.81]
    3 5 ms 7 ms 6 ms brhm-bb-1a-ae8-0.network.virginmedia.net [62.253.174.73]
    4 14 ms 11 ms 12 ms nrth-bb-1b-ae2-0.network.virginmedia.net [62.253.185.85]
    5 10 ms 10 ms 12 ms nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]
    6 13 ms 11 ms 11 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    7 27 ms 23 ms 23 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    8 33 ms 32 ms 34 ms gw-br02.frankfurt.telindus.lu [80.81.194.209]
    9 36 ms 46 ms 40 ms static-31-204-89-1.telindustelecom.lu [31.204.89.1]
    10 41 ms 35 ms 40 ms static-31-204-88-150.telindustelecom.lu [31.204.88.150]
    11 31 ms 31 ms 37 ms 109.105.154.4

    trace complete.

    tracing route to geo.l2.eu [109.105.153.10]
    over a maximum of 30 hops:

    1 6 ms 6 ms 5 ms 10.254.48.1
    2 8 ms 5 ms 6 ms brhm-core-2b-ae3-1333.network.virginmedia.net [213.106.228.209]
    3 6 ms 7 ms 7 ms brhm-bb-1b-ae8-0.network.virginmedia.net [62.253.174.77]
    4 57 ms 8 ms 7 ms nrth-bb-1a-as4-0.network.virginmedia.net [62.253.185.105]
    5 9 ms 9 ms 11 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    6 24 ms 26 ms 25 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    7 30 ms 32 ms 30 ms gw-br02.frankfurt.telindus.lu [80.81.194.209]
    8 39 ms 36 ms 37 ms static-31-204-89-1.telindustelecom.lu [31.204.89.1]
    9 35 ms 33 ms 36 ms static-31-204-88-150.telindustelecom.lu [31.204.88.150]
    10 34 ms 34 ms 37 ms geo.l2.eu [109.105.153.10]

    trace complete.

    tracing route to 109.105.156.11 over a maximum of 30 hops

    1 12 ms 5 ms 7 ms 10.254.48.1
    2 8 ms 6 ms 5 ms brhm-core-2a-ae3-1333.network.virginmedia.net [213.106.228.81]
    3 6 ms 7 ms 5 ms brhm-bb-1a-ae8-0.network.virginmedia.net [62.253.174.73]
    4 5 ms 5 ms 6 ms brhm-bb-1b-ae0-0.network.virginmedia.net [62.253.185.154]
    5 8 ms 10 ms 8 ms nrth-bb-1a-as4-0.network.virginmedia.net [62.253.185.105]
    6 12 ms 10 ms 10 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    7 29 ms 36 ms 31 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    8 33 ms 36 ms 31 ms gw-br02.frankfurt.telindus.lu [80.81.194.209]
    9 37 ms 40 ms 35 ms static-31-204-89-1.telindustelecom.lu [31.204.89.1]
    10 34 ms 37 ms 37 ms static-31-204-88-150.telindustelecom.lu [31.204.88.150]
    11 31 ms 32 ms 32 ms 109.105.152.35
    12 31 ms 32 ms 31 ms 109.105.156.11

    trace complete.

    tracing route to 109.105.156.12 over a maximum of 30 hops

    1 5 ms 6 ms 4 ms 10.254.48.1
    2 9 ms 7 ms 7 ms brhm-core-2a-ae3-1333.network.virginmedia.net [213.106.228.81]
    3 7 ms 5 ms 7 ms brhm-bb-1a-ae8-0.network.virginmedia.net [62.253.174.73]
    4 12 ms 15 ms 11 ms nrth-bb-1b-ae2-0.network.virginmedia.net [62.253.185.85]
    5 10 ms 12 ms 10 ms nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]
    6 12 ms 11 ms 12 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    7 25 ms 25 ms 25 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    8 33 ms 31 ms 31 ms gw-br02.frankfurt.telindus.lu [80.81.194.209]
    9 37 ms 36 ms 37 ms static-31-204-89-1.telindustelecom.lu [31.204.89.1]
    10 36 ms 37 ms 35 ms static-31-204-88-150.telindustelecom.lu [31.204.88.150]
    11 29 ms 30 ms 31 ms 109.105.152.35
    12 42 ms 33 ms 34 ms 109.105.156.12

    trace complete.

    tracing route to 109.105.156.21 over a maximum of 30 hops

    1 6 ms 5 ms 5 ms 10.254.48.1
    2 5 ms 9 ms 10 ms brhm-core-2a-ae3-1333.network.virginmedia.net [213.106.228.81]
    3 5 ms 8 ms 7 ms brhm-bb-1a-ae8-0.network.virginmedia.net [62.253.174.73]
    4 8 ms 6 ms 5 ms brhm-bb-1b-ae0-0.network.virginmedia.net [62.253.185.154]
    5 9 ms 28 ms 7 ms nrth-bb-1a-as4-0.network.virginmedia.net [62.253.185.105]
    6 12 ms 11 ms 11 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
    7 26 ms 26 ms 24 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
    8 30 ms 31 ms 31 ms gw-br02.frankfurt.telindus.lu [80.81.194.209]
    9 36 ms 38 ms 38 ms static-31-204-89-1.telindustelecom.lu [31.204.89.1]
    10 36 ms 35 ms 51 ms static-31-204-88-150.telindustelecom.lu [31.204.88.150]
    11 31 ms 29 ms 33 ms 109.105.152.35
    12 33 ms 33 ms 34 ms 109.105.156.21

    trace complete.

    pinging cdn.inn.eu [109.105.154.3] with 1000 bytes of data:
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=40ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=42ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=40ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=42ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=40ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=42ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=43ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=40ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54

    ping statistics for 109.105.154.3:
    packets: sent = 20, received = 20, lost = 0 (0% loss),
    approximate round trip times in milli-seconds:
    minimum = 37ms, maximum = 43ms, average = 39ms

    pinging frostsecurity.net [109.105.154.3] with 1000 bytes of data:
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=40ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=42ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=39ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=45ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=36ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=38ms ttl=54
    reply from 109.105.154.3: bytes=1000 time=37ms ttl=54

    ping statistics for 109.105.154.3:
    packets: sent = 20, received = 20, lost = 0 (0% loss),
    approximate round trip times in milli-seconds:
    minimum = 36ms, maximum = 45ms, average = 38ms

    pinging geo.l2.eu [109.105.153.10] with 1000 bytes of data:
    reply from 109.105.153.10: bytes=1000 time=39ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=41ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=39ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=36ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=38ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=40ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=36ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=38ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=36ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=38ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=37ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=38ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=36ms ttl=245
    reply from 109.105.153.10: bytes=1000 time=38ms ttl=245

    ping statistics for 109.105.153.10:
    packets: sent = 20, received = 20, lost = 0 (0% loss),
    approximate round trip times in milli-seconds:
    minimum = 36ms, maximum = 41ms, average = 37ms

    pinging 109.105.156.11 with 1000 bytes of data:
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=41ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=38ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.11: bytes=1000 time=36ms ttl=53

    ping statistics for 109.105.156.11:
    packets: sent = 20, received = 20, lost = 0 (0% loss),
    approximate round trip times in milli-seconds:
    minimum = 34ms, maximum = 41ms, average = 35ms

    pinging 109.105.156.12 with 1000 bytes of data:
    reply from 109.105.156.12: bytes=1000 time=42ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=38ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=41ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.12: bytes=1000 time=38ms ttl=53

    ping statistics for 109.105.156.12:
    packets: sent = 20, received = 20, lost = 0 (0% loss),
    approximate round trip times in milli-seconds:
    minimum = 35ms, maximum = 42ms, average = 37ms

    pinging 109.105.156.21 with 1000 bytes of data:
    reply from 109.105.156.21: bytes=1000 time=38ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=42ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=39ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=43ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=34ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=37ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=35ms ttl=53
    reply from 109.105.156.21: bytes=1000 time=36ms ttl=53

    ping statistics for 109.105.156.21:
    packets: sent = 20, received = 20, lost = 0 (0% loss),
    approximate round trip times in milli-seconds:
    minimum = 34ms, maximum = 43ms, average = 36ms

    good or bad ?
     
    Last edited by a moderator: Dec 4, 2012
  9. Razzly

    Razzly Banned

    Joined:
    17.12.11
    Messages:
    2,463
    Likes Received:
    253
    for me looks fine, i also let check it someone more oriented about this numbers.

    what about this program battleping? is it better with it ?
     
  10. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    i connected through england 1 and still had same lags. but i will try more tomorrow. today is time to go sleep.
     
  11. Arcadya

    Arcadya User

    Joined:
    03.11.12
    Messages:
    672
    Likes Received:
    28
    Last edited by a moderator: Dec 4, 2012
  12. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    i tried that leatrix latency fix few days ago and it made no difference. i have tried pretty much everything that i could find in google and forums.

    [​IMG]

    [​IMG]

    i tried to ping all the adresses cdn.inn.eu, frostsecurity.net, geo.l2.eu, 109.105.156.11, 109.105.156.12, 109.105.156.21 in the same time using multiple cmd windows and to play in same time. i was looking for any lost packets in the time when i am lagging but nothing. ping was good game still lags 5-10 and sometimes dc. i see how others move around me sometimes i see chat in game but i can't move and when i write in chat it shows up only after 5-10 seconds. if i start to stress by clicking everywhere with mouse and spam in chat i got dc.
     
    michaels89 and tester like this.
  13. Razzly

    Razzly Banned

    Joined:
    17.12.11
    Messages:
    2,463
    Likes Received:
    253
    try this:
    the point number 3 will help to trace the problem... i hope:)

    ps: guide not made by me
     
    Last edited by a moderator: Dec 4, 2012
  14. masteroforion

    masteroforion User

    Joined:
    11.09.12
    Messages:
    35
    Likes Received:
    1
    gm nemzeida wrote me that, when i had lags
    try this maybe will help, check this and send ticket to gm stuff with screens
     
  15. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    after ~20min lags in 2 boxes and 1 disconnect i got this. hope it will help to find the reason.

    [​IMG]

    winmtr.txt
     
  16. Razzly

    Razzly Banned

    Joined:
    17.12.11
    Messages:
    2,463
    Likes Received:
    253
    please provide this data on the ticket to the support ( link ).
     
  17. m0rph3u5

    m0rph3u5 User

    Joined:
    07.12.11
    Messages:
    12
    Likes Received:
    0
    how long it normaly takes to get answer from support ?
     
  18. DeepBlue

    DeepBlue Head Moderator (EU) Head moderator

    Joined:
    30.11.11
    Messages:
    13,751
    Likes Received:
    435
    can take up to 24 hours for a response which is standard protocol for any business. if there is any delay it could just be that they have a large number of tickets and you will get a response as soon as your turn in the queue has arrived.

    on a side note, i also use the same isp as yourself and experience no dc's or lags whilst ingame so we know for sure the isp isnt a problem.
     
Thread Status:
Not open for further replies.