Tremendous Lagspikes alongside "No Response From Server" since 2.0

[MaryJoana]

I have some huge FPS drops and lags since 2.0. I disconnect 3-4 times every game. At some point the game just stops, as if paused, but animations keep playing (walking animations), then I get the "connection problem" icon on the left, and finally "No Response From Server" after which I can't even log in for 5-10 seconds.

Additionally I have the feeling the loading screen has gotten a lot slower.

I read something about FPS drops in the hotfixes thread in Bug Reports, something about Catalyst Control Center 10.8 being an issue, and rollback to 10.4 should fix that, so I will try that, however it seems to me there is a deeper underlying issue here.

I am doubting it is my internet (however it could take it's part in it), as my friend is having the same thing.

Regarding the information you need, tell me what you need me to do, and I'll get on it asap. Got time on my hands anyway.

[IAmRoot]

I'll need your console.log, system specs, and msinfo32, and results from http://forums.heroesofnewerth.com/wiki/index.php/Network_Quality_Diagnostics.

[MaryJoana]

Sorry for the double packing of the console.log, but simple zip wouldn't fix it. I love winrar for being superior.

Anyway, msinfo32 and console.log are attached, my system specs are contained in the msinfo32, as far as I understand, but if you need them seperately, tell me.

As for the ping analysis:

ping -l 1300 -n 500 213.163.86.218 (NL Server):

Ping statistics for 213.163.86.218:
Packets: Sent = 500, Received = 499, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 184ms, Average = 28msping -l 1300 -n 500 213.163.67.69 (EU Server):

Ping statistics for 213.163.67.69:
Packets: Sent = 500, Received = 499, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 228ms, Average = 27msping -l 1300 -n 500 188.40.106.82 (DE Server):

Ping statistics for 188.40.106.82:
Packets: Sent = 500, Received = 492, Lost = 8 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 236ms, Average = 39msAs you can see I am spiking real hard, and have the occasional packet loss. I am running ping tests to amd.com, google.de and heise.de, which I will post in a second (When they're done).

EDIT: Tell me anything else you may need. Traceroutes, or the likes.

[MaryJoana]

ping -l 1300 -n 500 google.de:

Ping statistics for 66.102.13.103:
Packets: Sent = 500, Received = 499, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 419ms, Average = 43ms

ping -l 1300 -n 500 amd.com

Ping statistics for 163.181.249.32:
Packets: Sent = 500, Received = 498, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 161ms, Maximum = 595ms, Average = 185ms

ping -l 1300 -n 500 heise.de:

Ping statistics for 193.99.144.80:
Packets: Sent = 500, Received = 498, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 445ms, Average = 123ms

Also immense spiking, so I am assuming it's nothing to do with HoN?

[MaryJoana]

tracert 213.163.67.69 (EU Server)

Tracing route to hosted-by.i3d.net [213.163.67.69] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 7 ms 3 ms 192.168.1.1
3 11 ms 9 ms 9 ms 10.239.0.1
4 10 ms 9 ms 9 ms 213.51.151.113
5 17 ms 11 ms 18 ms csw2-pc156.tilbu1.nb.home.nl [213.51.151.95]
6 18 ms 20 ms 18 ms asd-tr0409-cr101-ae5-0.core.as9143.net [213.51.158.154]
7 19 ms 19 ms 19 ms ams-ix.ar1.nikhef.i3d.net [195.69.144.162]
8 20 ms 18 ms 20 ms 188.122.95.70
9 30 ms 19 ms 19 ms 188.122.95.83
10 20 ms 30 ms 21 ms hosted-by.i3d.net [213.163.67.69]

Trace complete.tracert 213.163.86.218 (NL Server)

Tracing route to hosted-by.serverboost.com [213.163.86.218] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 5 ms 7 ms 3 ms 192.168.1.1
3 12 ms 8 ms 9 ms 10.239.0.1
4 11 ms 8 ms 11 ms 213.51.151.113
5 12 ms 10 ms 10 ms csw2-pc156.tilbu1.nb.home.nl [213.51.151.95]
6 18 ms 20 ms 29 ms asd-tr0409-cr101-ae5-0.core.as9143.net [213.51.158.154]
7 98 ms 19 ms 31 ms ams-ix.ar1.nikhef.i3d.net [195.69.144.162]
8 28 ms 22 ms 26 ms 188.122.95.66
9 17 ms 19 ms 19 ms 188.122.95.90
10 17 ms 20 ms 19 ms 10ge-1.nlrtd.cs1.as49544.net [188.122.95.36]
11 18 ms 16 ms 17 ms hosted-by.serverboost.com [213.163.86.218]

Trace complete.tracert 188.40.106.82 (DE Server)

Tracing route to static.82.106.40.188.clients.your-server.de [188.40.106.82]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 7 ms 3 ms 192.168.1.1
3 12 ms 9 ms 7 ms 10.239.0.1
4 148 ms 9 ms 9 ms 213.51.151.113
5 10 ms 12 ms 17 ms csw2-pc156.tilbu1.nb.home.nl [213.51.151.95]
6 17 ms 17 ms 13 ms asd-tr0409-cr101-ae5-0.core.as9143.net [213.51.158.154]
7 20 ms 114 ms 34 ms r1ams1.ce.init7.net [195.69.144.210]
8 30 ms 35 ms 30 ms r1fra1.core.init7.net [77.109.128.153]
9 28 ms 30 ms 28 ms gw-hetzner.init7.net [77.109.135.18]
10 33 ms 32 ms 29 ms hos-bb1.juniper2.fs.hetzner.de [213.239.240.243]
11 29 ms 29 ms 29 ms hos-tr3.ex3k8.rz10.hetzner.de [213.239.227.201]
12 57 ms 27 ms 29 ms static.82.106.40.188.clients.your-server.de [188.40.106.82]

Trace complete.

[MaryJoana]

I did a second tracert to 188.40.106.82, while I was pinging all the IPs that came up in the tracert, cause the ping to 10.239.0.1 kept timing out.

This is the result:

tracert 188.40.106.82

Tracing route to static.82.106.40.188.clients.your-server.de [188.40.106.82]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 11 ms 113 ms 192.168.1.1
3 7 ms 7 ms 9 ms 10.239.0.1
4 28 ms 69 ms 13 ms 213.51.151.113
5 185 ms 119 ms 100 ms csw2-pc156.tilbu1.nb.home.nl [213.51.151.95]
6 297 ms 302 ms 51 ms asd-tr0409-cr101-ae5-0.core.as9143.net [213.51.158.154]
7 100 ms 134 ms 123 ms r1ams1.ce.init7.net [195.69.144.210]
8 39 ms 20 ms 47 ms r1fra1.core.init7.net [77.109.128.153]
9 20 ms 24 ms 120 ms gw-hetzner.init7.net [77.109.135.18]
10 29 ms 28 ms 29 ms hos-bb1.juniper2.fs.hetzner.de [213.239.240.243]
11 42 ms 111 ms 118 ms hos-tr3.ex3k8.rz10.hetzner.de [213.239.227.201]
12 87 ms 130 ms 169 ms static.82.106.40.188.clients.your-server.de [188
.40.106.82]

Trace complete.

[MaryJoana]

It is to note though, that pre-2.0 I had no problems whatsoever. And a friend of mine is having the same issue.

[MaryJoana]

I've now pinged all IPs in my Traceroute to the German Server:

Node 1:

Ping statistics for 192.168.0.1:
Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 96ms, Average = 0msNode 2:
Ping statistics for 192.168.1.1:
Packets: Sent = 500, Received = 498, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 354ms, Average = 43msNode 3:

Ping statistics for 10.239.0.1:
Packets: Sent = 500, Received = 0, Lost = 500 (100% loss)Node 4:

Ping statistics for 213.51.151.113:
Packets: Sent = 500, Received = 496, Lost = 4 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 382ms, Average = 58msNode 5:

Ping statistics for 213.51.151.95:
Packets: Sent = 500, Received = 499, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 452ms, Average = 58msNode 6:

Ping statistics for 213.51.158.154:
Packets: Sent = 500, Received = 496, Lost = 4 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 454ms, Average = 61msNode 7:

Ping statistics for 195.69.144.210:
Packets: Sent = 500, Received = 498, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 3662ms, Average = 73msNode 8:

Ping statistics for 77.109.128.153:
Packets: Sent = 500, Received = 493, Lost = 7 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 429ms, Average = 85msNode 9:

Ping statistics for 77.109.135.18:
Packets: Sent = 500, Received = 493, Lost = 7 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 485ms, Average = 86msNode 10:

Ping statistics for 213.239.240.243:
Packets: Sent = 500, Received = 493, Lost = 7 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 3360ms, Average = 100msNode 11:

Ping statistics for 213.239.227.201:
Packets: Sent = 500, Received = 494, Lost = 6 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 3908ms, Average = 97msNode 12:

Ping statistics for 188.40.106.82:
Packets: Sent = 500, Received = 490, Lost = 10 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 438ms, Average = 89ms

[IAmRoot]

Ok, it looks like the problem is happening between node 1 and 2. It looks like this is the router<-->modem connection. Either the cable, your modem, or your router is failing.

[MaryJoana]

I think I found the main problem. There was an IP conflict between the two routers we have, and when I changed my router's IP, the problems resolved.

Weird still, that said friend has the same problem, but nothing changed for him.

[IAmRoot]

I'm glad you got it fixed.

Have your friend post :). Hopefully he'll make as awesome of a post as you did. Seriously, I hate it when people write one line. It wastes so much of my time, and it takes them a lot longer to get their issues fixed.

[MaryJoana]

Actually, nevermind, that was not the problem. It seems it was just not occuring anymore at night.

So where could the problem be =/ DCing constantly again

[IAmRoot]

Well, It's still going to be at the same place. You can run all the tests again if you want to make sure (-n 100 is fine for each step, 500 takes forever).

[MaryJoana]

Well the really weird part is that, when I have these lags, my sound completely studders. Sometimes it plays half a second of the sound that just happened 20-30 times. This made me think maybe I have driver issues, but that doesn't affect the network connectivity. And router problems don't affect the graphic/sound fps, right?

[IAmRoot]

Nope. It could be a driver problem, I suppose. That would be a rare occurrence, though. There's not much else that I can test remotely. It's definitely a general problem with your computer/network, though, and not just HoN.