test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Neverwinter Discussion › Bug Reports (PC)

Being Blocked by Verizon

foxygrandpa83foxygrandpa83 Member, Neverwinter Beta Users Posts: 4 Arc User
edited August 2013 in Bug Reports (PC)
I have been trying to log in all weekend, scouring message boards like crazy, and trying all sorts of solutions like flushing my DNS, resetting the router/modem, etc. Result: Appears that Verizon has blocked the game!

I'm having no other connectivity issues on my FiOS and even tried it on the other computers in my home.

This is my pcl.log:
130803 05:53:30 1 [1]: Using HTTP patching: server akamai.nwhttppatch.crypticstudios.com port 80 prefix Night
130803 05:53:33 2 [1]: Syncing required files
130803 05:53:33 3 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/bins.hogg
130803 05:53:33 4 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/bins2.hogg
130803 05:53:33 5 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/character.hogg
130803 05:53:33 6 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/object.hogg
130803 05:53:33 7 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/sound.hogg
130803 05:53:33 8 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/texture.hogg
130803 05:53:33 9 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/texture2.hogg
130803 05:53:33 10 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/data.hogg
130803 05:53:33 11 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/exes.hogg
130803 05:53:35 12 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:53:35 13 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:53:35 14 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:53:36 15 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:53:42 16 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:58:14 17 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Server requested close(10054:Connection reset by remote host)
130803 05:58:15 18 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:58:25 19 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Disconnect Error: 10054(10054:Connection reset by remote host)
130803 05:58:25 20 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:58:33 21 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: socket was shutdown(10060:Timeout on connection attempt)
130803 05:58:34 22 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:58:35 23 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: socket was shutdown(10060:Timeout on connection attempt)
130803 05:58:36 24 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Server requested close(0:No error)
130803 05:58:36 25 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 05:58:36 26 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:00:58 27 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Disconnect Error: 10054(10054:Connection reset by remote host)
130803 06:00:58 28 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:07:15 29 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Server requested close(0:No error)
130803 06:07:59 30 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: socket was shutdown(10054:Connection reset by remote host)
130803 06:09:21 31 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:09:45 32 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:13:27 33 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Disconnect Error: 10054(10054:Connection reset by remote host)
130803 06:13:27 34 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:13:40 35 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Server requested close(0:No error)
130803 06:13:42 36 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:13:55 37 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: Server requested close(0:No error)
130803 06:13:56 38 [1]: HTTP patching connected to akamai.nwhttppatch.crypticstudios.com:80
130803 06:16:37 39 [1]: HTTP patching disconnected from akamai.nwhttppatch.crypticstudios.com:80: socket was shutdown(10060:Timeout on connection attempt)
130803 17:51:57 1 [1]: Using HTTP patching: server akamai.nwhttppatch.crypticstudios.com port 80 prefix Night
130803 17:52:02 2 [1]: Syncing required files
130803 17:52:02 3 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/bins.hogg
130803 17:52:02 4 [1]: Scanning hogg E:/Cryptic Studios/Neverwinter/Live/piggs/bins2.hogg

AND this running Tracert:

C:\Windows\system32> tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 5 ms L100.LSANCA-VFTTP-133.verizon-gni.net [173.67.10
8.1]
3 7 ms 7 ms 7 ms G0-10-2-0.LSANCA-LCR-22.verizon-gni.net [130.81.
140.26]
4 6 ms 6 ms 6 ms ae4-0.LAX01-BB-RTR2.verizon-gni.net [130.81.199.
114]
5 78 ms 78 ms 78 ms 0.xe-4-1-2.XL4.BOS4.ALTER.NET [152.63.5.186]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I can't even download the game from http://download.perfectworld.com/nw/neverwinter_setup.exe because the site "cannot connect"

Other than playing using a VPN, what can I do? There has got to be solution to this! I KNOW THERE ARE OTHERS WHO ARE HAVING THE SAME ISSUES!
Post edited by foxygrandpa83 on

Comments

  • fireyquestfireyquest Member, Neverwinter Beta Users, Neverwinter Guardian Users Posts: 12 Arc User
    edited August 2013
    This might by my problem. I can't get past the Cryptic Logo. It keeps telling me it can't connect with the auto patch or whatever. I have Verizon DSL. WTF? Why would Verizon be blocking this game?
  • foxygrandpa83foxygrandpa83 Member, Neverwinter Beta Users Posts: 4 Arc User
    edited August 2013
    I go to the launcher and it immediately tells me "Unable to authenticate:" when I log in. I read on other threads and also on the Star Trek Online forum that all the issues are from the Verizon's end since they are having problems with Cogent. This is so stupid that I want to switch to Time Warner.
  • fireyquestfireyquest Member, Neverwinter Beta Users, Neverwinter Guardian Users Posts: 12 Arc User
    edited August 2013
    Downloaded VPN and I can now play. Verizon is blocking the game definitely.
  • foxygrandpa83foxygrandpa83 Member, Neverwinter Beta Users Posts: 4 Arc User
    edited August 2013
    My launcher is finally running the patch with the VPN but we should not had to resort to this. I already complained to Verizon and I hope others also do the same. We pay them for the service so why are they pulling this HAMSTER of blocking sites from us? I hope Perfect Earth can get this resolved with them soon!
  • justicebringer3justicebringer3 Member Posts: 39 Arc User
    edited August 2013
    I don't believe they were blocking the game, but rather Cogent was blocking them.
Sign In or Register to comment.