Brazilian Connection

[pussinboots]

Hello everybody... im new arround here.

Im just here to ask if there is any brazilian player active on the forum...

Why is this in Server & Client Support? I am getting a lot of lag ingame, something like 500ms, and my internet connection is quite good, I mean, it is meant to be 10mbit/s...

So, maybe it is because of the ip adress, I mean, it has to go through a lot of servers before getting there at USA (or whatever country the server is).

Any comment?

My thanks!

[Chaos]

Hello ... Your in the right place ..

First off if ya would go to start-run-"cmd" -enter

Then type ping uosecondage.com

Then please copy paste all that into new reply ..

Also include copy paste of this

Also in "cmd" type tracert uosecondage.com


This is the best place to start

[pussinboots]

Ok, my cmd is actually in portuguese, so I'll try to translate it.

Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\USUARIO>ping uosecondage.com

Disparando contra uosecondage.com [64.34.176.148] com 32 bytes de dados:

Resposta de 64.34.176.148: bytes=32 tempo=595ms TTL=111
Resposta de 64.34.176.148: bytes=32 tempo=557ms TTL=115
Resposta de 64.34.176.148: bytes=32 tempo=581ms TTL=115
Resposta de 64.34.176.148: bytes=32 tempo=559ms TTL=115

Estat¡sticas do Ping para 64.34.176.148:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
M¡nimo = 557ms, M ximo = 595ms, M‚dia = 573ms

C:\Documents and Settings\USUARIO>ping uosecondage.com

Pinging uosecondage.com [64.34.176.148] with 32 bytes of data:

Reply from 64.34.176.148: bytes = 32 time = 595ms TTL = 111
Reply from 64.34.176.148: bytes = 32 time = 557ms TTL = 115
Reply from 64.34.176.148: bytes = 32 time = 581ms TTL = 115
Reply from 64.34.176.148: bytes = 32 time = 559ms TTL = 115

Ping statistics for 64.34.176.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 557ms, maximum = 595ms M, M, day = 573ms

The tracert is pretty damn strange. No idea of what happened. I tried even to disable the firewall.

Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

Rastreando a rota para uosecondage.com [64.34.176.148]
com no m ximo 30 saltos:

1 * * * Esgotado o tempo limite do pedido.
2 * * * Esgotado o tempo limite do pedido.
3 * * * Esgotado o tempo limite do pedido.
4 * * * Esgotado o tempo limite do pedido.
5 * * * Esgotado o tempo limite do pedido.
6 * * * Esgotado o tempo limite do pedido.
7 * * * Esgotado o tempo limite do pedido.
8 * * * Esgotado o tempo limite do pedido.
9 * * * Esgotado o tempo limite do pedido.
10 * * * Esgotado o tempo limite do pedido.
11 * * * Esgotado o tempo limite do pedido.
12 * * * Esgotado o tempo limite do pedido.
13 * * * Esgotado o tempo limite do pedido.
14 * * * Esgotado o tempo limite do pedido.
15 * * * Esgotado o tempo limite do pedido.
16 * * * Esgotado o tempo limite do pedido.
17 212 ms 211 ms 213 ms 64.34.176.148

Rastreamento conclu¡do.

C:\Documents and Settings\USUARIO>

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

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

Tracing route to uosecondage.com [64.34.176.148]
m with the maximum of 30 hops:

1 * * * timed request.
2 * * * timed request.
3 * * * timed request.
4 * * * timed request.
5 * * * timed request.
6 * * * timed request.
7 * * * timed request.
8 * * * timed request.
9 * * * timed request.
10 * * * timed request.
11 * * * timed request.
12 * * * timed request.
13 * * * timed request.
14 * * * timed request.
15 * * * timed request.
16 * * * timed request.
17 212 ms 211 ms 213 ms 64.34.176.148

Tracking fisinhed.

C: \ Documents and Settings \ USER>

Anyway, thank you for the help!

[Soul]

czech republic here with 11O ms

[Chaos]

Hrmm with logs like that do me a fav and repeat process pinging http://www.google.com.br/

and post

[pussinboots]

No translation this time... its quite understandable I think.

Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\USUARIO>ping http://www.google.com.br

Disparando contra http://www.l.google.com [64.233.163.104] com 32 bytes de dados:

Resposta de 64.233.163.104: bytes=32 tempo=22ms TTL=53
Resposta de 64.233.163.104: bytes=32 tempo=22ms TTL=53
Resposta de 64.233.163.104: bytes=32 tempo=22ms TTL=53
Resposta de 64.233.163.104: bytes=32 tempo=22ms TTL=53

Estat¡sticas do Ping para 64.233.163.104:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um n£mero redondo de vezes em milissegundos:
M¡nimo = 22ms, M ximo = 22ms, M‚dia = 22ms

C:\Documents and Settings\USUARIO>

C:\Documents and Settings\USUARIO>tracert http://www.google.com.br

Rastreando a rota para http://www.l.google.com [64.233.163.104]
com no m ximo 30 saltos:

1 * * * Esgotado o tempo limite do pedido.
2 * * * Esgotado o tempo limite do pedido.
3 * * * Esgotado o tempo limite do pedido.
4 * * * Esgotado o tempo limite do pedido.
5 * * * Esgotado o tempo limite do pedido.
6 * * * Esgotado o tempo limite do pedido.
7 * * * Esgotado o tempo limite do pedido.
8 * * * Esgotado o tempo limite do pedido.
9 * * * Esgotado o tempo limite do pedido.
10 * * * Esgotado o tempo limite do pedido.
11 * * * Esgotado o tempo limite do pedido.
12 22 ms 22 ms 22 ms bs-in-f104.1e100.net [64.233.163.104]

Rastreamento conclu¡do.

C:\Documents and Settings\USUARIO>

The ping is way better, but the tracert seems to be the same thing.

[orionsune]

When traceroute shows the no replies like you have, means the ping (icmp) packet is being denied a return path to your computer. Most likely a router has poor implementation of their tcp/ip stack. Specifically this can happen whan a router sets TTL of an ICMP echo to be the same as the residual TTL of the ICMP query. This means that the ICMP echo will be dropped by some router in the return path, until such time as the originating traceroute program has increased the TTL on the query packet to account for the number of hops in the return path as well as the outward path. This fools the traceroute program into inventing hops that do not reply.

Bottom line is traceroute will not help you troubleshoot this issue.

However you can go to http://visualroute.visualware.com/ and select any region in the US, and it will give you a visual traceroute back to your computer. Try all the different regions and see what kind of ms you get.

[pussinboots]

Sorry for the delay.

So, in this website, I've got some pretty good results. A quite small numer of jumps, most time 9 - 12 jumps, the latency never goes over 180...

I think that the problem is maybe my lan connection, dunno. I have a wireless router, and a modem. This modem has a free connection zone(DMZ) with the wireless, and the wireless is the one that blocks the ports and everything.

Maybe something in this connection is messing things up...

Thanks!

[Derrick]

I've heard many reports of high latency related to wireless lans. If possible, I'd recommend trying a wired connection and at least see if it makes a difference.