06-28-2009, 06:59 PM
LudaKrishna Wrote:yank i live in canada
Code:Pinging games05.xs4all.nl [194.109.69.205] with 32 bytes of data:
Reply from 194.109.69.205: bytes=32 time=132ms TTL=109
Reply from 194.109.69.205: bytes=32 time=133ms TTL=109
Reply from 194.109.69.205: bytes=32 time=132ms TTL=109
Reply from 194.109.69.205: bytes=32 time=131ms TTL=109
Ping statistics for 194.109.69.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 131ms, Maximum = 133ms, Average = 132ms
Here's the tracert
Code:Tracing route to games05.xs4all.nl [194.109.69.205]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 8 ms 11 ms 8 ms 10.80.192.1
3 9 ms 9 ms 9 ms 24.200.227.94
4 10 ms 9 ms 9 ms 24.200.227.97
5 11 ms 11 ms 10 ms 216.113.122.17
6 30 ms 28 ms 27 ms 216.113.122.78
7 120 ms 121 ms 120 ms cr2-tengig-0-7-0-0.londonuk1.savvis.net [204.70.
195.138]
8 124 ms 126 ms 126 ms msr1-tengig0-3-0-0.uk1.savvis.net [204.70.195.13
4]
9 122 ms 120 ms 120 ms 204.70.203.126
10 135 ms 126 ms 130 ms 206.24.169.254
11 127 ms 128 ms 135 ms ldn-s2-rou-1021.UK.eurorings.net [134.222.230.13
]
12 129 ms 133 ms 131 ms obl-rou-1021.NL.eurorings.net [134.222.231.173]
13 131 ms 131 ms 133 ms 134.222.224.26
14 129 ms 132 ms 131 ms 134.222.97.18
15 132 ms 131 ms 135 ms 0.ae2.xr4.d12.xs4all.net [194.109.5.82]
16 132 ms 129 ms 132 ms te5-4.swcolo2.1d12.xs4all.net [194.109.12.6]
17 132 ms 131 ms 129 ms games05.xs4all.nl [194.109.69.205]
Trace complete.
with a ping of 132 I shouldnt be "freezing" and barley able to walk, again I will say that this is more lag than the norm
You should be able to play fine with 130ms, but it's not the server hardware that is causing it, it is most likely your computer. The ping itself is low enough not to cause lag. If the server hardware would be causing it then everybody would lag the way you do. I have 130ms as well, and I can play fine without much lag at all, even tho I do prefer the days when I had 30ms by far ;p
Do you have a lot of packetloss? It does not say anything about packetloss in your ping-attempt, but on the other hand you may just have been lucky at that time. Ping for longer by typing "ping inx.xs4all.nl -t" and watch a long ping and see if you get timeouts, then post it here again.
My suggestion for what you should do to figure out what is causing it:
- First off let some friend of yours bring his computer to your place and play through your connection. If he also has 130ms and lags then it's the connection, but he should not have that, and then you can be pretty sure that it is your computer causing the lag.
- If he did not lag and you're starting to believe that it is your computer doing it then bring the computer to your friends house and try it there. If you lag there but not him then you can be certain that it is your computer doing it, however you can be 99% certain of it just after your friend testing his computer at your house.
Why do I not think it is the server hardware or your connection?
Answer:
Because if it would be the connection or the server hardware then you should either get packetloss or have A LOT worse ping than 130, with 130ms and no packetloss it should not be the connection nor the server hardware causing it.
Regards,
Hate