Showing Posts For Cuatroku.2765:
The fact that using a VPN solves these issues proves that IP identification is the root of this problem, unfortunately it seems that the coders are on vacation or not at their desks to work on an answer to a problem which is not limited to a small number of customers. Personally I do not want to start using a VPN or a proxy just to circumnavigate this problem, I do not have internet problems at my location and my authorised IP should be sufficient to access all areas of the game.
I play wvw on Tarnished Coast, currently I am unable to get in to Eternal Battlegrounds or sell items correctly on the trading post, i am not aware if issues regarding other maps are affecting me as Divinity’s Reach, Lions Arch are working normally.
My issues started with the “fix” patch of August 6th, on the first log in after update I got an error message saying I should contact Customer Support, however the subsequent log in attempt was successful so all appeared fine.
Unfortunately for me getting in to Jade Quarry borderlands was not possible on August 7th but then the next day I could not access Eternal Battlegrounds instead and that is the situation up to the present. Clearly, as a wvw player not able to access EB, my game is broken, all I can do is play EoTM until the problem is resolved. Nightmare!
It is apparent that the issue originated with the recent update and has affected significant numbers of players globally and across the entire game.
Like a ghost in the machine this is a problem that is difficult to isolate as it affects different clients in a non uniform manner and can be intermittent. My guess is that there is a conflict in the IP permissions and paths that allow clients to communicate with the servers and their partitions within the game architecture itself.
People are reporting that their friends can see their characters appearing in the locations yet their own computers are not receiving the return packets that put them in game and they subsequently time out receiving the ubiquitous error code. Also if you can resolve the issue using a VPN then an IP permission path problem would seem to be the cause. Someone suggested a corrupt IP database , this is possible as in my case the issues started upon reregistration of my client after the fix update.
Proving chaos theory here, a tiny piece of code in the wrong place has impacted massively throughout the GW2 universe, I do hope you techy dudes are working on this over the weekend as it is a ballache for all of us affected as I’m sure you realize.
Good luck and peace to you.