test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC, Network, and Other Technical Issues› Windows and General: PC, Network, and Other Technical Issues

Connection to server timeouts

shadowleopard64#3762 shadowleopard64
shadowleopard64#3762
 Member Posts: 171 Arc User
in Windows and General: PC, Network, and Other Technical Issues
Constant connection to server has timed out errors I can't stay connected to the game I have been disconnected twice in 5 min.

Comments

  • shadowleopard64#3762 shadowleopard64
    shadowleopard64#3762
         Member Posts: 171 Arc User
    Just got disconnected or server timed out in the middle of a breach event run seriously cryptic
  • bwhortonbwhorton Member Posts: 39 Arc User
    been disconnected every 5-10 minutes the last several hours gamepaly is impossible
  • generaldisaster#4313 generaldisaster
    generaldisaster#4313
         Member Posts: 373 Arc User
    edited April 2018
    I keep getting login server timeouts when i go to select my toon. when I did a tracert i got these results

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

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

    1 2 ms 1 ms 2 ms 192.168.1.1
    2 20 ms 46 ms 47 ms 195.215-34-174.res.dyn.surewest.net [174.34.215.195]
    3 21 ms 33 ms 29 ms 172.21.2.57
    4 22 ms 18 ms 18 ms 66.60.128.14
    5 51 ms 102 ms 52 ms 254.153-60-66-biz-static.surewest.net [66.60.153.254]
    6 50 ms 25 ms 33 ms sjo-b21-link.telia.net [62.115.155.238]
    7 124 ms 109 ms 133 ms nyk-bb4-link.telia.net [62.115.119.228]
    8 102 ms 127 ms 115 ms bost-b1-link.telia.net [62.115.122.235]
    9 119 ms 107 ms 120 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
    10 159 ms 105 ms 102 ms border3.ae1-bbnet1.bsn.pnap.net [63.251.128.7]
    11 109 ms 104 ms 127 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    12 127 ms 101 ms 131 ms 198.49.243.253
    13 * * * Request timed out.
    14 132 ms 114 ms 109 ms xboxpatchserver.crypticstudios.com [208.95.185.41]

    Trace complete.


    perhaps one of the server hampsters died? the issue seems to be something within the perfectworld network side of things.

    when i went to do a pathping, the command froze up when the ip address above that timed out was reached in pathping.



    [UPDATE]

    pathping finally finished...… took over 10 minutes to finish.

    C:\WINDOWS\system32>pathping patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 ChrisSolomon-PC [192.168.1.9]
    1 192.168.1.1
    2 195.215-34-174.res.dyn.surewest.net [174.34.215.195]
    3 172.21.2.57
    4 66.60.128.14
    5 254.153-60-66-biz-static.surewest.net [66.60.153.254]
    6 sjo-b21-link.telia.net [62.115.155.238]
    7 nyk-bb4-link.telia.net [62.115.119.228]
    8 bost-b1-link.telia.net [62.115.122.235]
    9 internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
    10 border3.ae1-bbnet1.bsn.pnap.net [63.251.128.7]
    11 perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    12 198.49.243.253
    13 * * *
    Computing statistics for 300 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 ChrisSolomon-PC [192.168.1.9]
    0/ 100 = 0% |
    1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 35ms 0/ 100 = 0% 0/ 100 = 0% 195.215-34-174.res.dyn.surewest.net [174.34.215.195]
    0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% 172.21.2.57
    0/ 100 = 0% |
    4 33ms 0/ 100 = 0% 0/ 100 = 0% 66.60.128.14
    0/ 100 = 0% |
    5 36ms 0/ 100 = 0% 0/ 100 = 0% 254.153-60-66-biz-static.surewest.net [66.60.153.254]
    0/ 100 = 0% |
    6 38ms 0/ 100 = 0% 0/ 100 = 0% sjo-b21-link.telia.net [62.115.155.238]
    0/ 100 = 0% |
    7 119ms 0/ 100 = 0% 0/ 100 = 0% nyk-bb4-link.telia.net [62.115.119.228]
    0/ 100 = 0% |
    8 117ms 0/ 100 = 0% 0/ 100 = 0% bost-b1-link.telia.net [62.115.122.235]
    0/ 100 = 0% |
    9 115ms 0/ 100 = 0% 0/ 100 = 0% internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
    0/ 100 = 0% |
    10 114ms 0/ 100 = 0% 0/ 100 = 0% border3.ae1-bbnet1.bsn.pnap.net [63.251.128.7]
    100/ 100 =100% |
    11 --- 100/ 100 =100% 0/ 100 = 0% perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    0/ 100 = 0% |
    12 --- 100/ 100 =100% 0/ 100 = 0% 198.49.243.253

    Trace complete.
    Star Treking, across the universe. Only going forward because we can't find reverse...
  • generaldisaster#4313 generaldisaster
    generaldisaster#4313
         Member Posts: 373 Arc User
    when I did a tracert directly on the ip address belonging to PWE the rout it took was completely different than when i did a tracert on patchserver.crypticstudios.com

    C:\WINDOWS\system32>tracert 198.49.243.253

    Tracing route to 198.49.243.253 over a maximum of 30 hops

    1 2 ms 1 ms 1 ms 192.168.1.1
    2 102 ms 97 ms 67 ms 195.215-34-174.res.dyn.surewest.net [174.34.215.195]
    3 93 ms 82 ms 78 ms 172.21.2.57
    4 67 ms 82 ms 79 ms 66.60.128.5
    5 49 ms 68 ms 77 ms 66.60.128.10
    6 101 ms 76 ms 84 ms ce-0-0-0-1.r00.scrmca02.us.bb.gin.ntt.net [131.103.117.193]
    7 93 ms 83 ms 38 ms ae-7.r02.snjsca04.us.bb.gin.ntt.net [129.250.7.10]
    8 105 ms 94 ms 98 ms ae-0.cogent.snjsca04.us.bb.gin.ntt.net [129.250.8.42]
    9 80 ms 68 ms 92 ms be3142.ccr21.sjc01.atlas.cogentco.com [154.54.1.193]
    10 47 ms 78 ms 85 ms be3178.ccr21.sfo01.atlas.cogentco.com [154.54.43.69]
    11 102 ms 81 ms 84 ms be3109.ccr21.slc01.atlas.cogentco.com [154.54.44.138]
    12 139 ms 142 ms 116 ms be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
    13 138 ms 129 ms 94 ms be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
    14 125 ms 163 ms 160 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
    15 120 ms 149 ms 125 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
    16 164 ms 151 ms 162 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
    17 158 ms 137 ms 138 ms be2299.ccr31.bos01.atlas.cogentco.com [154.54.43.9]
    18 196 ms 166 ms 162 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
    19 131 ms 161 ms 162 ms 38.111.40.114
    20 153 ms 168 ms 157 ms 198.49.243.253

    perhaps there is a misconfiguration for the route it takes, which is causing all the server timeouts?
    Star Treking, across the universe. Only going forward because we can't find reverse...
Sign In or Register to comment.