dabsch.6893

I think I found a fix for the issue on my system: use command line argument to make the gw2 client use port 80 instead of 6112 which it uses normally. https://wiki.guildwars2.com/wiki/Command_line_arguments you can read up on it there. basically add "-clientport 80" to your shortcut.

yes, I am getting the same impression. I play on the shiverpeak server one of the 4 or 5 servers that is being listed as "full". I get immediate timeouts in cantha 90% of the time. I can play in other regions for longer times - just did my daily earlier... but even in PoF or core areas I get a timeout when I move to distinct areas on a map. I have not been able to deduct a pattern here yet so far. Doubt I even can on my own. Arenanet should be seeing this on their end. Dont want to be toxic or anything, but after support also didn't care about it: yeah, I think there is no fix coming. maybe it will resolve itself when player numbers go down again. It's a real let down for me, not gonna lie.

Bought the EoD Expansion and installed the entire game fresh: I immediately time out with error code=7:11:3:202:101 on the new Cantha map. I don't get these timeouts in Lion Arch. It also seems to not happen in some of the regions of the first new EoD area... but well... If I want to actually play the expansion I obviously have to move from that and then I timeout again, on the same map. Anybody got some suggestions? I literally cannot start playing the expansion. I never had this error before on this hardware (which had not changed since I had the game installed last)