Lag Complaints Here

[Akilthedestroyer]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\user> tracert 66.135.42.153

Tracing route to 66.135.42.153 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.11.5.193
2 418 ms 68 ms 1 ms 203.171.242.33
3 3 ms 19 ms 3 ms 203.171.240.1
4 38 ms 37 ms 37 ms 172.29.211.109
5 * * * Request timed out.
6 592 ms 309 ms * if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.2
17.17]
7 229 ms 229 ms 229 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.21
7.6]
8 237 ms 261 ms 345 ms if-5-2.tcore1.L78-London.as6453.net [80.231.130.
1]
9 226 ms 431 ms 457 ms if-4-2.tcore1.NJY-Newark.as6453.net [80.231.130.
34]
10 238 ms * 543 ms if-2-2.tcore2.NJY-Newark.as6453.net [66.198.70.2
]
11 230 ms 549 ms 584 ms if-14-14.tcore2.NTO-NewYork.as6453.net [66.198.1
11.126]
12 662 ms 698 ms 641 ms 63.243.128.69
13 430 ms 240 ms 239 ms 209.58.26.86
14 498 ms 411 ms 239 ms pos-1-15-0-0-cr01.newyork.ny.ibone.comcast.net [
68.86.87.121]
15 761 ms 347 ms 270 ms he-0-5-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.88.150]
16 300 ms 302 ms 378 ms he-1-15-0-0-cr01.denver.co.ibone.comcast.net [68
.86.85.114]
17 304 ms 307 ms 379 ms he-2-8-0-0-cr01.dallas.tx.ibone.comcast.net [68.
86.85.218]
18 305 ms 345 ms 439 ms pos-0-9-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.88.198]
19 298 ms 330 ms 535 ms 173.167.58.14
20 * *

[Smashbros]

Originally Posted by EnigmaWave

At least on my machine (Windows 7 64-bit), that's what I'm seeing, yes.

If anyone else on Windows would like to check for this, run Sysinternals TCPView and if you see red and green lines like these that don't go away:

for java.exe with the Nodiatis IP address, that means your computer is reconnecting over and over again.

A single white line with ESTABLISHED means it's working correctly.

i just ran TCPView and have the same thing. but only 1 of each.

[Sexykills]

Originally Posted by EnigmaWave

This is weird.

Wireshark is showing that both client and server are correctly sending "Connection: keep-alive" in their HTTP headers; however, the packet containing the HTTP response from the server has the TCP control flag FIN set. So it appears that the HTTP server is still closing the connection, even though it's not supposed to.

That definitely explains additional latency, especially with SSL enabled as the SSL handshake has to be performed all over again for every connection.

pretty sure thats what i said HERE in post #4 but simpler lol
glitch neads to learn to read laymans o.0

[Enduir]

Originally Posted by zenga

... everyone is having bad routers guys!

If only they had Visa, Paypal and friends in Luxembourg.

[zenga]

Originally Posted by Enduir

If only they had Visa, Paypal and friends in Luxembourg.

hahaha legendary quote