UO Second Age

When I type "-ping" I usually get a good response, usually in the 20ms to 50 ms range. However periodically while I'm playing, it seems to come at regular intervals, I get hit with some lag. I'll freeze up for a second or two, and if I hit "-ping" at those times it can get well into the hundreds of ms. Any ideas? A server I used to play on had me run some program that showed the difference hops from my computer to the server and they used that to maximize their service, they had the hops that were slowing response time down to give them more speed there.

Are you running Windows 7? You'll need to disable visual themes and desktop composition on your Razor shortcut to correct the issue (I was having the same issue awhile back.)

If what Hicha said didn't help plz give us more into .. like are you using wireless internet .. instead of just pinging the server do a tracert to find were the lag is coming from ... what hop along the way.

I am running windows xp and have a wireless internet connection on my pc. How do I do a tracert?

start ~ run ~type "cmd" ~ enter

type "tracert login.uosecondage.com" ~enter

copy paste data returned.

Do this when you do and no not have lag post both.

Sorry this took so long I haven't played for weeks. I don't have particular times when there is lag, it usually hits me for only a few seconds, so I don't know if I can grab a tracert when it's happening. Here is one in which I don't believe I experienced the lag.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Kyle>tracert login.uosecondage.com

Tracing route to login.uosecondage.com [64.34.215.106]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.0.1
2 14 ms 28 ms 18 ms 68.84.236.1
3 8 ms 9 ms 9 ms xe-2-2-0-0-sur01.clementon.nj.panjde.comcast.net
[68.85.118.57]
4 9 ms 9 ms 10 ms xe-3-1-2-0-ar03.audubon.nj.panjde.comcast.net [6
8.85.62.129]
5 13 ms 14 ms 14 ms pos-3-7-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.95.149]
6 15 ms 13 ms 14 ms be-10-pe04.ashburn.va.ibone.comcast.net [68.86.8
4.202]
7 13 ms 14 ms 50 ms xe-3-1-0.was10.ip4.tinet.net [77.67.71.193]
8 14 ms 13 ms 14 ms xe-0-0-0.was14.ip4.tinet.net [89.149.184.30]
9 13 ms 14 ms 14 ms peer1-gw.ip4.tinet.net [173.241.128.102]
10 * * * Request timed out.
11 14 ms 13 ms 14 ms uosecondage.com [64.34.215.106]

Thought there was some lag going on with how fast weapons were arming/disarming but might have missed it here.

Tracing route to login.uosecondage.com [64.34.215.106]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 20 ms 24 ms 20 ms 68.84.236.1
3 10 ms 7 ms 9 ms xe-2-2-0-0-sur01.clementon.nj.pa
[68.85.118.57]
4 7 ms 10 ms 13 ms xe-3-1-2-0-ar03.audubon.nj.panjd
8.85.62.129]
5 13 ms 14 ms 14 ms pos-3-7-0-0-cr01.ashburn.va.ibon
8.86.95.149]
6 14 ms 14 ms 14 ms be-10-pe04.ashburn.va.ibone.comc
4.202]
7 14 ms 14 ms 14 ms xe-3-1-0.was10.ip4.tinet.net [77
8 13 ms 11 ms 17 ms xe-0-0-0.was14.ip4.tinet.net [89
9 12 ms 14 ms 14 ms peer1-gw.ip4.tinet.net [173.241.
10 * * * Request timed out.
11 16 ms 15 ms 14 ms uosecondage.com [64.34.215.106]

*bump*

well I can see you have one hop timing out .. however being over 30 hops makes it harder .. i think this might give a better show .. ( I forget I live near server) what is your normal ping to server.

Go to start .. run .. type cmd
type in ping login.uosecondage.com -t

run that for a little bit .. use ctrl c to stop it .

Pinging login.uosecondage.com [64.34.215.106] with 32 bytes

Reply from 64.34.215.106: bytes=32 time=12ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=12ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=12ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=2864ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=25ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=16ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118
Reply from 64.34.215.106: bytes=32 time=13ms TTL=118
Reply from 64.34.215.106: bytes=32 time=14ms TTL=118
Reply from 64.34.215.106: bytes=32 time=15ms TTL=118

Ping statistics for 64.34.215.106:
Packets: Sent = 57, Received = 57, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 2864ms, Average = 63ms

Try and go hard wired if you can see if this fixes .. Wireless can act funny at times .. if you could do a tracert while its lagging i'm betting that slow hop will be the first one ..

I'll have to wire it sometime in the future, it's not really an option right now. But thanks I'll give it a try when I'm doing a wiring project.

I also experience intermittent packet loss and lag. I'm located in Germany.

Traceroute:
Today the packet loss isn't very high (~3%), but I've seen 5-10% in the last days. But even the 3% have a definite impact on playing. :-/
Anything you can do about this?

-Connor

The problem is once the packet leave your provider its pretty much out of your hands .. I'm researching this .. and trying to find some thing that can be done .. and honestly not having a lot of luck .. One idea I've had that I've still got to look into is maybe there is a public free url rediector that we could maybe register a account with and have them redirect to us on a given port .. thus changing the hops that is needed in your journey to the server .

Derrick any comment on this you might have would be welcome.

Thanks for looking into this.

A few hours after my last post with the traceroute, the packetloss jumped to ~40% and UO became nearly completely unplayable. I never experienced it that bad before - it lasted about 30 minutes and then jumped back to normal.
One other guy on IRC confirmed that he also had "crazy lag" at the same time.