Showing Posts For Lagos.6938:
I’d prefer if it stayed toughness (letting us have cool tank builds) and seeing a new, viable +heal set without +toughness.
The Diessa Plateau event ‘Defend Bloodsaw Mill from the Flame Legion’ has been stuck at wave 4/8 for a few hours now. The next wave of flame legion never spawns. This prevents the meta from advancing which prevents various things (e.g. preventing us from getting to Font of Rhand, preventing us from finishing Mawdry, etc.).
I don’t know how long this has been going on but it’s been hours! I had time to go finish Drytop and come back. Someone else says they had time to run a dungeon and cap Leatherworking. No one can find a different version of the map to join.
Attached is a picture of me right now. T_T Please help.
Same issue. Please fix this. I love the hairstyle but can’t use it.
Just to update: This is still happening after the patch. Just hit me tonight.
Taimi froze again—this time near the final bend in the tunnel before the control room. This is the third time she’s frozen for me during this quest. >_<
In the past, people said that it helps if you let her always go in front. Did that this time and she still froze; I think it’s just a placebo.
It wouldn’t be so painful if it weren’t such a tedious mission to repeat: ‘Okay, Guild Wars 2. What now?’ ‘Kill this large group of Chak.’ ‘Phew. That was a pain. Now what?’ ‘Do that about 5 more times.’ ‘……’ ’Don’t worry: I’ll give you breaks in the form of long dialogue you get to sit through.’
Doing it a fourth time… I think I want to cry.
What about Charr Female? She was my favorite VA, and still has a similar cadence but sounds a bit ‘off’. Is it someone else or did Kate Miller have a cold that recording day?
Just heard back from Sonic.net. Their ops have unblocked the server so this shouldn’t hit anyone else on Sonic.net.
Tonight, I appear to only have problems connecting to anet’s login servers. Specifically, from gw2.exe -diag:
cligate.101.NCPlatform.net. 209.204.190.68:6112 - connect failed
das moran, the problem is that 209.204.190.68 isn’t the right ip address for cligate.101.NCPlatform.net. The correct ip address of cligate.101.NCPlatform.net should look like 64.25.40.x where x is some number.
209.204.190.68 is the ip address of a server sonic.net’s DNS server is sending people to if it thinks that a hostname is used for phishing. If you open ‘cligate.101.NCPlatform.net’ in your webbrowser on sonic.net right now, you’ll see a big warning.
The problem is that cligate.101.NCPlatform.net has been flagged as a malware site by sonic.net (probably eroneously :P). Until they fix it, your best workaround is not to use sonic.net’s DNS servers. I can confirm this worked for me.
If you want to use Google’s public DNS servers, they have instructions here: https://developers.google.com/speed/public-dns/docs/using
Vilkata, it’s possible for two computers on the same home network to use different DNS servers to translate the same name. If you can check your network setting, you’ll probably see that the two computers are using different servers.
Anyway, I changed my DNS server to 8.8.8.8 and was able to connect. Instructions for doing so on windows 7 are here: http://windows.microsoft.com/en-us/windows7/change-tcp-ip-settings
sonic.net’s customer support was closed, but I left a message and filled in the form. Good luck, guys.
Okay. I think I got it. ‘dig cligate.101.NCPlatform.net’ on my machine yields 209.204.190.68. This isn’t the right IP. It’s the IP for dns-blocked.sonic.net. Apparently sonic.net thinks that this hostname is associated with a phishing scheme. You can put ‘cligate.101.NCPlatform.net’ in your web browser and you’ll get to a phishing warning site with a mousetrap on it.
The reason I could connect on OS X is because on my mac, I’m using Google’s public DNS server 8.8.8.8.
I’m going to call Sonic.net now to ask them to fix this. In the meantime you might want to do the following:
1. Fill out the form on cligate.101.NCPlatform.net (it will only appear for sonic.net users) or
2. Change your dns server to 8.8.8.8
lol, because I live in San Francisco and use Sonic.net. Looks like we have the same exact problem.
Okay, I ran the client with -diag, and got these results (edited down slightly):
================ = Discovering external address ================
Current IP Address: (Hiding this since I’m posting on a forum)Section completed in 0.16 seconds
================ = Checking server connectivity ================
Section completed in 0.00 secondsDiag.ArenaNetworks.com
64.25.39.21:80 – connect succeeded
64.25.39.21:6112 – connect succeeded
206.127.158.31:80 – connect succeeded
206.127.158.31:6112 – connect succeededSection completed in 0.34 seconds
assetcdn.101.ArenaNetworks.com.
173.228.66.10:80 – connect succeeded
173.228.66.8:80 – connect succeededSection completed in 1.08 seconds
auth1.101.ArenaNetworks.com.
64.25.38.72:6112 – connect succeeded
64.25.38.51:6112 – connect succeeded
64.25.38.172:6112 – connect succeeded
64.25.38.171:6112 – connect succeeded
64.25.38.54:6112 – connect succeededSection completed in 0.30 seconds
auth2.101.ArenaNetworks.com.
206.127.159.109:6112 – connect succeeded
206.127.159.108:6112 – connect succeeded
206.127.159.77:6112 – connect succeeded
206.127.146.74:6112 – connect succeeded
206.127.159.107:6112 – connect succeeded
206.127.146.73:6112 – connect succeededSection completed in 3.38 seconds
cligate.101.NCPlatform.net.
209.204.190.68:6112 – connect failedSection completed in 10.25 seconds
What’s interesting is I can ping 209.204.190.68 just fine. But if I try to netcat port 6112 of it (basically just opening a socket), no connection is found. I guess I’ll try calling sonic.net if it’s not fixed in the morning.
Hi, Izu.
I have OS X and Windows on the same computer. It connected under OS X but still does not on Windows. My problems also started around 10 PM PST.
I’m running the client with -repair now to see if something was corrupted, but I doubt that’s it. Most odd.
Are you living in San Francisco and use Sonic.net for internet?
Wow. Yes, I am. That’s a little creepy.
Anyway, I could connect by rebooting into OS X and using my Mac client on the same computer. Maybe the mac client uses different servers, though.
Hi, Izu.
I have OS X and Windows on the same computer. It connected under OS X but still does not on Windows. My problems also started around 10 PM PST.
I’m running the client with -repair now to see if something was corrupted, but I doubt that’s it. Most odd.
Been getting this on Windows. Logged out around 5:30 PM PST just fine. Tried to log in at 10 PM and couldn’t. Interestingly, running GW2 on OS X on the same box works fine.
Curiously enough, booting from Windows into OS X on the same machine (with the same ip after the restart) my OS X client can connect just fine.
Getting the same problem. I could log in just fine a few hours earlier. All other games and network operations work fine.
1. My computer hasn’t restarted and still has the same LAN ip. I also tried restarting the box just in case Windows was the problem.
2. Didn’t change any settings on my router.
3. I tried disabling Windows Firewall.
4. I tried the clientport suggestion.
5. This is a home network, not campus, hotel, etc.
Still nothing. Please help.
Build is 26150
Error Code is 42:0:9001:4137 at the moment.