Menu
What's new
UOGamers Community

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

  • To obtain new Razor updates, please reinstall Razor from our new website.

Server Move

F

Formater

Knight
Re: Server Move

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

C:\Documents and Settings\Chris>ping

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] target_name

Options:
    -t             Ping the specified host until stopped.
                   To see statistics and continue - type Control-Break;
                   To stop - type Control-C.
    -a             Resolve addresses to hostnames.
    -n count       Number of echo requests to send.
    -l size        Send buffer size.
    -f             Set Don't Fragment flag in packet.
    -i TTL         Time To Live.
    -v TOS         Type Of Service.
    -r count       Record route for count hops.
    -s count       Timestamp for count hops.
    -j host-list   Loose source route along host-list.
    -k host-list   Strict source route along host-list.
    -w timeout     Timeout in milliseconds to wait for each reply.


C:\Documents and Settings\lol>ping -n 10 login.uogamers.com

Pinging login.uogamers.com [209.173.139.110] with 32 bytes of data:

Reply from 209.173.139.110: bytes=32 time=43ms TTL=117
Reply from 209.173.139.110: bytes=32 time=43ms TTL=117
Reply from 209.173.139.110: bytes=32 time=43ms TTL=117
Reply from 209.173.139.110: bytes=32 time=43ms TTL=117
Reply from 209.173.139.110: bytes=32 time=42ms TTL=117
Reply from 209.173.139.110: bytes=32 time=43ms TTL=117
Reply from 209.173.139.110: bytes=32 time=42ms TTL=117
Reply from 209.173.139.110: bytes=32 time=42ms TTL=117
Reply from 209.173.139.110: bytes=32 time=43ms TTL=117
Reply from 209.173.139.110: bytes=32 time=43ms TTL=117

Ping statistics for 209.173.139.110:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 43ms, Average = 42ms

C:\Documents and Settings\lol>

See where it says loss. If there is any loss it is unacceptable.
 
W

Woody III

Wanderer
Re: Server Move

I have noticed that since the move my ping is never consistant. On the old server I had around 100ms ping at all times. On the new server it could range anywhere from 40ms which is the lowest to 203ms the highest. That changes every few seconds if im moving or standing still.
 
F

Formater

Knight
Re: Server Move

Woody III;1683758 said:
I have noticed that since the move my ping is never consistant. On the old server I had around 100ms ping at all times. On the new server it could range anywhere from 40ms which is the lowest to 203ms the highest. That changes every few seconds if im moving or standing still.
Click to expand...

your using -ping in game right?
 
J

Jab

Wanderer
Re: Server Move

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

C:\Documents and Settings\Sug>ping -n 10 login.uogamers.com

Pinging login.uogamers.com [209.173.139.110] with 32 bytes of data:

Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=62ms TTL=113
Reply from 209.173.139.110: bytes=32 time=62ms TTL=113
Reply from 209.173.139.110: bytes=32 time=65ms TTL=113
Reply from 209.173.139.110: bytes=32 time=64ms TTL=113
Reply from 209.173.139.110: bytes=32 time=64ms TTL=113

Ping statistics for 209.173.139.110:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 65ms, Average = 63ms

C:\Documents and Settings\Sug>
 
F

Formater

Knight
Re: Server Move

B
Jab;1683761 said:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Sug>ping -n 10 login.uogamers.com

Pinging login.uogamers.com [209.173.139.110] with 32 bytes of data:

Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=63ms TTL=113
Reply from 209.173.139.110: bytes=32 time=62ms TTL=113
Reply from 209.173.139.110: bytes=32 time=62ms TTL=113
Reply from 209.173.139.110: bytes=32 time=65ms TTL=113
Reply from 209.173.139.110: bytes=32 time=64ms TTL=113
Reply from 209.173.139.110: bytes=32 time=64ms TTL=113

Ping statistics for 209.173.139.110:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 65ms, Average = 63ms

C:\Documents and Settings\Sug>
Click to expand...

No loss and 63ms is perfect.
 
J

Jab

Wanderer
Re: Server Move

i never was saying i had horrible ping.... i was just saying it had gone up from before. anyway.

thanks
 
F

Felony-FA

Sorceror
Re: Server Move

Formater,

maybe you can answer this question for me:

During the ping test, I am pinging an average of 59ms, but in game I ping around 90ms average. Which one is actually correct? Are they both correct? Is it possible that the server adds an additional 30ms to my ping? Thanks.
 
F

Formater

Knight
Re: Server Move

Jab;1683763 said:
i never was saying i had horrible ping.... i was just saying it had gone up from before. anyway.

thanks
Click to expand...

Mark;1676612 said:
Over 400ms: Banksit, roleplay, trash talk on forums
Under 400ms: Playable
Under 200ms: Satisfactory
Under 100ms: Optimal

Just about everyone in the United States (aside from dial-up users) should be under 100ms.

Packetloss is much more important than latency though.
Click to expand...

Just a FYI and besides its funny.
 
P

Point.n.Click-

Wanderer
Re: Server Move

Well that might be why I've noticed some latency changes.... for some reason im still going to dallas first....is this normal?
Way more hops :<
C:\Users\Owner>tracert 209.173.139.110

Tracing route to login.uogamers.com [209.173.139.110]
over a maximum of 30 hops:

1 3 ms <1 ms 1 ms

2 9 ms 13 ms 11 ms

3 14 ms 13 ms 13 ms

4 16 ms 13 ms 11 ms

5 16 ms 15 ms 13 ms Omaha7206-GE-0-1.206.pnpt.net [8.7.192.65]

6 19 ms 18 ms 17 ms Cambridge7206-FA4-1.pnpt.com [69.2.15.9]

7 33 ms 34 ms 36 ms se-4-0-12.hsa1.Denver1.Level3.net [209.245.16.145]

8 35 ms 38 ms 44 ms ae-32-52.ebr2.Denver1.Level3.net [4.68.107.62]

9 35 ms 36 ms 38 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 51 ms 52 ms 54 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 64 ms 48 ms 51 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.136.138]

12 45 ms 41 ms 47 ms ge-0-3-0-69.bbr1.Dallas1.Level3.net [4.68.19.1]

13 50 ms 49 ms 49 ms so-6-0-0.edge1.Dallas1.Level3.net [209.244.15.162]

14 * 48 ms 46 ms 0.so-2-0-0.BR1.DFW13.ALTER.NET [204.255.169.25]

15 46 ms 46 ms 48 ms 0.so-0-0-0.XL4.DFW13.ALTER.NET [152.63.98.70]

16 59 ms 71 ms * 0.so-7-0-0.XL1.IND6.ALTER.NET [152.63.64.66]

17 64 ms 60 ms 60 ms POS6-0.GW1.IND6.ALTER.NET [152.63.68.169]

18 62 ms 67 ms 69 ms profitability-gw.customer.alter.net [157.130.123.170]

19 65 ms 67 ms * 209.173.128.70

20 62 ms 65 ms 66 ms 209.173.128.142

21 * 64 ms 60 ms login.uogamers.com [209.173.139.110]

Trace complete.
 
F

Formater

Knight
Re: Server Move

starsky;1684165 said:
Well that might be why I've noticed some latency changes.... for some reason im still going to dallas first....is this normal?
Way more hops :<
C:\Users\Owner>tracert 209.173.139.110

Tracing route to login.uogamers.com [209.173.139.110]
over a maximum of 30 hops:

1 3 ms <1 ms 1 ms

2 9 ms 13 ms 11 ms

3 14 ms 13 ms 13 ms

4 16 ms 13 ms 11 ms

5 16 ms 15 ms 13 ms Omaha7206-GE-0-1.206.pnpt.net [8.7.192.65]

6 19 ms 18 ms 17 ms Cambridge7206-FA4-1.pnpt.com [69.2.15.9]

7 33 ms 34 ms 36 ms se-4-0-12.hsa1.Denver1.Level3.net [209.245.16.145]

8 35 ms 38 ms 44 ms ae-32-52.ebr2.Denver1.Level3.net [4.68.107.62]

9 35 ms 36 ms 38 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 51 ms 52 ms 54 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 64 ms 48 ms 51 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.136.138]

12 45 ms 41 ms 47 ms ge-0-3-0-69.bbr1.Dallas1.Level3.net [4.68.19.1]

13 50 ms 49 ms 49 ms so-6-0-0.edge1.Dallas1.Level3.net [209.244.15.162]

14 * 48 ms 46 ms 0.so-2-0-0.BR1.DFW13.ALTER.NET [204.255.169.25]

15 46 ms 46 ms 48 ms 0.so-0-0-0.XL4.DFW13.ALTER.NET [152.63.98.70]

16 59 ms 71 ms * 0.so-7-0-0.XL1.IND6.ALTER.NET [152.63.64.66]

17 64 ms 60 ms 60 ms POS6-0.GW1.IND6.ALTER.NET [152.63.68.169]

18 62 ms 67 ms 69 ms profitability-gw.customer.alter.net [157.130.123.170]

19 65 ms 67 ms * 209.173.128.70

20 62 ms 65 ms 66 ms 209.173.128.142

21 * 64 ms 60 ms login.uogamers.com [209.173.139.110]

Trace complete.
Click to expand...

That is fucked up. Call your isp and bitch. Your isp pnpt is connected to the level3 backbone sending you to Dallas and then to the server. It is like the longest possible trip. Let us see that is your home network, your isp's network,level3's network, alter.net's network all before you get there.
I would bitch about it because that is a routing problem.
 
F

Formater

Knight
Re: Server Move

-_-Chamillionaire-_-;1686050 said:
Same here. =[
Click to expand...

Why not post some results for us? What is it I see around here all the time.. um "pics or it didnt happen"?


Please go to Start -> Run ->type cmd then enter
In the command prompt type the following
ping -n 10 login.uogamers.com then enter
when that finishes do the following
pathping login.uogamers.com then enter

Then right click and choose select all and right click and select copy
Make a new thread and at the top put your city and state (or country).
Then just paste your results here.

DO NOT TRUST THE IN GAME -PING COMMAND. IT DOES NOT WORK CORRECTLY ON RUNUO SERVERS AND GIVES FALSE RESULTS THAT ARE NOT EVEN CLOSE. Do not take my word for it check Ryans recent posts he said the same thing. I think Mark said it and even posted the link to the code. This shard is not EA games so things work a little bit different.
 
C

-_-Chamillionaire-_-

Wanderer
Re: Server Move

Pinging login.uogamers.com [209.173.139.110] with 32 bytes of data:

Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=41ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118
Reply from 209.173.139.110: bytes=32 time=43ms TTL=118
Reply from 209.173.139.110: bytes=32 time=42ms TTL=118

Ping statistics for 209.173.139.110:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 43ms, Average = 42ms

Tracing route to login.uogamers.com [209.173.139.110]
over a maximum of 30 hops:
 
F

Formater

Knight
Re: Server Move

-_-Chamillionaire-_-;1686072 said:
I guess not.
Click to expand...

Dunno mine went from 18ms to 43ms but there is no change in game play at all. Fact is 43ms is good and you do not seem to have any packet loss so you should be doing fine.
 
H

hell yeah

Wanderer
Re: Server Move

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

C:\DOCUME~1\ADMINI~1>cd..

C:\DOCUME~1>cd..

C:\>ping -n 10 login.uogamers.com

Pinging login.uogamers.com [209.173.139.110] with 32 bytes of data:

Request timed out.
Reply from 209.173.139.110: bytes=32 time=53ms TTL=114
Reply from 209.173.139.110: bytes=32 time=53ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.173.139.110: bytes=32 time=58ms TTL=114
Request timed out.
Reply from 209.173.139.110: bytes=32 time=55ms TTL=114

Ping statistics for 209.173.139.110:
Packets: Sent = 10, Received = 4, Lost = 6 (60% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 58ms, Average = 54ms

C:\>pathping login.uogamers.com

Tracing route to login.uogamers.com [209.173.139.110]
over a maximum of 30 hops:
0 NEXUS [me]
1 router
2 adsl-3-64-1.mia.bellsouth.net [65.3.64.1]
3 205.152.108.1
4 her00mia-ge-6-3.bellsouth.net [205.152.145.161]
5 65.83.237.156
6 65.83.238.29
7 65.83.238.3
8 65.83.238.64
9 pxr00chi-so-0-0-0.bellsouth.net [65.83.236.64]
10 peer-02-ge-3-0-1-14.chcg.twtelecom.net [66.192.252.108]
11 207-250-147-226.static.twtelecom.net [207.250.147.226]
12 207-250-147-226.static.twtelecom.net [207.250.147.226]
13 209.173.128.70
14 209.173.128.142
15 login.uogamers.com [209.173.139.110]

Computing statistics for 375 seconds...
 
F

Formater

Knight
Re: Server Move

hell yeah;1686578 said:
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\ADMINI~1>cd..

C:\DOCUME~1>cd..

C:\>ping -n 10 login.uogamers.com

Pinging login.uogamers.com [209.173.139.110] with 32 bytes of data:

Request timed out.
Reply from 209.173.139.110: bytes=32 time=53ms TTL=114
Reply from 209.173.139.110: bytes=32 time=53ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.173.139.110: bytes=32 time=58ms TTL=114
Request timed out.
Reply from 209.173.139.110: bytes=32 time=55ms TTL=114

Ping statistics for 209.173.139.110:
Packets: Sent = 10, Received = 4, Lost = 6 (60% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 58ms, Average = 54ms

C:\>pathping login.uogamers.com

Tracing route to login.uogamers.com [209.173.139.110]
over a maximum of 30 hops:
0 NEXUS [me]
1 router
2 adsl-3-64-1.mia.bellsouth.net [65.3.64.1]
3 205.152.108.1
4 her00mia-ge-6-3.bellsouth.net [205.152.145.161]
5 65.83.237.156
6 65.83.238.29
7 65.83.238.3
8 65.83.238.64
9 pxr00chi-so-0-0-0.bellsouth.net [65.83.236.64]
10 peer-02-ge-3-0-1-14.chcg.twtelecom.net [66.192.252.108]
11 207-250-147-226.static.twtelecom.net [207.250.147.226]
12 207-250-147-226.static.twtelecom.net [207.250.147.226]
13 209.173.128.70
14 209.173.128.142
15 login.uogamers.com [209.173.139.110]

Computing statistics for 375 seconds...
Click to expand...

Ok first of all at the end "Computing statistics for 375 seconds" you have to wait awile before the results come up for that and that is what was really needed. You have to be patient. All your current post tells me is that

1. You have major packet loss which is really bad. I recommend using the free tools at dslreports.com to diagnose the problem. I doubt the server move has anything to do with the fact your losing packets somewhere. Please repost with the results after the 375 seconds.
2. The responses you did get to your ping are good and you could play fine with that avg. So you just need to figure out where your packet loss is and get that taken care of asap.

3. Until the packet loss is fixed I would not play any game online (your gonna die).

Hope this helps.
 
You must log in or register to reply here.
Top