error 42:0:9001:3927
Hi Sumarus – At what point do you receive this error? How long have you been getting this error and how often?
I have been getting this same error whenever I try to login to the game client. It worked fine last night but today it hasn’t let me on at all.
edit:
The editing a shortcut to “/clientport 80” seems to have fixed it. Either that or whatever did has great timing. Thanks!
(edited by LONGTIME.8425)
Thanks LONGTIME! I’m glad to hear that this workaround resolved the issue.
@Samarus – If you’re still receiving this error message, I’d like for you to try the clientport 80 workaround.
To do this:
1. Navigate to your Guild Wars 2 installation folder.
2. Right-click on “GW2.exe” and select “Create Shortcut.”
3. Rename this shortcut to “Guild Wars 2 Port Test.”
4. Right-click on this shortcut and select “Properties.”
5. Edit the “Target” line to include /clientport 80 at the end.
Note: Please make sure /clientport 80 is outside of the quotes
Correctly Formatted Example: “C:\Games\Guild Wars 2\GW2.exe” /clientport 80
Incorrectly Formatted Example: “C:\Games\Guild Wars 2\GW2.exe /clientport 80”
6. Once completed, click “Ok” to save your changes.
If you get an error trying to save, your target line may not have the correct format. Please try step 5 again.
7. Double click “Guild Wars 2 Port Test” and try connecting again.
Wow! I have been trying all sorts of workarounds to get around my ISP blocking port 6112. But this /clientport 80 worked for me.
I can finally play the game!
Thanks
Was playing fine but 5 minutes ago got kicked with error 42 and nothing works…
I’ve got the same problem as Brimlor – dc’d with an error 42, and since I can’t reconnect. Tried the port 80 rename fix mentioned above, but it hasn’t worked…
I also got kicked off about ten minutes ago error 42 saying unable to gain acces to login server what am i supposed to do now i can still log in but i cant press play when my characters come up
Same for me as well
twitter: Guild Wars 2 ?@GuildWars2
We are aware of login issues and are investigating.
by the way: im having the same problem but it should be fixed sooner or later
Same here as well. Kicked 10 min ago. Maybe the servers just went down.
Yup same here, yea looking at the number of ppl saying they ahve the same issue im hoping its a server problem and get fixed soon
I started having this problem for the first time this morning. After much searching I found this thread and the clientport 80 fix worked.
This clientport 80 fix – what exactly is it telling the client to do? Listen on port 80, or target port 80 for outbound connections?