test content
What is the Arc Client?
Install Arc

Unable to authenticate

2»

Comments

  • johnnyquantumjohnnyquantum Member, Neverwinter Beta Users, Neverwinter Hero Users, Neverwinter Guardian Users, Neverwinter Knight of the Feywild Users Posts: 6 Arc User
    edited June 2014
    Same here - all Cryptic games
  • allumbukerallumbuker Member Posts: 2 Arc User
    edited June 2014
  • ambisinisterrambisinisterr Member, Neverwinter Moderator Posts: 10,462 Community Moderator
    edited June 2014
    vasdamas wrote: »
    This one is always a problem. Each time I look at my trace there is always congentco lightened up. The only thing that is.

    What's the deal with them?

    I don't think it is congentco this time. It's a different hub. But Congentco has crappy service and just doesn't care as near as I can tell. They must get complaints from every service around them because it effects a lot of games, streaming services, etc.

    But Cryptic doesn't use congentco as an ISP. It's not a problem they have any control over. Think of the internet as a road and congenco is just a pothole riddled mess some people have to travel through in order to get to Cryptic's ISP. You can complain to congenco to fix their roadway but it is ultimately up to them to care enough that they are hurting everybody who has to use their roads.
  • twoedge1twoedge1 Member, NW M9 Playtest Posts: 79 Arc User
    edited June 2014
    I was noticing connection issues as well this morning.
  • elvenaarelvenaar Member, NW M9 Playtest Posts: 81 Arc User
    edited June 2014
    I don't think it is congentco this time. It's a different hub. But Congentco has crappy service and just doesn't care as near as I can tell. They must get complaints from every service around them because it effects a lot of games, streaming services, etc.

    But Cryptic doesn't use congentco as an ISP. It's not a problem they have any control over. Think of the internet as a road and congenco is just a pothole riddled mess some people have to travel through in order to get to Cryptic's ISP. You can complain to congenco to fix their roadway but it is ultimately up to them to care enough that they are hurting everybody who has to use their roads.

    Well I'm located in the east-Eu, so can say for sure that your US cogentco is not present here, so why do we have any problems?

    BTW rest of my internet works just fine, only Cryptic games are down.
  • twoedge1twoedge1 Member, NW M9 Playtest Posts: 79 Arc User
    edited June 2014
    nevawinna wrote: »
    Is Dragon server in its death throes or what is going on? There's like one minute delay to everything, getting the server not responding message occasionally when I am not just warping and rubberbanding all over the place...

    One of the ISP internet hubs is down. It has nothing to do with the servers.
    You can see my post regarding the issue including the trace here.
    -Ambisinisterr


    This was what I was seeing this morning as well..
  • hexarequiemhexarequiem Member, Neverwinter Beta Users Posts: 3 Arc User
    edited June 2014
    at least with road I can take alternative paths, even if it's longer.
    cogentco can't block every single road to my home now, can they?
  • hetz000hetz000 Member Posts: 0 Arc User
    edited June 2014
    I just tried and have no problems connetcing,and my trace dont show any problems.Im from europe btw.
  • thegrandexenothegrandexeno Member Posts: 239 Bounty Hunter
    edited June 2014
    For me it's the Boston(?) node that DOUBLES my ping
    • Halflingas The Great - Stormwarden HR(60)
  • onodrainonodrain Member Posts: 334 Arc User
    edited June 2014
    I still cannot login to either gateway or game. I am able to login to Diablo3 and GuildWars2. I can ping LA, British Columbia, Austin, and Boston from Dallas whilst maintaining my internet speed per Speedtest.net.
  • ambisinisterrambisinisterr Member, Neverwinter Moderator Posts: 10,462 Community Moderator
    edited June 2014
    Being able to log into another game or ping elsewhere doesn't matter. It is that specific hub which is the current problem and that hub may not be on the route to other servers.

    Go into cmd.exe and type "tracert patchserver.crypticstudios.com" into the command line.

    That's the only valid way to test the connection. Anything else is the equivalent of saying that there's no traffic going to your mother's house so there must be no traffic going to work.

    EDIT - Unsupported claims and off topic rants will not fly with me.
  • hexarequiemhexarequiem Member, Neverwinter Beta Users Posts: 3 Arc User
    edited June 2014
    problem seems to be solved for me, even if it was a bit unstable while logging.
  • onodrainonodrain Member Posts: 334 Arc User
    edited June 2014
    Ok. Not sure how to show the trace on this thread without putting a pic on another site. But my trace show everything ok till perfectworldent-4 (hop 14). Then first trace has * to it, the second and third are 73 and 70 ms each.

    Hop 15 is patchserver2. The first and third trace are * and the second trace is 79 ms

    Hop 16 is final hop to patchserver2 and is 65 66 65 ms
  • ayliffetayliffet Member, Neverwinter Beta Users, Neverwinter Hero Users, Neverwinter Knight of the Feywild Users Posts: 2 Arc User
    edited June 2014
    Seems to be good for me as well. The tracert I did just before logging in seemed all cleaned up as well. Logged in quick, fingers crossed, it will last for a few hours, :)
  • twoedge1twoedge1 Member, NW M9 Playtest Posts: 79 Arc User
    edited June 2014
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms myrouter.home []
    2 31 ms 29 ms 35 ms L100.DLLSTX-VFTTP-61.verizon-gni.net [71.123.232.1]
    3 9 ms 6 ms 10 ms G0-9-3-3.DLLSTX-LCR-21.verizon-gni.net [100.41.202.76]
    4 37 ms 34 ms 61 ms ae9-0.DFW9-BB-RTR1.verizon-gni.net [130.81.162.152]
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 97 ms 50 ms 49 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
    10 51 ms 49 ms 50 ms 0.ge-3-1-0.XL3.BOS4.ALTER.NET [152.63.20.217]
    11 50 ms 49 ms 50 ms 0.xe-8-3-0.GW15.BOS4.ALTER.NET [152.63.24.38]
    12 50 ms 49 ms 50 ms internap-gw.customer.alter.net [152.179.134.214]
    13 52 ms 52 ms 52 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    14 49 ms 52 ms 51 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    15 58 ms 59 ms 56 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.


    This seems to happen every couple of months with verizon. ae9-0.DFW9-BB-RTR1.verizon-gni.net was the same failure point last time as well. It took a couple of days before things started working again. Anybody using Verizon in the DFW area(Dallas/Fortworth) is most likely going to have a problem.
  • onodrainonodrain Member Posts: 334 Arc User
    edited June 2014
    Ok...figured out the copy and paste. Here is my trace.

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    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
    2 * * * Request timed out.
    3 10 ms 9 ms 8 ms xe-0-0-2.196.aggr09.fscotx.grandecom.net [72.48.
    173.149]
    4 9 ms 10 ms 9 ms xe-0-0-1.0.aggr09.wacotx.grandecom.net [24.155.1
    21.54]
    5 11 ms 10 ms 10 ms ae4-0.core01.gf01.dllstx.grandecom.net [24.155.1
    21.6]
    6 11 ms 10 ms 11 ms ge-11-3-2.mpr1.dfw1.us.above.net [64.124.200.249
    ]
    7 12 ms 10 ms 11 ms xe-0-2-0.cr2.dfw2.us.above.net [64.125.27.214]
    8 33 ms 19 ms 21 ms ae2.cr2.iah1.us.us.above.net [64.125.21.62]
    9 52 ms 70 ms 47 ms ae14.cr2.dca2.us.above.net [64.125.21.53]
    10 58 ms 61 ms 116 ms xe-1-1-0.mpr4.bos2.us.above.net [64.125.24.117]

    11 63 ms 77 ms 59 ms ae2.mpr3.bos2.us.above.net [64.125.25.41]
    12 57 ms 59 ms 57 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
    8.184.110.70]
    13 62 ms 63 ms 64 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
    1]
    14 * 73 ms 70 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    15 * 79 ms * patchserver2.crypticstudios.com [208.95.185.41]

    16 65 ms 66 ms 65 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.

    C:\WINDOWS\System32>
  • noerqnoerq Member, Neverwinter Beta Users Posts: 26 Arc User
    edited June 2014
    Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41] über maximal 30 Abschnitte:

    1 1 ms 1 ms 1 ms o2.box []
    2 22 ms 21 ms 24 ms rdsl-trir-de01.nw.mediaways.net [213.20.57.226]
    3 20 ms 21 ms 21 ms xmws-trir-de03-chan-18.nw.mediaways.net [195.71.37.225]
    4 43 ms 76 ms 45 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182]
    5 55 ms 56 ms 120 ms 207.88.15.77.ptr.us.xo.net [207.88.15.77]
    6 141 ms 148 ms 138 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
    7 135 ms 134 ms 137 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
    8 136 ms 138 ms 141 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
    9 134 ms 134 ms 140 ms 209.117.103.10
    10 142 ms 141 ms 138 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    11 146 ms 143 ms 142 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    12 136 ms 138 ms 133 ms patchserver.crypticstudios.com [208.95.185.41]

    Although my tracert looks okay, playing is near impossible. Ping spikes to about 2-3 seconds with massive rubberbanding etc.

    edit:
    Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41] über maximal 30 Abschnitte:

    1 1 ms 4 ms 1 ms o2.box []
    2 21 ms 21 ms 22 ms rdsl-trir-de01.nw.mediaways.net [213.20.57.226]
    3 21 ms 21 ms 22 ms xmws-trir-de03-chan-18.nw.mediaways.net [195.71.37.225]
    4 43 ms 47 ms 40 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182]
    5 83 ms 56 ms 56 ms 207.88.15.77.ptr.us.xo.net [207.88.15.77]
    6 135 ms 154 ms 150 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
    7 136 ms 135 ms 135 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
    8 136 ms 137 ms 140 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
    9 1422 ms 1407 ms * 209.117.103.10
    10 902 ms 951 ms 1172 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    11 1182 ms 1187 ms 1190 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    12 * * 1439 ms patchserver.crypticstudios.com [208.95.185.41]

    Hello Mr. Lagspike!
  • ayliffetayliffet Member, Neverwinter Beta Users, Neverwinter Hero Users, Neverwinter Knight of the Feywild Users Posts: 2 Arc User
    edited June 2014
    I spoke too soon, rubber banding and losing contact to server. Itlasted long enough to lull me into a sense of security.
  • ambisinisterrambisinisterr Member, Neverwinter Moderator Posts: 10,462 Community Moderator
    edited June 2014
    noerq wrote: »
    Hello Mr. Lagspike!
    Different location than me but the issue is still before Cryptic. The actually problem arises at hop 9.

    Perhaps some other lines are being saturated due to the issue myself and others are experiencing? That's my best guess, at least.
  • hetz000hetz000 Member Posts: 0 Arc User
    edited June 2014
    My trace
    1 67 ms 100 ms 99 ms dsldevice.lan
    2 * * * Request timed out.
    3 12 ms 12 ms 12 ms 172.29.16.113
    4 13 ms 13 ms 12 ms gtr10-gdr11.ip.t-com.hr [195.29.110.126]
    5 13 ms 13 ms 13 ms te7-7.ccr01.zag01.atlas.cogentco.com [149.6.30.6
    1]
    6 21 ms 22 ms 21 ms te0-7-0-21.ccr21.vie01.atlas.cogentco.com [130.1
    17.50.169]
    7 28 ms 27 ms 28 ms be2200.ccr21.muc01.atlas.cogentco.com [130.117.4
    9.1]
    8 34 ms 34 ms 33 ms be2228.ccr41.fra03.atlas.cogentco.com [154.54.38
    .49]
    9 40 ms 40 ms 40 ms be2261.ccr41.ams03.atlas.cogentco.com [154.54.37
    .29]
    10 50 ms 50 ms 50 ms be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77
    .246]
    11 115 ms 115 ms 116 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
    .161]
    12 115 ms 116 ms 115 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    13 126 ms 125 ms 125 ms 38.111.40.114
    14 115 ms 115 ms 114 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.
    This route seems to be ok, i mean no more lag than usual.
  • grimfang50grimfang50 Member Posts: 0
    edited June 2014
    Different location than me but the issue is still before Cryptic. The actually problem arises at hop 9.

    Perhaps some other lines are being saturated due to the issue myself and others are experiencing? That's my best guess, at least.

    I cannot log in either.

    What I find odd is that I am logging in thru the ARC client and it is asking me for my password. Usually while logging thru ARC I do not have to enter my password. Thus I logged out of ARC and signed back in. Still asks me for password at the launcher.

    Anyhow it authenticates and hits "patching" and just stalls out at that point.

    It also does not respond when I click the "Cancel" button.

    My tracert shows everything is fine!
  • zebularzebular Member, Neverwinter Moderator, NW M9 Playtest Posts: 15,270 Community Moderator
    edited June 2014
    . . . I'm in Michigan and I can connect fine. From everything I am reading and hearing here and elsewhere, it sounds like what Ambi said, a certain Relay HUB is down which is affecting only people who would go through that HUB. When a HUB goes down, it usually doesn't stay down for long as ISPs start raising a fuss.
  • grimfang50grimfang50 Member Posts: 0
    edited June 2014
    zebular wrote: »
    . . . I'm in Michigan and I can connect fine. From everything I am reading and hearing here and elsewhere, it sounds like what Ambi said, a certain Relay HUB is down which is affecting only people who would go through that HUB. When a HUB goes down, it usually doesn't stay down for long as ISPs start raising a fuss.

    I FIGURED OUT THE ISSUE!


    For me I clicked on CONROL+SHIFT+ESC.....

    This brings up Task Manager.

    Click on the processes tab and look for a Cryptic err that is running. Click to End it and problem was solved upon rebooting!

    At least that is what worked for me!

    Hope it helps!
Sign In or Register to comment.