Amazing Lag

[max 0]

 

Can i hear from the player of country Malaysia.

 

I enjoy playing in this server so much but the lag that i experiencing lately is abnormal lag which there is no way to play the game anymore.

 

1) network traffic is normal for all(every 2 step for me)

2) Dc most of the time after like 5 steps running in WH

3) Delayed time like 2-5 seconds for spells

4) Chat only = DC

5) Connection sometimes took more than 2 minutes

6) No way to AKF more than 10 minutes i think

 

Hope i m the only one from Malaysia that facing this problem because i can follow up with my service provider but if this is cause by the server, then i and alot of malaysian will have to quit from nemesis.

 

Good work by the GM so far

 

Looking forward for some good news from GM about this problem :unsure:

 

 

 

[~Hunter[GM] 0]

I am sorry I cannot help you and I hope someone else will be able to help.

 

I just want to say that I hope you are able to fix this situation and make things more bearable.

 

I would hate to lose our Malay players and especially you. Youre a good player, decent guy.

 

Good luck

[~Jaapy 0]

Well we can try and diagnose this, but we need some more information.

 

You need to run a traceroute to our gameserver. You can do this as follows:

 

1. Press Start;

2. Click Run;

3. Type in "cmd" (without quotes) and press [ENTER];

4. A black window appears. Type in "tracert 69.93.31.90" (without quotes) and press [ENTER];

5. The route to the gameserver is being diagnosed it will take a minute;

6. When finished, you can look at the LAST line it printed to see the amount of ms (milliseconds) you need. This is the amount of lag you have ingame. If it's 0-100 it's very good, 100-250 is what most user will probably have, 250-500 is still OK, 500-1000 is laggy and 1000+ is unplayable;

7. You need to copy the entire output to the forum. Do it like this:

7A. Right click the black window and select the option Mark or something like that (don't know the name);

7B. Make the selection with your left mouse button (click and drag). Select the entire trace route text it will become white.

7C. Press [ENTER]. The white marking will go away and the text is now in your CLIPBOARD;

7D. Go back to the forum here, make a new post and to paste the text in the message press CTRL+V (or right-click -> Paste);

 

The below is an example of mine. The last few (12 -> 16) are from theplanet, this is where our gameserver is hosted. If the milliseconds start going up in one of these places it OUR fault :-P

 

Example:

 

 12   154 ms   153 ms   154 ms  te9-1.dsr01.dllstx3.theplanet.com [70.87.253.6]
13   152 ms   150 ms   151 ms  te1-4.dsr01.dllstx2.theplanet.com [70.87.253.114]
14   150 ms   150 ms   150 ms  vl1.asr01.dllstx2.theplanet.com [12.96.160.26]
15   155 ms   153 ms   154 ms  gi0-2.car15.dllstx2.theplanet.com [69.41.250.74]
16   155 ms   153 ms   148 ms  5a.1f.5d45.static.theplanet.com [69.93.31.90]

 

I got latency of about ~150ms.

[max 0]

ok jaapy,

thx for the fast reply from u

 

doing it now and will send to u asap

 

from wat i see from the trancert, its not good. most are request time out

i will try few time and compare the result before sending it to u

 

 

 

Microsoft Windows XP [Version 5.1.2600]

? Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\Lester>tracert 69.93.31.90

 

Tracing route to www.helbreathnemesis.com [69.93.31.90]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms mygateway1.ar7 [192.168.1.1]

2 38 ms 12 ms 20 ms 219.93.218.177

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * *

 

done this when i m conected to hbnemesis and my char manage to stay AFK ingame

 

Then i close helbreath down and everything incluse messenger and i still get the same result

 

Lets me know whats more that i can do

 

From wat i see, this problem starts a few days before christmas or its after christmas

 

Really glad that jaapy helping

 

let me know wat to do next

 

Malaysian Players out there, if u guys dont mind pls post the info in command protm together.

[max 0]

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\Lester>tracert 69.93.31.90

 

Tracing route to www.helbreathnemesis.com [69.93.31.90]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms mygateway1.ar7 [192.168.1.1]

2 11 ms 9 ms 9 ms ^C

C:\Documents and Settings\Lester>ping 69.93.31.90

 

Pinging 69.93.31.90 with 32 bytes of data:

 

Reply from 69.93.31.90: bytes=32 time=511ms TTL=110

Reply from 69.93.31.90: bytes=32 time=512ms TTL=111

Reply from 69.93.31.90: bytes=32 time=513ms TTL=111

Reply from 69.93.31.90: bytes=32 time=515ms TTL=110

 

Ping statistics for 69.93.31.90:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 511ms, Maximum = 515ms, Average = 512ms

 

C:\Documents and Settings\Lester>ping 69.93.31.90 -t

 

Pinging 69.93.31.90 with 32 bytes of data:

 

Request timed out.

Reply from 69.93.31.90: bytes=32 time=514ms TTL=110

Request timed out.

Reply from 69.93.31.90: bytes=32 time=513ms TTL=111

Reply from 69.93.31.90: bytes=32 time=513ms TTL=110

Request timed out.

Reply from 69.93.31.90: bytes=32 time=516ms TTL=111

Reply from 69.93.31.90: bytes=32 time=516ms TTL=110

Reply from 69.93.31.90: bytes=32 time=515ms TTL=111

Reply from 69.93.31.90: bytes=32 time=514ms TTL=110

Request timed out.

Reply from 69.93.31.90: bytes=32 time=512ms TTL=111

Reply from 69.93.31.90: bytes=32 time=513ms TTL=110

Request timed out.

Reply from 69.93.31.90: bytes=32 time=510ms TTL=111

Reply from 69.93.31.90: bytes=32 time=513ms TTL=110

 

Ping statistics for 69.93.31.90:

Packets: Sent = 16, Received = 11, Lost = 5 (31% loss),

Approximate round trip times in milli-seconds:

Minimum = 510ms, Maximum = 516ms, Average = 513ms

Control-C

^C

C:\Documents and Settings\Lester>tracert 69.93.31.90

 

Tracing route to 5a.1f.5d45.static.theplanet.com [69.93.31.90]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms mygateway1.ar7 [192.168.1.1]

2 15 ms 14 ms 10 ms 219.93.218.177

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

 

Trace complete.

 

This is the 3rd result

 

Is it surpose to be like this?? i m not getting any result at all :wacko:

 

this is really abnormal

 

 

[Synz 0]

It's rather high considering your geographical location. I would expect you to ping 300-380ms from Malaysia.

 

You also are having a lot of "lost packets", meaning you aren't receiving any information from the server. This would result in your game locking up (Network/Connection Lag Please Wait! in this game).

 

Possible problems:

1. ISP (Internet Service Provider) is having problems resulting in clients having lag and loss.

2. Shared Network's bandwidth being used in excess by one or more users.

 

 

If there were a large amount of people having connection difficulties - it would be the server having the problem.

 

So, this is most likely client-side.

[oceaneagle 0]

I am not one to stick his nose in when the experts are about BUT! I found I reduced lag by running HB in either W95 or W98 mode and closing down all other programs that access the net. Explorer and things such as background programs.

[-*BtO*- 0]

Well we can try and diagnose this, but we need some more information.

 

You need to run a traceroute to our gameserver. You can do this as follows:

 

1. Press Start;

2. Click Run;

3. Type in "cmd" (without quotes) and press [ENTER];

4. A black window appears. Type in "tracert 69.93.31.90" (without quotes) and press [ENTER];

5. The route to the gameserver is being diagnosed it will take a minute;

6. When finished, you can look at the LAST line it printed to see the amount of ms (milliseconds) you need. This is the amount of lag you have ingame. If it's 0-100 it's very good, 100-250 is what most user will probably have, 250-500 is still OK, 500-1000 is laggy and 1000+ is unplayable;

7. You need to copy the entire output to the forum. Do it like this:

7A. Right click the black window and select the option Mark or something like that (don't know the name);

7B. Make the selection with your left mouse button (click and drag). Select the entire trace route text it will become white.

7C. Press [ENTER]. The white marking will go away and the text is now in your CLIPBOARD;

7D. Go back to the forum here, make a new post and to paste the text in the message press CTRL+V (or right-click -> Paste);

 

The below is an example of mine. The last few (12 -> 16) are from theplanet, this is where our gameserver is hosted. If the milliseconds start going up in one of these places it OUR fault :-P

 

Example:

 

 12   154 ms   153 ms   154 ms  te9-1.dsr01.dllstx3.theplanet.com [70.87.253.6]
13   152 ms   150 ms   151 ms  te1-4.dsr01.dllstx2.theplanet.com [70.87.253.114]
14   150 ms   150 ms   150 ms  vl1.asr01.dllstx2.theplanet.com [12.96.160.26]
15   155 ms   153 ms   154 ms  gi0-2.car15.dllstx2.theplanet.com [69.41.250.74]
16   155 ms   153 ms   148 ms  5a.1f.5d45.static.theplanet.com [69.93.31.90]

 

I got latency of about ~150ms.

 

this is what players call PING? (what makes u cast faster/slower..)

[Aealy 0]

noooo :( im so laggy so so laggy i got latency about

 

lets line was 800-1200-2366 im so laggy in game i dunno why .. it happens lately !

[max 0]

noooo :( im so laggy so so laggy i got latency about

 

lets line was 800-1200-2366 im so laggy in game i dunno why .. it happens lately !

 

 

yes i agreed with u, its happen lately

 

 

 

this is what players call PING? (what makes u cast faster/slower..)

 

 

i m not worrying about how fast i can cast bro

 

i cant even run or walk more than 5 or 10 steps

 

my casting time delayed like 2 to 3 seconds most of the time inside WH

 

can u imagine what will happen if other players running around u ? >>> DISCONNECTED(after u died of course)

[-*BtO*- 0]

 

 

 

this is what players call PING? (what makes u cast faster/slower..)

 

 

i m not worrying about how fast i can cast bro

 

i cant even run or walk more than 5 or 10 steps

 

my casting time delayed like 2 to 3 seconds most of the time inside WH

 

can u imagine what will happen if other players running around u ? >>> DISCONNECTED(after u died of course)

 

 

i know u dont worry about it.. i am just asking cos i wanna know and didnt want to open a new thread...

[~Jaapy 0]

From what we can see in the trace route your computer need to traverse 30 "hops", these are devices like switches, routers, etc etc. The last one should be our server machine (though we cant tell right now).

 

The first hop:

1 <1 ms <1 ms <1 ms mygateway1.ar7 [192.168.1.1]

Is your own router probably. It gets the very fast of course as this is local LAN to you.

 

The second hop:

2 15 ms 14 ms 10 ms 219.93.218.177

Is either some cable modem or already some kind of device likely to be in your street somewhere or around your neighbourhood.

 

The third hop times out:

This is probably the first entry into the realm of your ISP. An extensive firewall could be blocking tracert traffic here...

 

Your problem seems to be starting at hop 3, which means the problem lies very near to you. Since ping seems to work I suspect your ISP blocks traceroute ICMP messages (tracert is a little different from ping and can be blocked seperately).

It can also indicate that hop3 is taking a very long time.

Also 30 hops is the default limit so it's seems to stop at hop 30, but maybe its longer.

 

Let's try again with:

 

tracert -d -h 100 -w 60000 69.93.31.90

 

This will allow us a max of 100 hops, each may timeout after 1 minute and -d tells tracert not to resolve DNS hostnames, which may result in better tracing.

 

Also try to do it a few times more (try like 20 times), because ping tells you 31% loss and tracert packets may be lost also indicating the timeout.

Post output here again, let's hope we can see more now. Altough I think output will be same (just cancel after one timout occurs, it wont show more anyway).

 

------------------------

 

So you have 500ms latency, which is not too bad.. should be playable.

But with 31% loss... this is VERY bad... 31% is high! It is the reason you have so much problems.

 

I don't know yet what causes this.

 

 

You need to go through each of the hops in the tracert output and apply a ping to it and measure packet loss seperately to find the source of the problem. We have a strong indication it's hop 3, which may likely be your ISP. But we aren't 100% sure yet.

 

From the website http://www.exit109.com/~jeremy/news/provid...traceroute.html :

If you see packet loss on a connection, you can use ping with your traceroute output to find the source of the loss. Start by pinging the next to last router in the trace. If you still see packet loss, ping the one before that. Eventually the packet loss will disappear, and you have found the part of the path where the problem begins.

[max 0]

From what we can see in the trace route your computer need to traverse 30 "hops", these are devices like switches, routers, etc etc. The last one should be our server machine (though we cant tell right now).

 

The first hop:

1 <1 ms <1 ms <1 ms mygateway1.ar7 [192.168.1.1]

Is your own router probably. It gets the very fast of course as this is local LAN to you.

 

The second hop:

2 15 ms 14 ms 10 ms 219.93.218.177

Is either some cable modem or already some kind of device likely to be in your street somewhere or around your neighbourhood.

 

The third hop times out:

This is probably the first entry into the realm of your ISP. An extensive firewall could be blocking tracert traffic here...

 

Your problem seems to be starting at hop 3, which means the problem lies very near to you. Since ping seems to work I suspect your ISP blocks traceroute ICMP messages (tracert is a little different from ping and can be blocked seperately).

It can also indicate that hop3 is taking a very long time.

Also 30 hops is the default limit so it's seems to stop at hop 30, but maybe its longer.

 

Let's try again with:

 

tracert -d -h 100 -w 60000 69.93.31.90

 

This will allow us a max of 100 hops, each may timeout after 1 minute and -d tells tracert not to resolve DNS hostnames, which may result in better tracing.

 

Also try to do it a few times more (try like 20 times), because ping tells you 31% loss and tracert packets may be lost also indicating the timeout.

Post output here again, let's hope we can see more now. Altough I think output will be same (just cancel after one timout occurs, it wont show more anyway).

 

------------------------

 

So you have 500ms latency, which is not too bad.. should be playable.

But with 31% loss... this is VERY bad... 31% is high! It is the reason you have so much problems.

 

I don't know yet what causes this.

 

Did u do anything jappy?

 

i can run right now after successfully went to IB

 

alittle lag but still playable

 

hope the problem has been solved

 

its that all the posible thing i can do jappy?

i can double check and let my servive provider know about it.

 

[shiba 0]

This might help.

 

http://www.streamyx.com.my/whats_new/whats...rticle_20081220

[evocator 0]

sg gets approx 235ms of latency.

[smellz 0]

alright jaapy is getting real scary. half the thing he said i cant understand but as far as i know from my house i have the same problem for the past month not only 1 week before christmas. 1 thing i know is even in my workplace is the same. alot of time outs. when i connect to any website it takes sometime to load and sometimes waiting for response till it gets connection time out. i think it's the ISP problem. even my bro's workplace has the same problem. judging from a few people i think it's the ISP. i called up and those noobs answering the phone have no idea wat's going on. well i hope they will fix it asap if not nemesis will lose alot of malaysians.

 

20/12/2008

SERVICE INTERRUPTION

 

Dear Valued Customers,

 

Telekom Malaysia Berhad wishes to announce that there is a disruption of its Internet services due to circuits fault on Southeast Asia - Middle East - Western Europe 4 (SMW4) submarine cable network between Palermo (Southern Italy) and Alexandria (Northern Egypt) linking Malaysia to Europe. Due to this, customers using Internet services may now experience slow browsing while accessing websites hosted in Europe.

 

In addition, customers using other IP services such as Virtual Private Network (VPN) and other critical business applications linked to Europe may also experience some service degradation.

 

To alleviate the problem, some of the links have been rerouted to alternate routes to ease the congestion.

 

Restoration works on the affected cables are already in progress. However, in the restoration process, traffic to Northern America may experience minor degradation while traffic to other countries is not affected. TM expects the complete recovery of its services by December 31, 2008. TM will make further announcements on the progress of the restoration works.

 

TM wishes to assure its customers that it is undertaking all necessary measures to restore communications services for its customers as soon as possible.

 

Customers can call TM at 100 and select ?Internet Services? or e-mail us at help@tm.com.my for any Internet related problems.

 

 

 

Thank You.

 

this is what my isp say.

[Cleanser 0]

if any1 using a wireless router to play hb thats a big problem :)

[max 0]

This might help.

 

http://www.streamyx.com.my/whats_new/whats...rticle_20081220

 

 

i consider it good news as our service provider will have to fix this if its their problem.

we can still play hb if its fix

 

i only manage to play yesterday for like 1 hours plus

now the lag is back

 

CAN I HAVE ALL THE PLAYERS IN MALAYSIA TO COMMENT ON THE SITUATIONS?

[DEz 0]

if any1 using a wireless router to play hb thats a big problem :)

 

not rly if its good wirless router ;)

 

i use sometimes cable, sometimes wireless

[~Jaapy 0]

OK, all you guys need to do is wait it out. We can't help it.

[ridickulus 0]

i noticed that the lag happen during 9am - 6pm in m'sia, i get 300ms+ and 25% timed out but after 6.30pm i get 200ms+ and 0% time out. guess the network is congested during the day. Btw, TM blocked traceroute for home users, i used my server in the IDC to trace, it's just 20 hops and 200ms+ :)

[smellz 0]

just to check. any m'sian still having the lag problem? it seems better but i still have network traffic when i run long but just 1 or 2 and people jumping around haha. like 1 sec here another sec few coords away. just to check with m'sian players

[Raquzz 0]

if any1 using a wireless router to play hb thats a big problem :)

 

not rly if its good wirless router ;)

 

i use sometimes cable, sometimes wireless

Well if u have WCZ on, on xp, its very laggy, But I have turned it off so Im not too laggy. Well my ping is about 250 and Im living in Finland so I assume its pretty normal. So wireless router does just fine.

[ridickulus 0]

seems the line is back to normal now. i got a constant 200ms+ with no packet loss most of the time. what bout u guys?

[smellz 0]

i trying to do the tracert and i get same like max all request timed out. my ping is roughly 500-550 in my workplace but at home i have no idea. seems like my house is better than my workplace because the router splits the connection to 4-5 desktop and lappy. let me check at home. but these few days it's better. might be ok if i go back and check tonight.