Hey everyone,
Everyone has been posting some great suggestions for this error. Unfortunately this is another one of those situations in which this error can be caused from a number of different things. If you’re one of the unlucky ones who may be seeing this error, please run through the following checklist:
1. Is your connection stable? Run a trace to the Guild Wars 2 servers to see if there is any packet loss found throughout your connection en route to the game servers as a stable connection can cause this error.
2. On that note, a supported connection method is also necessary and so if you’re on a mobile, satellite. or dial-up connection, you will also likely encounter this error. In order to play Guild Wars 2, you must have a broadband internet connection.
3. Is your router properly configured to connect to Guild Wars 2? The easiest way to rule out any issues with the router would be to bypass it completely and connect directly to your modem.
If you have a router/modem combo and so a bypass simply isn’t possible, you will want to ensure that TCP ports 80, 443, 6112 and port 6600 are fully unrestricted and accessible, both inbound and outbound.
If you are connecting to Guild Wars 2 while on a campus, military, or business network, please check with your network’s administrator to verify that these ports are fully opened and unrestricted. If you are on a home Local Area Network (LAN), you will want to make sure that your network’s hardware is configured properly.
As someone else mentioned, you will also want to check your router’s security settings to ensure no router firewalls are blocking your connection to the client.
4. Ensure no security software or conflicting applications may be interfering with the client. The easiest way to rule out conflicting background applications is via MSCONFIG.
5. Be sure that you do not have any malware or spyware hanging around your system.
6. A Winsock reset is also a good way to go in troubleshooting this issue.
7. Lastly, a simple DNS flush, or even using Google’s Public DNS has been known to resolve this particular issue.
Should the above not help or should anyone have any additional questions or concerns, please do submit a support ticket and we’d be happy to be of further assistance!