Lag/Disconect issue, post here !

disconnect after disconnect. very nice. after i pay for pa will i get disconnects x2 too?

 

well players from turkey can play without any dc, but i cant even move around dunno if it's about my connection or the problem that is facing server atm.

 

i'm from france and i have disconnected.
15 dc in the last hours ... it's great for instances, pvp, or just for a quest ...

 

considering that we are a bunch of people with this problem and most of us only have this issue on innova servers, would be nice to hear a "we are working into it" from the admins. the "innova servers are fine" statement doesnt make sense anymore.

 

okay, guys, i'll try to explain the situation a little.

there are no any problem with our servers. there are no problems with our network connection. there are no any problem with the client except some bugs made by developers (which we try to solve). there are no problems with frost though it's rather hard preventing cheats and hacks. 99,9% of dc issues have their solution on your side. they may be related with:

1. antiviruses and firewalls. we hardly try to made our software compatible with all the avs but they update constantly and sometimes compatibility problems appear.
the solution: you can determine the reason of an issue by temporal deleting an av, cleaning up a registry and rebooting pc. if after that the problem is gone, you can be sure that the issue is related with your av. so far the best way to play stable is to tweak the av - to include 4game folder and lineage 2 folder into the exceptions, to switch off web-shield and traffic filter. it doesn't give you 100% guarantee but we are ready to investigate each issue in private.

2. viruses. even if you have a good updating av sometimes there is a chance that you have some viruses on your pc. check the system periodically. the thing is that frost see viruses as cheats injecting game process. there will be dcs and problems with launching the game.
the solution: check for viruses, using a deep check. we hardly recommend to use, for example, the free utility anti-malware .

3. outdated hardware. there is no secret that mmos and l2 especially hardly loading the cpu. that's why you should have a rather fast processor to play comfortably. dcs happen when cpu can't process the frost and game packets in time and the server thinks that protection system is off --> disconnect you as a cheater.
the solution: update all drivers. if it isn't help, update your hardware.

4. bad "windows". pirate versions, repacks, custom installations can have handmade modules and modifications which doesn't allow the client and frost to work correctly. also sometimes os can be full of trash and be damaged which cause many problems including dcs.
the solution: the easiest way is to install clear original windows. but firstly it's better try to clean up the registry (e.g. using ccleaner), clean up startup menu and install all the updates.

5. router. some devices can have internal firewalls and web-shields, and also traffic filters. so the problem is the same as with avs is. also there is some other features and options in different routers.
the solution: the best way to determine a reason of dc is to try to connect your pc to the net without router. if dcs are gone, the problem is in a router. so far you should check its parameters. switch off firewalls and web-shields, and also traffic filters. update its firmware. if it doesn't help please contact router's manufacturer. we will pick up information about problematic routers and ways of its tweaking.

6. bad hardware drivers. when some drivers have no digital signature they can conflict with frost. but all official drivers have it. so you should just to update them.
the solution: you can see if drivers have such a signature in directx information window (windows+r --> type dxdiag). so if some of them doesn't have a digital signature, update them.

7. cheats and hacks. no comments. and no solution except deleting it.

8. problems with updating frost. this issue happens when the client is updating incorrectly. you can enter the game but there will be dc because of wrong frost version.
the solution: delete system folder, delete frost folder, delete all files from a root directory and made a fullcheck.

9. 3g/4g modems. there is no guarantee of stable connection using 3g/4g. even a provider never guarantees it. so even if the very connection doesn't break packets may be lost and you will have dc.
the solution: use more stable internet connection. or play and pray.

10. bad internet connection. not so often but you can have dc because of your internet connection. if a ping is very high or so much packets are losing there will be a dc.
the solution: usually a tracert can show it. if it is, call up your provider and ask for the support. we hardly can do something in such situation.

11. some private rare issues which should be investigated separatedly.
the solution: write to our support.

voila!

 

after mornings update everything was ok but 2h ago i saw 4game update and now im getting dc every 5-10mins and my net getting freez for a moment...

 

i can't play on this server due to constant disconnections, every few minutes.
few things to mention:
1.i am from poland.
2. my internet is 10mb upc connection (having no problem whatsoever in any other online game etc.).
3. my router is d-link dir-300. i've forwarded several ports that i heard l2 is using: 53,80,2106,2009,7777.
4. my antivirus is avast - i have added 4game and lineage 2 folders to exceptions + cdn.inn.eu / frostsecurity.net to net traffic exceptions.
5. installed leatrix latency fixer.
6. my computer is way above l2 requirements, i used to play aion on global and even skyrim on high details, so it's not question of lags or anything pc related. i have fresh windows and all drivers updated.
7. i've tried in cmd ping -t 109.105.156.11 and it shows 0% packets lost, and normal ping is ~55, no spikes even during dc from server. (yes i left it to check if i lose connection during playing, but no)
8. i'm playing on desktop and my wife is playing from laptop, maybe that would be the issue, but we get dc even when only 1 of us is playing and other computer is shut down.
9. i usually can play in the evenings without any dc.
10. i dont lag in the game, at all, no soulshot lags, anything.

if anyone could help me out and tell what else might need checking or maybe i should do something else about my router please do.

 

i recommend you to update a firmware. there is an issue with this router sometimes.

 

i was able to play perfectly fine on the first day and reached level 33, so my computer can handle the heavily populated areas. however since then i keep getting disconnected everytime i log in.
u suggest i should'nt have turn my comp off between two session??

 

don't be angry please =) just write to support, they will help you to solve your issue.

 

and according to this half polish players have sh1ty internet like me for example (d 10mb/s / u 1mb/s) based on planet mh2000 router, on witch i don't have problems to play on servers hosted in usa, but ofc its my configuration problem that i can fluently play on lineage2.com, l2.ws, dragon-network, dex servers, and few others that i have been playing servers. ofc for all others servers my bad internet connection, or pc setting in some strange and impossible way was working, but ofc here is not working. maybe european server is not for "some part" of european society? and whats more strange european serve is in asian part or russia, and why not in europiean that it can work more fluently and makes less jumpls? and yes its work better for france people because polish people have to jump over switzerland to get to russia l2 server

tell me more that its problem from my side when i downloaded client two times from 0, and tested it on 2 pc's in home, 1 pc at friend house, and 1 pc in work. on all pc's (3 different internet connections), my maximum playtime was 30min w/o dc.

Code:

tracert 109.105.129.23
śledzenie trasy do 109.105.129.23 z maksymalną liczbą 30 przeskoków.

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    50 ms    25 ms    26 ms  rze-ru2.neo.tpnet.pl [213.25.2.230]
  3    25 ms    36 ms    42 ms  rze-r1.tpnet.pl [80.49.0.189]
  4    31 ms    52 ms    30 ms  war-r2.tpnet.pl [194.204.175.53]
  5    63 ms    53 ms    53 ms  hbg-b2-link.telia.net [213.248.89.93]
  6    57 ms    53 ms    54 ms  hbg-bb1-link.telia.net [80.91.246.6]
  7    71 ms    75 ms    81 ms  s-bb1-link.telia.net [213.248.64.29]
  8   129 ms    95 ms    93 ms  mow-b3-link.telia.net [80.91.251.222]
  9   178 ms   211 ms   222 ms  mow-m9-i2-link.telia.net [80.91.254.70]
 10    93 ms    92 ms    93 ms  innova-ic-136495-mow-m9-i2.c.telia.net [213.248.
96.70]
 11     *      475 ms   597 ms  sw-1-ti-po-4.msk.inn.ru [109.105.128.34]
 12    91 ms    89 ms    91 ms  109.105.129.23

śledzenie zakończone.

 

everything i wrote is based on my experience supporting l2 client. i've just tried to collect the most popular reasons. my main purpose was to make you not to cry about "bad innova" and "stupid russians" but to help us to solve your issue. you can see there are many reasons of dcs and to find a solution we need some information and a bit of patience from you.
so please write to our support, they will help you.

 

my power to trying to fix "my problem" after i used all knowledge learned on 5years of collage on university of information technology and my specialization was networking, and as i also play l2 since like 4 years, testing proxy, tunneling, and few other things helping in passing some technical issues with connection.
problem is simple, client get information that some date was lost and he makes dc, even if pings passing and there is no lag in game. one missing package and bey bey... dc

 

is there something interesting in wireshark logs?

 

i have latest firmware already installed on my router - 1.04. any other solutions? i'm getting dc nonstop. it's starting to be really frustrating. i have done every single thing you mentioned on this forums and even more. time to say the truth - the problem lies on your side. there is too many people with disconnection problems, it's impossible that everyone got f***** up computer, yet we all can play other games or lineage 2 on other servers.

but other people may have their problems, maybe you could find a solution for me - once more my list:

1.i am from poland.
2. my internet is 10mb upc connection (having no problem whatsoever in any other online game etc.).
3. my router is d-link dir-300. i've forwarded several ports that i heard l2 is using: 53,80,2106,2009,7777.
4. my antivirus is avast - i have added 4game and lineage 2 folders to exceptions + cdn.inn.eu / frostsecurity.net to net traffic exceptions.
5. installed leatrix latency fixer.
6. my computer is way above l2 requirements, i used to play aion on global and even skyrim on high details, so it's not question of lags or anything pc related. i have fresh windows and all drivers updated.
7. i've tried in cmd ping -t 109.105.156.11 and it shows 0% packets lost, and normal ping is ~55, no spikes even during dc from server. (yes i left it to check if i lose connection during playing, but no)
8. i'm playing on desktop and my wife is playing from laptop, maybe that would be the issue, but we get dc even when only 1 of us is playing and other computer is shut down.
9. i usually can play in the evenings without any dc.
10. i dont lag in the game, at all, no soulshot lags, anything.

if anyone could help me out and tell what else might need checking or maybe i should do something else please do.

Code:

microsoft windows xp [wersja 5.1.2600]
(c) copyright 1985-2001 microsoft corp.

c:\documents and settings\user>ping -t 109.105.156.11

badanie 109.105.156.11 z użyciem 32 bajtów danych:

odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=60ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=60ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=58ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=67ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=60ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=58ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=61ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=55ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=52ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=57ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=54ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=51ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=53ms ttl=48
odpowiedź z 109.105.156.11: bajtów=32 czas=56ms ttl=48

statystyka badania ping dla 109.105.156.11:
    pakiety: wysłane = 115, odebrane = 115, utracone = 0 (0% straty),
szacunkowy czas błądzenia pakietów w millisekundach:
    minimum = 51 ms, maksimum = 67 ms, czas średni = 54 ms
control-c
^c
c:\documents and settings\user>

stopped 3 seconds after dc - no packets lost and i was checking shops in giran.

 

where have i said that all pcs that have dcs are bad? there could be compatible problems and they have a solution.

 

so i highly recommend you to write to support.

 

my problem is disconnects since few days, sometime i receive dc after 1h, sometimes even after few minutes and lags in the evening.
today it beats records, disconnects since morning even after 5 minutes (today about 20 disconnects)

so far i've 66 lvl so as you see i could play but these random disconnects and lags in the evening are annoying as hell, especially if i gets few disconnects in 1h.
location: poland

i downloaded it, right now it scanning my pc, we will see.
i chose the longest version of scan.

Code:

microsoft windows [wersja 6.0.6000]
copyright (c) 2006 microsoft corporation. wszelkie prawa zastrzezone.

c:\windows\system32>ping -t 109.105.156.11

badanie 109.105.156.11 z 32 bajtami danych:

odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=67ms ttl=51
uplynal limit czasu zadania.
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=67ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=62ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=61ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=62ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=60ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=66ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
uplynal limit czasu zadania.
odpowiedz z 109.105.156.11: bajtow=32 czas=63ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=64ms ttl=51
odpowiedz z 109.105.156.11: bajtow=32 czas=65ms ttl=51

statystyka badania ping dla 109.105.156.11:
    pakiety: wyslane = 63, odebrane = 61, utracone = 2 (3% straty),
szacunkowy czas bladzenia pakietow w millisekundach:
    minimum = 60 ms, maksimum = 67 ms, czas sredni = 64 ms
control-c
^c
c:\windows\system32>

c:\windows\system32>

edit

ok scan is done.


i added everything to quarantine, what now can i do?

looking for answers, now i go test may it reduce my lags/disconnects, i hope.

 

is there any frost log where we can see why are we disconnecting? seems like there are quite a lot of reasons which would make frost kick me out of the game, so knowing why frost did it would help troubleshooting the problem.

 

hi,

i'm experiencing heavy lag only during peak hours (18h to 22h gmt +1).
i've used ping and tracert out of this period and gets good results (14 jumps and 54 ms ping average, no packet loss, very low variance).


during peak hours i have lags of 1 to 2 seconds every 5 seconds, and sometimes i can't move at all for 5 seconds and need to use the arrows.
today i thought about using ping to the gameserver at peak hour and got this:

Code:

microsoft windows [version 6.1.7601]
copyright (c) 2009 microsoft corporation. tous droits réservés.

c:\users\jeremy>ping -t 109.105.156.11

envoi d'une requête 'ping'  109.105.156.11 avec 32 octets de données*:
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=71 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=71 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
délai d'attente de la demande dépassé.
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
délai d'attente de la demande dépassé.
délai d'attente de la demande dépassé.
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=88 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=74 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=72 ms ttl=51
délai d'attente de la demande dépassé.
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
délai d'attente de la demande dépassé.
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
délai d'attente de la demande dépassé.
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=82 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=73 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=71 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=65 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=84 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=70 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=67 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=69 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=68 ms ttl=51
réponse de 109.105.156.11*: octets=32 temps=66 ms ttl=51

statistiques ping pour 109.105.156.11:
    paquets*: envoyés = 124, reçus = 118, perdus = 6 (perte 4%),
durée approximative des boucles en millisecondes :
    minimum = 65ms, maximum = 88ms, moyenne = 67ms
ctrl+c
^c
c:\users\jeremy>

and here is a tracert done 2 minutes ago:

Code:

microsoft windows [version 6.1.7601]
copyright (c) 2009 microsoft corporation. tous droits réservés.

c:\users\jeremy>tracert 109.105.156.11

détermination de l'itinéraire vers 109.105.156.11 avec un maximum de 30 sauts.

  1     1 ms    <1 ms    <1 ms  livebox.home [192.168.1.1]
  2    20 ms    20 ms    21 ms  80.10.123.200
  3    20 ms    19 ms    19 ms  10.123.109.10
  4    21 ms    21 ms    21 ms  bundle-ether41.ntaub201.aubervilliers.francetele
com.net [193.252.159.110]
  5    20 ms    19 ms    44 ms  ae30-0.niaub201.aubervilliers.francetelecom.net
[193.252.103.26]
  6    23 ms    25 ms    22 ms  81.253.184.10
  7    29 ms    31 ms    30 ms  pos0-11-0-0.lontr1.london.opentransit.net [193.2
51.242.113]
  8    58 ms    57 ms    57 ms  te0-3-0-6.ccr22.lon13.atlas.cogentco.com [130.11
7.14.153]
  9    57 ms    58 ms    57 ms  te0-2-0-0.ccr22.par01.atlas.cogentco.com [130.11
7.50.198]
 10    61 ms    61 ms    62 ms  te2-1.ccr01.rhe01.atlas.cogentco.com [154.54.36.
22]
 11   207 ms   213 ms   202 ms  te2-1.ccr01.lux01.atlas.cogentco.com [154.54.38.
118]
 12    65 ms    89 ms    66 ms  149.6.66.82
 13     *       66 ms    65 ms  109.105.152.35
 14    71 ms    66 ms    70 ms  109.105.156.11

itinéraire déterminé.

c:\users\jeremy>

being healer it's very annoying because i feel frustrated whenever someone dies because of this, even if everything was under control.
if you could take a look to help me, i would be very grateful.

regards


edit: also before telling me problem is from my connexion or w/e, i have absolutely no lag of any sort on any other game or server out there, the tracert also clearly shows a peak of ping just before reaching your server, and packets lost at 109.105.152.35 somewhere near your server.