Showing Posts For Kitten Kong.6384:
Good luck getting anyone to acknowledge the problem or even more that it’s them at fault.
Check some of the other many posts regarding lag incl. some of the ones I’ve posted in. Many things to check/try. If one works for you W00T!
Only came on forums tonight because I noticed the tell tale sign’s of a monumental lag fest starting up again….. Here we go again #HWG
(edited by Kitten Kong.6384)
No worries – we all good
Quick update. Logged on at 18:00 GMT and everything running like a dream. All toons in all maps launched pretty much instantly and were 100% responsive. Me = Happy Camper!
Naively started mapping Gendarran Fields, hoping a miracle had taken place, until bang on 18:30 – and I do mean bang on to the second – my 1st skill stopped responding. Ping shot up from 52 to over 4000. Disconnected – Game unplayable. No toon on any map will load.
Immediate thought – somewhere in the chain is throttling connections and traffic shaping. I’m thinking that unfortunately GW2’s TCP stream either registers as a torrent or something else that an ISP is blocking/shaping VERY badly.
Even forcing port 443 or 80 over the past days makes no difference to this.
Going to delve deeper.
In response to MTU – have been doing some thinking on this. Will come back with numbers, test results and thoughts in a bit.
ciow,
I’m currently forcing the game to run on port 443
What appears to be happening is that the responses from the server are becoming very slow which causes the guild was application to get confused and communication starts to break up, this causes excessive lag, an inability to cast skills or do anything server side, and ultimately losing connection.
This suggests that the problem is with the GW2 server and not with EE in my case.
It would be interesting to see if anyone else could find similar results.As always all of my information is there if people want to add information or help prove/disprove my theory.
Spot on. I found exactly the same about 2 years back and posed similar traces into the thread that led me here ‘Connection error 7:11:3:191:101 [merged]’.
Example of the loss with my Guardian in Diessa:
24 0.697144000 206.127.146.50 192.168.0.200 TCP 75 [TCP Previous segment not captured] dtspcd > 51471 [PSH, ACK] Seq=713 Ack=5 Win=512 Len=21
25 0.697205000 192.168.0.200 206.127.146.50 TCP 66 [TCP Dup ACK 23#1] 51471 > dtspcd [ACK] Seq=5 Ack=650 Win=251 Len=0 SLE=713 SRE=734
26 0.767133000 206.127.146.50 192.168.0.200 TCP 204 dtspcd > 51471 [PSH, ACK] Seq=734 Ack=5 Win=512 Len=150
27 0.767209000 192.168.0.200 206.127.146.50 TCP 66 [TCP Dup ACK 23#2] 51471 > dtspcd [ACK] Seq=5 Ack=650 Win=251 Len=0 SLE=713 SRE=884
28 0.951195000 206.127.146.50 192.168.0.200 TCP 99 [TCP Previous segment not captured] dtspcd > 51471 [PSH, ACK] Seq=941 Ack=5 Win=512 Len=45
29 0.951294000 192.168.0.200 206.127.146.50 TCP 74 [TCP Dup ACK 23#3] 51471 > dtspcd [ACK] Seq=5 Ack=650 Win=251 Len=0 SLE=941 SRE=986 SLE=713 SRE=884
30 0.988435000 206.127.146.50 192.168.0.200 TCP 390 [TCP Retransmission] dtspcd > 51471 [PSH, ACK] Seq=650 Ack=5 Win=512 Len=336
31 0.988560000 192.168.0.200 206.127.146.50 TCP 66 51471 > dtspcd [ACK] Seq=5 Ack=986 Win=256 Len=0 SLE=713 SRE=884
32 1.002468000 192.168.0.200 206.127.146.50 TCP 58 51471 > dtspcd [PSH, ACK] Seq=5 Ack=986 Win=256 Len=4
Actually managed to log into LA last night where I was 1 of about 20 people there. Everything ran perfectly. Switched to Bloodtide, Queensdale, Citadel etc. and boom. All traces showing exactly the same against each of the respective servers.
In game ping on Options screen was showing well over 200 and oddly on Bloodtide 0 where it remained frozen till I gave up.
This is starting to worry me. I might actually have to find something worthwhile to do with my evenings instead
Happy to provide logs for any map to assist if support need them.
cheers and nice work!