test content
What is the Arc Client?
Install Arc

Server Not responding

I logged in for the first time today around 2:30 eastern and managed to get through ISE but afterwards I started having major server not responding errors. I logged out and noticed I was getting a "No Internet Access" message from my Internet, so I restarted got everything back up and tried again. Loading another toon I got the same problem SNRs so I logged off.

My question is anyone else having problems like this today or is it something about my computer and Internet access
Post edited by joshjpeter2 on

Comments

  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited June 2014
    ...
    My question is anyone else having problems like this today or is it something about my computer and Internet access

    Hard to say without additional information... Take a look at this thread, then post some Network Diagnostic results... http://sto-forum.perfectworld.com/showthread.php?t=225155
  • joshjpeter2joshjpeter2 Member Posts: 19 Arc User
    edited June 2014
    here is the tracert I ran

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 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 192.168.0.1
    2 33 ms 17 ms 30 ms cpe-24-166-96-1.neo.res.rr.com [24.166.96.1]
    3 9 ms 10 ms 10 ms tge7-1.grrdpaao02h.midwest.rr.com [24.164.103.17
    3]
    4 13 ms 12 ms 15 ms 24.33.101.36
    5 13 ms 15 ms 17 ms be14.clevohek-ccr03.midwest.rr.com [65.29.1.98]

    6 18 ms 14 ms 19 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
    7 39 ms 41 ms 41 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
    8 38 ms 38 ms 39 ms 107.14.17.178
    9 37 ms 40 ms 37 ms 107.14.19.133
    10 38 ms 38 ms 38 ms te0-11-0-23.ccr41.iad02.atlas.cogentco.com [154.
    54.10.193]
    11 37 ms 38 ms 40 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.
    234]
    12 45 ms 45 ms 47 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
    .118]
    13 54 ms 51 ms 53 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
    .42]
    14 53 ms 52 ms 49 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    15 54 ms 53 ms 52 ms 38.111.40.114
    16 51 ms 53 ms 51 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.

    C:\Windows\system32>


    And now the nettest

    contacting nettest server..
    Local IP:
    Ping: 50.0 msec
    Port: 80: 880 KB/sec 26 KB/sec 934 KB/sec 500
    Port: 80: 574 KB/sec 15 KB/sec 609 KB/sec 500
    Port: 443: 358 KB/sec 13 KB/sec 379 KB/sec 500
    Port: 443: 667 KB/sec 20 KB/sec 707 KB/sec 500
    Port: 7255: 683 KB/sec 18 KB/sec 723 KB/sec 500
    Port: 7255: 704 KB/sec 16 KB/sec 744 KB/sec 500
    Port: 7003: 629 KB/sec 19 KB/sec 666 KB/sec 500
    Port: 7003: 763 KB/sec 21 KB/sec 808 KB/sec 500
    Port: 7202: 840 KB/sec 24 KB/sec 891 KB/sec 500
    Port: 7202: 746 KB/sec 19 KB/sec 789 KB/sec 500
    Port: 7499: 861 KB/sec 26 KB/sec 916 KB/sec 500
    Port: 7499: 583 KB/sec 18 KB/sec 616 KB/sec 500
    Port: 80: 680 KB/sec 19 KB/sec 720 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited June 2014
    here is the tracert I ran
    ...

    The latency values of your 'Trace Route' look fine, but the inconsistent results of your 'Net Test' seems to indicate you have a connection quality issue of some kind...

    You may be suffering from silently dropped packets somewhere along your connection path to the STO Servers... Use the 'pathping' command, (which has the syntax as the 'tracert' command) and post those results, as this will show if you have a dropped packet problem or not...
  • joshjpeter2joshjpeter2 Member Posts: 19 Arc User
    edited June 2014
    I hope I did this right since i'm not to familiar with this sort of thing anyway here it is

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

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 xxxxxxxxx xxxxxxxxxxxxxxx
    1 192.168.0.1
    2 cpe-24-166-96-1.neo.res.rr.com [24.166.96.1]
    3 tge7-1.grrdpaao02h.midwest.rr.com [24.164.103.173]
    4 24.33.101.36
    5 be14.clevohek-ccr03.midwest.rr.com [65.29.1.98]
    6 be25.clevohek01r.midwest.rr.com [65.29.1.32]
    7 ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
    8 107.14.17.178
    9 107.14.19.133
    10 te0-11-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.193]
    11 be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
    12 be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
    13 be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
    14 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    15 38.111.40.114
    16 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 400 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 xxxxxxxxx xxxxxxxxxxxxxxx
    0/ 100 = 0% |
    1 14ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
    0/ 100 = 0% |
    2 23ms 0/ 100 = 0% 0/ 100 = 0% cpe-24-166-96-1.neo.res.rr.com [24
    .166.96.1]
    0/ 100 = 0% |
    3 25ms 0/ 100 = 0% 0/ 100 = 0% tge7-1.grrdpaao02h.midwest.rr.com
    [24.164.103.173]
    0/ 100 = 0% |
    4 22ms 0/ 100 = 0% 0/ 100 = 0% 24.33.101.36
    0/ 100 = 0% |
    5 27ms 0/ 100 = 0% 0/ 100 = 0% be14.clevohek-ccr03.midwest.rr.com
    [65.29.1.98]
    0/ 100 = 0% |
    6 39ms 0/ 100 = 0% 0/ 100 = 0% be25.clevohek01r.midwest.rr.com [6
    5.29.1.32]
    0/ 100 = 0% |
    7 61ms 0/ 100 = 0% 0/ 100 = 0% ae-3-0.cr0.dca20.tbone.rr.com [66.
    109.6.70]
    0/ 100 = 0% |
    8 59ms 0/ 100 = 0% 0/ 100 = 0% 107.14.17.178
    0/ 100 = 0% |
    9 60ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.133
    0/ 100 = 0% |
    10 57ms 0/ 100 = 0% 0/ 100 = 0% te0-11-0-23.ccr41.iad02.atlas.coge
    ntco.com [154.54.10.193]
    0/ 100 = 0% |
    11 55ms 0/ 100 = 0% 0/ 100 = 0% be2176.ccr21.dca01.atlas.cogentco.
    com [154.54.41.54]
    0/ 100 = 0% |
    12 62ms 0/ 100 = 0% 0/ 100 = 0% be2149.ccr22.jfk02.atlas.cogentco.
    com [154.54.31.126]
    0/ 100 = 0% |
    13 66ms 0/ 100 = 0% 0/ 100 = 0% be2095.ccr21.bos01.atlas.cogentco.
    com [154.54.30.38]
    0/ 100 = 0% |
    14 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.254]
    0/ 100 = 0% |
    15 72ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    16 65ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
    08.95.185.41]

    Trace complete.

    C:\Windows\system32>
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited June 2014
    ...
    13 66ms 0/ 100 = 0% 0/ 100 = 0% be2095.ccr21.bos01.atlas.cogentco.
    com [154.54.30.38]
    0/ 100 = 0% |
    14 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.254]
    0/ 100 = 0% |
    15 72ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    16 65ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
    08.95.185.41]

    Trace complete.

    C:\Windows\system32>

    So 'Path Ping' indicates the problem is being caused by the Cogent Boston Hub, so there isn't much you can do about it...

    You could try using the patch and game 'Proxy' options, located in the Options Menu of the STO Launcher, as this may, or may not redirect your connection path around the Boston Hub congestion...
  • joshjpeter2joshjpeter2 Member Posts: 19 Arc User
    edited June 2014
    thanks for the help
  • eera73eera73 Member Posts: 9 Arc User
    edited June 2014
    it is not the FAI matter, it is the STO code who are worth. You/we only can hope that one day dev fix it !
  • medtac124medtac124 Member Posts: 0 Arc User
    edited June 2014
    Of course it's Cogent's fault. Who would've guessed? :rolleyes:
    [SIGPIC]Click here to visit our website[/SIGPIC]
    lunasto wrote: »
    Banned because I don't like your pictures eyebrows! They look like pinball flippers!
  • drachenfelesdrachenfeles Member Posts: 163 Arc User
    edited June 2014
    yep, massive lags today around 1800-1900 hours (game became unplayable) although around noon (1200-1300) was quite well (given STO standards), no such issues other non-cryptic mmo's

    I'm currently GMT+2 btw
  • rakija879rakija879 Member Posts: 646 Arc User
    edited June 2014
    I have the problem that is when I dc for a character I cant get back onto him (server time out).
    But I still can log in on my others but the game is lagging a lot for some time now.

    Is there any problem here?


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

    1 2 ms 4 ms <1 ms 192.168.1.1
    2 22 ms 21 ms 26 ms 85.114.33.42
    3 23 ms 21 ms 21 ms 85.114.32.177
    4 22 ms 22 ms 23 ms te4-2.ccr01.zag01.atlas.cogentco.com [149.6.30.2
    1]
    5 33 ms 30 ms 31 ms te0-7-0-21.ccr21.vie01.atlas.cogentco.com [130.1
    17.50.169]
    6 36 ms 36 ms 36 ms be2223.ccr22.muc01.atlas.cogentco.com [130.117.4
    9.137]
    7 41 ms 42 ms 44 ms be2229.ccr42.fra03.atlas.cogentco.com [154.54.38
    .57]
    8 49 ms 49 ms 49 ms be2262.ccr42.ams03.atlas.cogentco.com [154.54.37
    .33]
    9 62 ms 62 ms 58 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
    .69]
    10 687 ms 124 ms 124 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
    .165]
    11 123 ms 125 ms 125 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
    4]
    12 126 ms 125 ms 125 ms 38.111.40.114
    13 124 ms 128 ms 124 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.


    contacting nettest server..
    Local IP: 89.201.180.173
    Ping: 120.4 msec
    Port: 80: 352 KB/sec 11 KB/sec 371 KB/sec 500
    Port: 80: 353 KB/sec 11 KB/sec 372 KB/sec 500
    Port: 443: 186 KB/sec 9 KB/sec 196 KB/sec 500
    Port: 443: 190 KB/sec 7 KB/sec 200 KB/sec 500
    Port: 7255: 197 KB/sec 8 KB/sec 208 KB/sec 500
    Port: 7255: 183 KB/sec 9 KB/sec 193 KB/sec 500
    Port: 7003: 192 KB/sec 8 KB/sec 203 KB/sec 500
    Port: 7003: 192 KB/sec 9 KB/sec 203 KB/sec 500
    Port: 7202: 181 KB/sec 7 KB/sec 191 KB/sec 500
    Port: 7202: 156 KB/sec 7 KB/sec 164 KB/sec 500
    Port: 7499: 185 KB/sec 9 KB/sec 196 KB/sec 500
    Port: 7499: 184 KB/sec 7 KB/sec 194 KB/sec 500
    Port: 80: 353 KB/sec 11 KB/sec 372 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit


    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Baja [192.168.1.101]
    1 192.168.1.1
    2 85.114.33.42
    3 85.114.32.177
    4 te4-2.ccr01.zag01.atlas.cogentco.com [149.6.30.21]
    5 te0-7-0-21.ccr21.vie01.atlas.cogentco.com [130.117.50.169]
    6 be2223.ccr22.muc01.atlas.cogentco.com [130.117.49.137]
    7 be2229.ccr42.fra03.atlas.cogentco.com [154.54.38.57]
    8 be2262.ccr42.ams03.atlas.cogentco.com [154.54.37.33]
    9 be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
    10 be2387.ccr22.bos01.atlas.cogentco.com [154.54.44.165]
    11 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    12 38.111.40.114
    13 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 325 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Baja [192.168.1.101]
    0/ 100 = 0% |
    1 8ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 51ms 0/ 100 = 0% 0/ 100 = 0% 85.114.33.42
    0/ 100 = 0% |
    3 39ms 0/ 100 = 0% 0/ 100 = 0% 85.114.32.177
    0/ 100 = 0% |
    4 54ms 0/ 100 = 0% 0/ 100 = 0% te4-2.ccr01.zag01.atlas.cogentco.c
    om [149.6.30.21]
    0/ 100 = 0% |
    5 43ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-21.ccr21.vie01.atlas.cogen
    tco.com [130.117.50.169]
    0/ 100 = 0% |
    6 42ms 0/ 100 = 0% 0/ 100 = 0% be2223.ccr22.muc01.atlas.cogentco.
    com [130.117.49.137]
    0/ 100 = 0% |
    7 56ms 0/ 100 = 0% 0/ 100 = 0% be2229.ccr42.fra03.atlas.cogentco.
    com [154.54.38.57]
    0/ 100 = 0% |
    8 58ms 0/ 100 = 0% 0/ 100 = 0% be2262.ccr42.ams03.atlas.cogentco.
    com [154.54.37.33]
    0/ 100 = 0% |
    9 65ms 0/ 100 = 0% 0/ 100 = 0% be2183.ccr22.lpl01.atlas.cogentco.
    com [154.54.58.69]
    0/ 100 = 0% |
    10 135ms 0/ 100 = 0% 0/ 100 = 0% be2387.ccr22.bos01.atlas.cogentco.
    com [154.54.44.165]
    0/ 100 = 0% |
    11 158ms 0/ 100 = 0% 0/ 100 = 0% te4-2.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.254]
    0/ 100 = 0% |
    12 142ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    13 134ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
    08.95.185.41]

    Trace complete.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited June 2014
    rakija879 wrote: »
    I have the problem that is when I dc for a character I cant get back onto him (server time out).
    But I still can log in on my others but the game is lagging a lot for some time now.

    Is there any problem here?


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

    1 2 ms 4 ms <1 ms 192.168.1.1
    2 22 ms 21 ms 26 ms 85.114.33.42
    3 23 ms 21 ms 21 ms 85.114.32.177
    4 22 ms 22 ms 23 ms te4-2.ccr01.zag01.atlas.cogentco.com [149.6.30.2
    1]
    5 33 ms 30 ms 31 ms te0-7-0-21.ccr21.vie01.atlas.cogentco.com [130.1
    17.50.169]
    6 36 ms 36 ms 36 ms be2223.ccr22.muc01.atlas.cogentco.com [130.117.4
    9.137]
    7 41 ms 42 ms 44 ms be2229.ccr42.fra03.atlas.cogentco.com [154.54.38
    .57]
    8 49 ms 49 ms 49 ms be2262.ccr42.ams03.atlas.cogentco.com [154.54.37
    .33]
    9 62 ms 62 ms 58 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
    .69]
    10 687 ms 124 ms 124 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
    .165]
    11 123 ms 125 ms 125 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
    4]
    12 126 ms 125 ms 125 ms 38.111.40.114
    13 124 ms 128 ms 124 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.
    .....

    Now Cryptic recommends a upper limit of 180ms for latency, and it appears the Boston Cogent Hub is way above this...

    The recommended throughput should be in the 300KB/s - 500KB/s, and the 'Net Test' shows that your sustained throughput is well below this range, and indicates a connection quality issue of some kind...

    Its unusual that the 'Path Ping' isn't showing any packet drop, but the problem is probably intermittent in nature, and could have simply missed seeing the problem...

    You could try using the Europe Proxy settings in the Launcher 'Option' menu and see if that might bypass the network congestion, but it may, or may not work, but doesn't hurt to try...
  • rakija879rakija879 Member Posts: 646 Arc User
    edited June 2014
    Eu proxy doesnt do a lot of good I tried it in the past a few times the problem is still the same :(
Sign In or Register to comment.