Connection Issues
PlatinumBub
Hello there everyone! I'm having a lot of trouble connecting to GW all of a sudden. It was working fine until I downloaded the newest patch earlier this morning, and now it just sits at the "Connecting to ArenaNet" screen. I've made sure my ports are open, I've tried resetting WinSock, uninstalling/reinstalling, deleting the DAT file, made sure the firewall was disabled and Guild Wars was on the exceptions list, and even writing to ArenaNet. Still though, NOTHING. The strange this is that my friend and I both play on the same router / modem and his is working fine. So if anyone out there has any tips, tricks, or suggestions please let me know ASAP! Thank you!
cyber88
I am having the same issue with you. I was getting lagged out so much that I could even play. After the update, I couldn't even go in.
wind fire and ice
Just wait-it'll get better..just after update lags,every one gets 'em.
Rolain
Had the same problem a few hours ago on the server, probably all of the halloween content.
blackmage_z
Usually the inability to connect to GW that I have seen on the forums are related to either NOD32 blocking the patching process or a corrupt .dat file.
If you have NOD32 be sure that it hasn't blocked GW. Try searching the forums for the various NOD32 "can't connect" posts or give the support site a try:
http://eu.plaync.com/eu/help/support-doc/doc_6347/
If you don't have NOD32 try putting your current gw.dat file in another folder and see if you connect to GW. If it connects then try putting the gw.dat back to see if a corrupt file is the issue.
If these don't solve the problem then open a support ticket to see if they have any ideas.
If you have NOD32 be sure that it hasn't blocked GW. Try searching the forums for the various NOD32 "can't connect" posts or give the support site a try:
http://eu.plaync.com/eu/help/support-doc/doc_6347/
If you don't have NOD32 try putting your current gw.dat file in another folder and see if you connect to GW. If it connects then try putting the gw.dat back to see if a corrupt file is the issue.
If these don't solve the problem then open a support ticket to see if they have any ideas.