2 pc RED Lineage 2

Hi there, before I star to talk about my problem, Sorry for my bad english hehe :)

Well this is what is happen to me playing 2 pc on red, After making some test with Lineage 2 at any server I realize playing with 2 pc on red I got some lag (online)...

This is what i got :

1 PC AMD Phenom 9950 4 GB ddr2 7950 gt
2 PC AMD Phenom 2 955 4 Gb ddr 3 8800 GT
2MB Conexion on internet ( I Know the internet conex its not big deal but I can play games like Guild Wars , Aion Even at Chinesse Server , with out any Lag with 2 pc on.

So only got this issue if i got connect the 2 pc, the way connect is Modem - Router - 2 PC,

If I only let 1 pc the games never lags online even with 3 Client at same computer...

Well I hope you can undertand what im trying to say. thank you for any help

Poisonsita :)
Aria Server.

e-e-e-e--e..... I don't get it, soz... :/

I m not quite sure what red refers to :S

If you mean that 2 clients on 2 pcs you get lag whereas 2 clients on 1 pc you get no lag check your router and cabling

I m not quite sure what red refers to :S

If you mean that 2 clients on 2 pcs you get lag whereas 2 clients on 1 pc you get no lag check your router and cabling

that's a **** of a clue!

red=net or network....in spanish anyway.

So 2 pc's playing L2 will lag out but only one pc connected will not lag, even if there a multiple clients on the one.

Weird, never experienced that. I can have several clients on one pc or 3 pc's with several each and dont get any more lag by the number of connected pc's, unless all the pc's are running junk in the background at the same time (IE large wndows updates all downloading at the same time on all pc's)...etc.

maybe it's not a PC problem?
maybe the problem is with Allocated bandwith?
i mean i had an issue where someone else on my network logged on, caused me huge lag spikes, and i only run one client. banwith caps are often problematic, i suggest finding out the information on your network allocation... could also be a problem with your router/hub...
how many people are on your network?

oh? 2mb?
i lag on a 6mb connection:) maybe time to upgrade?
now only if there were some program so you wouldn't actually have to open lineage 2 to play...

2MB should be enough.

Try running several clients on one PC with disabled "decrease background performance" in options. If it doesn't lag, then it's definitely a problem in your part of the network (router, one of PCs or cabling).

Hi ElfyGirl

Try to se if its your router settings making the latency. Check the site http://portforward.com/ . they have port forwarding guides for all games and routers.

gl

Hi ElfyGirl

Try to se if its your router settings making the latency. Check the site http://portforward.com/ . they have port forwarding guides for all games and routers.

gl


Congratulations, excelent web page, nice info :D

2MB should be enough.

Try running several clients on one PC with disabled "decrease background performance" in options. If it doesn't lag, then it's definitely a problem in your part of the network (router, one of PCs or cabling).

For me "decrease background performance" does not sound as option affecting network aspects :-D

And is true that if you use program to use mouse/keyboard of 1 machine on more machines (for example Synergy) - these programs used to unfocus window on all computers except the one with active pointer.
This unfocus will cause graphic based lag if "decrease background performance" is checked.

For me "decrease background performance" does not sound as option affecting network aspects :-D
Dunno, just to be sure. I didn't analyze their protocol, but I can expect this stuff to decrease network load from a client in background as well.

I had pretty much the same problem. However, I upgraded my video card so that I could run two monitors on it, and now I can run two accounts (one on each monitor) through one PC and have very little user end lag. (server lag is quite another issue). BTW, I share a T1 with 74 other apartments in my complex so at times my bandwidth is comperable to a 56k modem, and still very little lag on my end running it this way.

Hi there, Many thanks for all answers, I did what you guys say.. actually test this site http://portforward.com/ ty btw :), very nice site to know , but im still having the same latency when i got 2 pc conected at same red, I think its a problem for router or i dont know..

Any one knows if i use a Swicth instead a router will works fine ?

Again thank you for your cooperation.

Regards!

I'm experiencing lags all days long, and lateley those lags increase and increase every minute!
IDN what to do... can this port forwarding help me?

The port forwarding page guides you through what ports needs to be open as a recommendation from NCsoft. Its not bad to do it but it might not necessary help with the problem you have.

@Elfygirl
Check your routers firmware if there is any update around.
Also check the PCs network card link speed and duplex. Set it to AUTO if your not sure what speed your router are set too. Else be sure to set it according to your routers.

A modern router is to prefer before a switch if thats the only device you have connected before reaching your internet connection. A switch doesnt normally provide any kind of "fire wall" protection like NAT etc.

The port forwarding page guides you through what ports needs to be open as a recommendation from NCsoft. Its not bad to do it but it might not necessary help with the problem you have.

@Elfygirl
Check your routers firmware if there is any update around.
Also check the PCs network card link speed and duplex. Set it to AUTO if your not sure what speed your router are set too. Else be sure to set it according to your routers.

A modern router is to prefer before a switch if thats the only device you have connected before reaching your internet connection. A switch doesnt normally provide any kind of "fire wall" protection like NAT etc.

IDN what's goin on but every one in a month or two, I'm having this FULL TIME LAGG where I type anything and it appears only in a second or two in the chat. The bad thing is: when the problem occurs, it lasts for at least a month :/ This time it's been lasting for almost two months now :///

@Woonaloow

Whats your location? Im in euro. Very often when you have those latencies for a longer time it a router in your routing way to the Lineage2 server. It can be small latencies that don’t trigger any alarm at the company managing that specific router. When doing normal surfing you won’t notice anything but when you play online all those small latencies can be very very enjoying. Normally when this faulty router is restarted the problem goes away.

It a small procedure to find out what router and who owns.

With the commands tracert and ping (if they are familiar) you can find out which router and then you can use a whois-site or service to find out about the owner. They usually have a tech mail address that you can send a mail to.

I did this a few time and the problem was gone a few hrs later.

@Woonaloow

Whats your location? Im in euro. Very often when you have those latencies for a longer time it a router in your routing way to the Lineage2 server. It can be small latencies that don’t trigger any alarm at the company managing that specific router. When doing normal surfing you won’t notice anything but when you play online all those small latencies can be very very enjoying. Normally when this faulty router is restarted the problem goes away.

It a small procedure to find out what router and who owns.

With the commands tracert and ping (if they are familiar) you can find out which router and then you can use a whois-site or service to find out about the owner. They usually have a tech mail address that you can send a mail to.

I did this a few time and the problem was gone a few hrs later.

Man...we really need to talk! Do you have ICQ,SKYPE? Pm me plz. This sounds like what I need!

No I don’t have that. I will try to explain ><

To use those tools you need to open a DOS Windows

In Windows start menu click Start – Run…
Type “CMD”
In the dos window type “Tracert www.lineage2.com (http://www.lineage2.com)” (same global routing as to the servers I think ^^)

Now you see a number of hops appearing.

Write down the last IP-Address before the hops start to say:
* * * Request timed out

Now, open a new DOS window and type “Ping {IP ADDRESS} –t

IP address should be something like XXX.XX.XXX.XX

It will now send repeated ping to the last replying router in your routing way to L2. Check if you get any “Request timed out” or if the ping to that router is steady.

It should look something like: (IP is fake in the example below)

Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121

The “time” section should be steady and not vary much

This example result is good enough:

Reply from {IP ADDRESS}: bytes=32 time=140ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=140ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=145ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=150ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=165ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=178ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=180ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=160ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=150ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=155ms TTL=121

This example result is bad: (High pings)

Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=12ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=900ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121

This example result is even worse: (flops)

Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Request timed out.
Request timed out.
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=12ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=900ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Request timed out.
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121

yeah.. I know how to do it... but, plz explain what to do next? I mean, what should I do when (and if) I get some BAD results?
What's next?

Edit: Could you plz copy-paste here YOUR tracert for www.lineage2.com (http://www.lineage2.com)? I hope this info is not confidential....

Edit2: At least give me your e-mail, so I could send you my tracert report for your investigation (if you don't mind)

My trace route will not be the same as yours so you need to look at it yourself. Just try to find out the first router in your routing way that give you bad results. Start pinging the last router and then the one before that and so on untill you get a good ping. When you get a good ping you ping the router after that and if that one still give a bad result, thats the one to pin point.

Post that one here IP and Name and we go from there.

My trace route will not be the same as yours so you need to look at it yourself. Just try to find out the first router in your routing way that give you bad results. Start pinging the last router and then the one before that and so on untill you get a good ping. When you get a good ping you ping the router after that and if that one still give a bad result, thats the one to pin point.

Post that one here IP and Name and we go from there.

thanks! I'm about to leave home from work atm, I'll post from home! Thank you for your help, man! Lemme add a plus to you....

No I don’t have that. I will try to explain ><

To use those tools you need to open a DOS Windows

In Windows start menu click Start – Run…
Type “CMD”
In the dos window type “Tracert www.lineage2.com (http://www.lineage2.com)” (same global routing as to the servers I think ^^)

Now you see a number of hops appearing.

Write down the last IP-Address before the hops start to say:
* * * Request timed out

Now, open a new DOS window and type “Ping {IP ADDRESS} –t

IP address should be something like XXX.XX.XXX.XX

It will now send repeated ping to the last replying router in your routing way to L2. Check if you get any “Request timed out” or if the ping to that router is steady.

It should look something like: (IP is fake in the example below)

Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121

The “time” section should be steady and not vary much

This example result is good enough:

Reply from {IP ADDRESS}: bytes=32 time=140ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=140ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=145ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=150ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=165ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=178ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=180ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=160ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=150ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=155ms TTL=121

This example result is bad: (High pings)

Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=12ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=900ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121

This example result is even worse: (flops)

Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=14ms TTL=121
Request timed out.
Request timed out.
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=12ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=11ms TTL=121
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=900ms TTL=121
Reply from {IP ADDRESS}: bytes=32 time=880ms TTL=121
Request timed out.
Request timed out.
Reply from {IP ADDRESS}: bytes=32 time=10ms TTL=121



Hi there thank for the info, I made exactly what you did, and I see this :

* * * Request timed out

and

Request timed out

So the weird thing its a go to www.lineage2.com and also works perfect...

Gotta love nab netadmins :S

most routers these days block ICMP packets, your tracert means nothing more than a chance for you to see some of the hops, you can't diagnose problems in other networks.

If you 're lagging all the time chances are that either a) you got a cheapo net connection from a lousy provider that hops you to death before getting on the prime lines or b) you got some crap on your network/pc eating up your bandwidth.

lineage2.com is one of those that block icmp btw, that's why your requests timeout.

Gotta love nab netadmins :S

Yes and many other companys block it but In my expeirence the problems was never it their net because its carfully monitored. I solved my problem this way a few times and trying to share it with others to atleast try if it help. And most public routers does not block ping, but I guess you already know that.

Last post in this thread.

2 31 ms 19 ms 19 ms var-UTC.ukrtel.net [195.5.5.18]
3 31 ms 16 ms 20 ms 10.70.1.57
4 220 ms 114 ms 65 ms 212.73.203.41
5 62 ms 58 ms 60 ms ae-6-6.ebr1.Frankfurt1.Level3.net [4.69.135.34]
6 88 ms 72 ms 76 ms ae-91-91.csw4.Frankfurt1.Level3.net [4.69.140.14]
7 67 ms 59 ms 58 ms ae-92-92.ebr2.Frankfurt1.Level3.net [4.69.140.29]
8 156 ms 159 ms 179 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.58]
9 267 ms 300 ms 172 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
10 199 ms 165 ms 159 ms ae-2-79.edge1.Washington4.Level3.net [4.68.17.82]
11 150 ms 159 ms 159 ms 4.68.111.254
12 330 ms 341 ms 335 ms 0.ge-5-1-0.XL3.IAD8.ALTER.NET [152.63.41.154]
13 326 ms 335 ms 337 ms 0.so-6-0-0.XL1.TCO4.ALTER.NET [152.63.32.69]
14 166 ms 159 ms 159 ms POS6-0.GW3.TCO4.ALTER.NET [152.63.35.61]

the most interesting thing is that I was waited for at least (AT LEAST!!!) 20 seconds for each line to appear. The second line (2: 31 ms 19 ms 19 ms var-UTC.ukrtel.net [195.5.5.18]) took me 30 secs of waiting! is that ok? Couse it says 19ms....

166ms from kiev to vienna to frankfurt to dc to colorado to virginia aint bad

Hi again.. ok this is what i got this afternoon, I star playing at Phoenix, to know about latency..., well also was Very Nice.. Not even cero lag, show me 86 from ping, so yesterday was imposible to play...

The weird things its the server let me play today around 1 hour after that, I star laging horrible... and then works fine again.. star thinking its server problem..

Well does any 1 can explaind me plz im not so good in this stuff , about how I ping on www.lineage2.com and i recieve it time out... and i can go site without a problem and play even "somethimes"

Regards! =)

Well does any 1 can explaind me plz im not so good in this stuff , about how I ping on www.lineage2.com and i recieve it time out... and i can go site without a problem and play even "somethimes"

Regards! =)
->

most routers these days block ICMP packets

166ms from kiev to vienna to frankfurt to dc to colorado to virginia aint bad

Yes, maybe, but is said 166ms, but I was waiting for 30-50secs for this line to appear!

Here's my another tracert from a different ISP:

Microsoft Windows XP [Версия 5.1.2600]
(С) Корпорация Майкрософт, 1985-2001.

Трассировка маршрута к lineage2.com [206.127.153.147]
с максимальным числом прыжков 30:

1 1 ms 1 ms 1 ms vpn.maxnet.ua [79.171.120.13]
2 1 ms 1 ms 1 ms bb-core-ix1.maxnet.ua [79.171.120.7]
3 1 ms <1 мс 1 ms pool1.maxnet.ua [79.171.120.234]
4 2 ms 2 ms 1 ms inet-gw.maxnet.ua [79.171.120.241]
5 8 ms 8 ms 8 ms undefined.datagroup.com.ua [77.222.145.149]
6 40 ms 40 ms 40 ms tr1-v454.de-fra.datagroup.ua [80.91.160.206]
7 40 ms 42 ms 50 ms tge5-3.fr3.frf.llnw.net [80.81.192.221]
8 56 ms 51 ms 49 ms tge10-1.fr3.ams.llnw.net [69.28.172.9]
9 136 ms 129 ms 127 ms tge5-1.fr4.lga.llnw.net [69.28.171.86]
10 133 ms 133 ms 137 ms tge2-3.fr4.iad.llnw.net [69.28.171.153]
11 133 ms 140 ms 133 ms ve5.fr3.iad.llnw.net [69.28.171.213]
12 * * * Превышен интервал ожидания для запроса.
13 * * * Превышен интервал ожидания для запроса.
14 *

the most interesting thing is that I was waited for at least (AT LEAST!!!) 20 seconds for each line to appear. The second line (2: 31 ms 19 ms 19 ms var-UTC.ukrtel.net [195.5.5.18]) took me 30 secs of waiting! is that ok? Couse it says 19ms....

Could be some problem with your DNS resolution (then 30 sec is the time to find that 195.5.5.18 is var-UTC.ukrtel.net).

Could be some problem with your DNS resolution (then 30 sec is the time to find that 195.5.5.18 is var-UTC.ukrtel.net).

Influenced each line? I mean.. what should I do about it?

try tracert -d whatever.com

but usually the delay is just tracert waiting for the lost packets to time out