UO Second Age

Yeah it sucks pretty bad.. I'm not getting the lag like that though; mine is more every few minutes i'll pause like its saving then will be fine for another few minutes.. then another pause and so on..
But yes I have lost quite a few duels in the Jhelom duel pits (before everyone stopped going there) to these lag spikes..
I'm at the point where when I get the lag I ask everyone in my vicinity if they experienced it.. mostly nobody gets it but me and a few others it seems.

Yesterday lagged for a few seconds and told Derrick immediately, he said he experienced it as well but the funny part was that KING WONG moved quite a few tiles during this and he is in the same area

OSI actually made a little program for tracing lag way back in the day.

I just found it,they still have it on their site.

http://support.uo.com/latency.html

Download UO Trace at the top of the page, it's a little more user friendly for people not too good with DOS.

Hemperor wrote:http://img99.imageshack.us/img99/9316/pingir4.png

This definitely indicates you've got a local problem hemp. You've got a lot of loss at your ISP.

I'm not sure if the program was working well, the ones that lost things would lose it every single time, 100%, I could have left it running all day and it would be the same...too bad command prompt is bunk for me.

What should I do about this?

Hemperor wrote:I'm not sure if the program was working well, the ones that lost things would lose it every single time, 100%, I could have left it running all day and it would be the same...too bad command prompt is bunk for me.

What should I do about this?

Hop 2 is very confusing to me, it's like it's using 0.0.0.0 as a gateway address, which can't possible be correct.

Hop's 4, 5, and 6 completely failed, problebly a momentary failure, but recurring later when trying to get responces from more remote devices.

Does your cmd prompt tracert indicate any problems on rogers.com? Run a few in a row to be sure.

You've by far been reporting the absolute worst packet loss than i've heard and I think there might be something on your end. This doesn't rule out other problems on The Planets network too, but it definately shouldn't be this bad.

I ran it again and it had the exact same results. I just did another trace to rogers.com (with UO Trace) and 3 of the 10 hops have apparently 100% packet loss heh...

Would a command prompt traceroute do the exact same thing? I could start up my piece of crap 450mhz to command prompt on that if necessary...

So this would definitely be an ISP problem and not a router problem?

Better call em up and make them replace everything!

You can't do a tracert on this computer?

That may be indicitive of a problem right there.

Antivirus: http://avast.com

Heh yeah, we've had this discussion befoer. I have used avast in the past and it worked well, but I have a virus again and the trial has run out :/

i ran tracert righ tnow cause i was freezing up relaly badly, and it timed out on the second line, which i assume is relaly close to me? and not anywhere near the server
but i can still use the webpage and all other internet stuff fine? wutup

C:\Documents and Settings\Mark>tracert uosecondage.com

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 6 ms 5 ms 6 ms gw03.lndn.phub.net.cable.rogers.com [66.185.90.6
5]
4 6 ms 6 ms 7 ms gw01.lndn.phub.net.cable.rogers.com [66.185.80.8
1]
5 9 ms 9 ms 8 ms 64.71.241.101
6 22 ms 22 ms 23 ms 64.71.241.118
7 24 ms 24 ms 25 ms 24.153.3.145
8 37 ms 37 ms 37 ms pos-1-12-0-0-cr01.atlanta.ga.ibone.comcast.net [
68.86.85.237]
9 59 ms 61 ms 60 ms pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.153]
10 60 ms 58 ms 59 ms 68.86.88.50
11 60 ms 60 ms 60 ms te7-1.dsr01.dllstx3.theplanet.com [70.87.253.2]

12 59 ms 60 ms 59 ms po31.dsr01.dllstx5.theplanet.com [70.85.127.106]

13 84 ms 64 ms 61 ms 1a.fe.5746.static.theplanet.com [70.87.254.26]
14 59 ms 60 ms 59 ms 8a.b8.5646.static.theplanet.com [70.86.184.138]


Trace complete.

You had the same 2nd line as me Blackfoot, strange eh...We are the same region and same ISP it seems, I don't see your packetloss anywhere, or maybe I just can't read these things?

After I run the trace from the run prompt it performs the trace but immediatly closes the window when its complete. What is the command to get it to pause?

I beleive it was stated in the first or second page the second line (which also timed out on my computer) is if your using a router; or is a local tracert which shouldn't really be the cause of any problems?