lag-o-cron

[Ryuben]

ok got server lag tonight its not my connection as i was downloading before and after it (just now) and getting my normal speed (70kb/s) its neo i pinged the login server and i got this


Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

ping 62.140.29.54

Pinging 62.140.29.54 with 32 bytes of data:

Request timed out.
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=35ms TTL=117
Request timed out.

Ping statistics for 62.140.29.54:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 35ms, Average = 34ms



when i do get in its very laggy and hard to play my ping sits about 60 but feels like 600 and some times bouces about, i randomly synch and it kicks me to login screen where it is very slow and takes a few trys to get my char info
any ideas?

[csh1]

thats the new name....there changign it to lag-o-cron!

[Void Dildano]

Looks like server went down just now.. or is it just me?

[ZoneVortex]

everyone getting this lag? i haven't logged on yet today

[athon]

To get a more accurate view of lost packets, do: ping -t <ip / address>
and leave it for about half an hour. The -t flag tells ping to run indefinitely. Press CTRL+C to exit, or CTRL+Break to show stats but continue pinging.

Alternatively you can als o do something like: ping -n 100 <ip / address>
which will ping the specified address 100 times. Again, press CTRL+C to abort ot CTRL+Break to show stats and continue.

For a full list of ocmmands, run: ping
(ie. no parameters)

Another useful command:

tracert <ip / address>

Displays the route to a specified ip / address. If you run this it may show you a particular point on the route where your signal slows down.

HTH

Athon Solo

[Ryuben]

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

ping -n 100 62.140.29.54

Pinging 62.140.29.54 with 32 bytes of data:

Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=35ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=71ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=72ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Request timed out.
Request timed out.
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Reply from 62.140.29.54: bytes=32 time=33ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Request timed out.
Reply from 62.140.29.54: bytes=32 time=34ms TTL=117
Request timed out.

Ping statistics for 62.140.29.54:
Packets: Sent = 43, Received = 31, Lost = 12 (27% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 72ms, Average = 36ms





>tracert 62.140.29.54

Tracing route to 62.140.29.54 over a maximum of 30 hops

1 6 ms 5 ms 6 ms 10.74.96.1
2 6 ms 5 ms 6 ms lee-t2cam1-b-ge-wan34-111.inet.ntl.com [80.0.55.117]
3 7 ms 7 ms 6 ms lee-t2core-b-ge-wan64.inet.ntl.com [80.0.241.169]
4 7 ms 7 ms 7 ms lee-bb-b-so-120-0.inet.ntl.com [62.253.185.21]
5 12 ms 11 ms 48 ms ren-bb-a-so-000-0.inet.ntl.com [62.253.185.161]

6 24 ms 24 ms 24 ms bre-bb-b-so-200-0.inet.ntl.com [62.253.185.166]

7 24 ms 57 ms 23 ms 195.50.116.133
8 23 ms 24 ms 24 ms so-4-0-0.mp2.London2.Level3.net [212.187.129.253]
9 33 ms * * so-0-0-0.mp2.Hamburg1.Level3.net [212.187.128.66]
10 * 34 ms 34 ms gige5-1.hsipaccess2.Hamburg1.Level3.net [195.122.140.180]
11 * 35 ms 53 ms 212.162.3.84
12 33 ms * 34 ms 62.140.29.54

Trace complete.



u can guess the rest?

[ben77890]

i got a spike of 1602

[Helen Angilley]

No unusual lag here.

Perfectly playable for me.