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

Game times out on splash screen.

aunvyraeaunvyrae Member Posts: 0 Arc User
edited August 2014 in Windows and General: PC, Network, and Other Technical Issues
I was going to post in a different thread, but most threads that where close to what I have are old (1+ years). So I'm starting a new one.

When I login to the game (both through ARC and Steam) the launcher kicks over to the .exe but never connects to the game server. It just hangs there on the splash screen till I get a timed out error message. Which then brings up a crash report window that doesn't last long enough for me to even put any information in it to send.

I did a tracert, nettest, and pathping tests to see if it was an ISP problem. The nettest goes directly to a timed out message where as the other two go through with out any real problems that I can see that would cause this issue. I've also cleared my DNS cache and reset my DNS with no effect.



Tracert:

1 <1 ms <1 ms <1 ms
2 47 ms 26 ms 29 ms dynamic-216-186-218-1.knology.net [216.186.218.1
]
3 12 ms 12 ms 16 ms user-69-73-108-117.knology.net [69.73.108.117]
4 24 ms 15 ms 11 ms user-69-73-108-149.knology.net [69.73.108.149]
5 13 ms 13 ms 16 ms user-69-73-108-210.knology.net [69.73.108.210]
6 25 ms 24 ms 24 ms user-24-96-153-77.knology.net [24.96.153.77]
7 27 ms 28 ms 24 ms FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
8 22 ms 26 ms 35 ms user-24-214-2-221.knology.net [24.214.2.221]
9 40 ms 33 ms 29 ms 76.73.147.238
10 105 ms 140 ms 25 ms ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
11 42 ms 24 ms 28 ms te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.5
4.11.61]
12 27 ms 35 ms 28 ms be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.
121]
13 39 ms 37 ms 38 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
14 45 ms 50 ms 56 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
15 60 ms 53 ms 60 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
16 80 ms 221 ms 206 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
17 57 ms 53 ms 53 ms 38.111.40.114
18 56 ms 52 ms 57 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.


Pathping:

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

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 my computer
1 (my ISP)
2 dynamic-216-186-218-1.knology.net [216.186.218.1]
3 user-69-73-108-117.knology.net [69.73.108.117]
4 user-69-73-108-149.knology.net [69.73.108.149]
5 user-69-73-108-210.knology.net [69.73.108.210]
6 user-24-96-153-77.knology.net [24.96.153.77]
7 FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
8 user-24-214-2-221.knology.net [24.214.2.221]
9 76.73.147.238
10 ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
11 te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.54.11.61]
12 be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.121]
13 be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
14 be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
15 be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
16 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
17 38.111.40.114
18 patchserver2.crypticstudios.com [208.95.185.41]

Computing statistics for 450 seconds...


Lastly, I heard rumors at one time that Neverwinter and STO shared the same server, if that's the case it's most definitely a STO problem since I have no issues logging in and playing Neverwinter.

Thanks for your time.
Post edited by aunvyrae on

Comments

  • stoutesstoutes Member Posts: 4,219 Arc User
    edited August 2014
    Hey there, is it something along the lines of locking up when you loaded the game? Just after you see the LoR logo?

    If so, someone else yesterday posting something the same in this topic. The answers given might help you.
    maxvitor wrote: »
    Nerf is OP, plz nerf
    That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.

    I call it, the Stoutes paradox.
  • aunvyraeaunvyrae Member Posts: 0 Arc User
    edited August 2014
    No, I don't get that far. I get to the black cryptic splash screen and then a timed out message. No loading bar or any thing.
  • stoutesstoutes Member Posts: 4,219 Arc User
    edited August 2014
    Have you checked your event viewer for possible errors?

    Start => Run => eventvwr or take a look at YT how to open and use your Event viewer.
    maxvitor wrote: »
    Nerf is OP, plz nerf
    That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.

    I call it, the Stoutes paradox.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited August 2014
    aunvyrae wrote: »
    ....
    1 <1 ms <1 ms <1 ms
    2 47 ms 26 ms 29 ms dynamic-216-186-218-1.knology.net [216.186.218.1
    ]
    3 12 ms 12 ms 16 ms user-69-73-108-117.knology.net [69.73.108.117]
    4 24 ms 15 ms 11 ms user-69-73-108-149.knology.net [69.73.108.149]
    5 13 ms 13 ms 16 ms user-69-73-108-210.knology.net [69.73.108.210]
    6 25 ms 24 ms 24 ms user-24-96-153-77.knology.net [24.96.153.77]
    7 27 ms 28 ms 24 ms FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
    8 22 ms 26 ms 35 ms user-24-214-2-221.knology.net [24.214.2.221]
    9 40 ms 33 ms 29 ms 76.73.147.238
    10 105 ms 140 ms 25 ms ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
    11 42 ms 24 ms 28 ms te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.5
    4.11.61]
    12 27 ms 35 ms 28 ms be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.
    121]
    13 39 ms 37 ms 38 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
    .110]
    14 45 ms 50 ms 56 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
    .74]
    15 60 ms 53 ms 60 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
    .118]
    16 80 ms 221 ms 206 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
    4]
    17 57 ms 53 ms 53 ms 38.111.40.114
    18 56 ms 52 ms 57 ms patchserver2.crypticstudios.com [208.95.185.41]

    Pathping:

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

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 my computer
    1 (my ISP)
    2 dynamic-216-186-218-1.knology.net [216.186.218.1]
    3 user-69-73-108-117.knology.net [69.73.108.117]
    4 user-69-73-108-149.knology.net [69.73.108.149]
    5 user-69-73-108-210.knology.net [69.73.108.210]
    6 user-24-96-153-77.knology.net [24.96.153.77]
    7 FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
    8 user-24-214-2-221.knology.net [24.214.2.221]
    9 76.73.147.238
    10 ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
    11 te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.54.11.61]
    12 be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.121]
    13 be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
    14 be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
    15 be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
    16 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    17 38.111.40.114
    18 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 450 seconds...
    ....

    Did you wait 450 seconds for the 'Path Ping' to complete ???

    The Trace Route shows high latency for the Cogent Boston Hub, but hop #10, the gateway from your ISP to the Cogent Internet Backbone also looks suspicious, with its sudden jump in network latency value compared to its proceeding and following hop, so the 'Path Ping' results would be very useful...

    If the 'Net Test' fails, this indicates that this is a Internet connection route issue, as 'Net Test' talks to a simple diagnostic server located on the same local network as the STO servers, so the STO servers are completely out of the picture for the 'Net Test' diagnostics...

    And STO and Neverwinter share the same local network, but use different Servers...

    Something you might want to try is to use the 'US Proxy' in the Launcher Option menu, as this may, or may not improve your condition. (Doesn't hurt to try, and you can always change it back if it doesn't work...)
  • aunvyraeaunvyrae Member Posts: 0 Arc User
    edited August 2014
    Ok this is telling me there is an issue with the program over the internet. Which at this point I don't know how to fix since the game ran fine before the last patch (not the patch today). So I guess at this point I'll wait till the servers come up see if the newest patched fixed it then do a uninstall and reinstall and see what happens. The only thing that I can think of that I have changed with my computer since the time it worked (2-3 days before yesterday) and now is I had a OS update, but that shouldn't have affected the exe file.


    The program GameClient.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
    Process ID: 13cc
    Start Time: 01cfbd1d4a326287
    Termination Time: 18
    Application Path: C:\Program Files (x86)\Steam\steamapps\common\Star Trek Online\Star Trek Online\Live\GameClient.exe
    Report Id: 8eac44c0-2910-11e4-b1a8-448a5b58f1fd


    But here is the complete pathping results.

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

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 [my pc name]
    1 [my ISP]
    2 dynamic-216-186-218-1.knology.net [216.186.218.1]
    3 user-69-73-108-117.knology.net [69.73.108.117]
    4 user-69-73-108-149.knology.net [69.73.108.149]
    5 user-69-73-108-210.knology.net [69.73.108.210]
    6 user-24-96-153-77.knology.net [24.96.153.77]
    7 FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
    8 user-24-214-2-221.knology.net [24.214.2.221]
    9 76.73.147.238
    10 ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
    11 te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.54.11.61]
    12 be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.121]
    13 be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
    14 be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
    15 be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
    16 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    17 38.111.40.114
    18 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 450 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 [my computer name]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% [my ISP]

    2 14ms 0/ 100 = 0% 0/ 100 = 0% dynamic-216-186-218-1.knology.net [216.186.218.1]
    0/ 100 = 0% |
    3 15ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-108-117.knology.net [69.73.108.117]
    0/ 100 = 0% |
    4 17ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-108-149.knology.net [69.73.108.149]
    0/ 100 = 0% |
    5 15ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-108-210.knology.net [69.73.108.210]
    0/ 100 = 0% |
    6 15ms 0/ 100 = 0% 0/ 100 = 0% user-24-96-153-77.knology.net [24.96.153.77]
    0/ 100 = 0% |
    7 14ms 0/ 100 = 0% 0/ 100 = 0% FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
    0/ 100 = 0% |
    8 27ms 0/ 100 = 0% 0/ 100 = 0% user-24-214-2-221.knology.net [24.214.2.221]
    0/ 100 = 0% |
    9 34ms 0/ 100 = 0% 0/ 100 = 0% 76.73.147.238
    0/ 100 = 0% |
    10 30ms 0/ 100 = 0% 0/ 100 = 0% ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
    0/ 100 = 0% |
    11 38ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.54.11.61]
    0/ 100 = 0% |
    12 40ms 0/ 100 = 0% 0/ 100 = 0% be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.121]
    0/ 100 = 0% |
    13 41ms 0/ 100 = 0% 0/ 100 = 0% be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
    0/ 100 = 0% |
    14 50ms 0/ 100 = 0% 0/ 100 = 0% be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
    0/ 100 = 0% |
    15 57ms 0/ 100 = 0% 0/ 100 = 0% be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
    0/ 100 = 0% |
    16 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    0/ 100 = 0% |
    17 60ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    18 55ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.


    Update: Ok so now nothing is working, Can't connect to the patcher server for the launcher any more either. Both tracert and pathping are showing the same as I have posted here and nettest still a no go, times out every time after a few seconds. Something tells me this a internet issue on their end since I can connect to any other account I have with multiple companies around the world.... except this one game. Neverwinter still works.

    Update: fixed it, between shutting some programs down in the background, updating my Ethernet drivers, and the patch it's now working. Not sure which on of the above fixed the problem, but it's fixed.
  • azurianstarazurianstar Member Posts: 6,985 Arc User
    edited August 2014
    Meh, this patching glitch has happened since 9.5! :(




    HERE IS MINE!:

    1 1 ms 1 ms 1 ms PK5001Z.PK5001Z [192.168.0.1]
    2 26 ms 25 ms 26 ms fl-71-49-120-1.dhcp.embarqhsd.net [71.49.120.1]

    3 28 ms 27 ms 26 ms fl-69-68-14-65.dyn.embarqhsd.net [69.68.14.65]
    4 25 ms 26 ms 25 ms 173-248-66-236.centurylink.net [173.248.66.236]

    5 26 ms 26 ms 25 ms bb-wnpkflxe-jx9-02-ae0.core.centurytel.net [208.
    110.248.94]
    6 26 ms 26 ms 34 ms bb-wnpkflxe-jx9-01-ae0.core.centurytel.net [208.
    110.248.93]
    7 44 ms 45 ms 43 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
    [208.110.248.157]
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 62 ms 61 ms 62 ms bst-edge-05.inet.qwest.net [67.14.30.126]
    12 73 ms 63 ms 64 ms 65.120.117.250
    13 62 ms 63 ms 62 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
    04]
    14 66 ms 71 ms 71 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    15 71 ms 64 ms 198 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.


    EDIT: ISP Fixed.
  • zefferoncochranzefferoncochran Member Posts: 2 Arc User
    edited August 2014
    I am having the same issue with my account. Patch seems OK, even ran the 10 minute "verify all files" option, but when I get to the first splash screen the login server is unresponsive. I have a program called NetWorks that verifies all my internet activity in real time and it shows the login server as unresponsive.

    I have ran a speedtest, over 8 megs per second
    Have ran a traceroute and it's OK
    And even the pathping shows good to the login server, but it will not let me login, just times out on the splash screen, then brings up the crash report that says "Failed to connect to the login server, connection timed out".

    Even tried releasing and renewing my ipconfig. Basically the problem seems to be on the login server side, frustrating.. :confused::(
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited August 2014
    aunvyrae wrote: »
    ...

    But here is the complete pathping results.

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

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 [my pc name]
    1 [my ISP]
    2 dynamic-216-186-218-1.knology.net [216.186.218.1]
    3 user-69-73-108-117.knology.net [69.73.108.117]
    4 user-69-73-108-149.knology.net [69.73.108.149]
    5 user-69-73-108-210.knology.net [69.73.108.210]
    6 user-24-96-153-77.knology.net [24.96.153.77]
    7 FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
    8 user-24-214-2-221.knology.net [24.214.2.221]
    9 76.73.147.238
    10 ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
    11 te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.54.11.61]
    12 be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.121]
    13 be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
    14 be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
    15 be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
    16 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    17 38.111.40.114
    18 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 450 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 [my computer name]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% [my ISP]

    2 14ms 0/ 100 = 0% 0/ 100 = 0% dynamic-216-186-218-1.knology.net [216.186.218.1]
    0/ 100 = 0% |
    3 15ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-108-117.knology.net [69.73.108.117]
    0/ 100 = 0% |
    4 17ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-108-149.knology.net [69.73.108.149]
    0/ 100 = 0% |
    5 15ms 0/ 100 = 0% 0/ 100 = 0% user-69-73-108-210.knology.net [69.73.108.210]
    0/ 100 = 0% |
    6 15ms 0/ 100 = 0% 0/ 100 = 0% user-24-96-153-77.knology.net [24.96.153.77]
    0/ 100 = 0% |
    7 14ms 0/ 100 = 0% 0/ 100 = 0% FLTAMPPO1EDGX02-01.knology.net [24.214.0.42]
    0/ 100 = 0% |
    8 27ms 0/ 100 = 0% 0/ 100 = 0% user-24-214-2-221.knology.net [24.214.2.221]
    0/ 100 = 0% |
    9 34ms 0/ 100 = 0% 0/ 100 = 0% 76.73.147.238
    0/ 100 = 0% |
    10 30ms 0/ 100 = 0% 0/ 100 = 0% ge2-12.br01.atl01.pccwbtn.net [63.216.31.145]
    0/ 100 = 0% |
    11 38ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-34.ccr21.atl04.atlas.cogentco.com [154.54.11.61]
    0/ 100 = 0% |
    12 40ms 0/ 100 = 0% 0/ 100 = 0% be2035.ccr42.atl01.atlas.cogentco.com [154.54.6.121]
    0/ 100 = 0% |
    13 41ms 0/ 100 = 0% 0/ 100 = 0% be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]
    0/ 100 = 0% |
    14 50ms 0/ 100 = 0% 0/ 100 = 0% be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
    0/ 100 = 0% |
    15 57ms 0/ 100 = 0% 0/ 100 = 0% be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
    0/ 100 = 0% |
    16 --- 100/ 100 =100% 100/ 100 =100% te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
    0/ 100 = 0% |
    17 60ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    18 55ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.


    Update: Ok so now nothing is working, Can't connect to the patcher server for the launcher any more either. Both tracert and pathping are showing the same as I have posted here and nettest still a no go, times out every time after a few seconds. Something tells me this a internet issue on their end since I can connect to any other account I have with multiple companies around the world.... except this one game. Neverwinter still works.

    Update: fixed it, between shutting some programs down in the background, updating my Ethernet drivers, and the patch it's now working. Not sure which on of the above fixed the problem, but it's fixed.

    Now a 100% Packet Drop at the Cogent Boston Hub could explain why the 'Net Test' and the STO Client was failing. Since these kinds of things are often load based, and are intermittent in nature, (notice that the latency issue with hop #10 is gone...) the problem may have cleared up on its own, but could return...
    zefferoncochran wrote: »
    I am having the same issue with my account. Patch seems OK, even ran the 10 minute "verify all files" option, but when I get to the first splash screen the login server is unresponsive. I have a program called NetWorks that verifies all my internet activity in real time and it shows the login server as unresponsive.

    I have ran a speedtest, over 8 megs per second
    Have ran a traceroute and it's OK
    And even the pathping shows good to the login server, but it will not let me login, just times out on the splash screen, then brings up the crash report that says "Failed to connect to the login server, connection timed out".

    Good and OK in what way ???
  • zefferoncochranzefferoncochran Member Posts: 2 Arc User
    edited August 2014
    Like the previous poster stated "BAD PROGRAMMING"...

    Restarted PC, nothing.

    Restarted router, nothing.

    Had to restart receiver (have wireless internet that basically feeds off a cell-tower) and now it works.

    PS. It's a PAIN to reset my receiver, have to call tech support because they are not set up to be reset/restarted.

    But I did not have the 100% packet loss the previous person have, I had 0% on all mine, that's why I said it tested OK.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited August 2014
    zefferoncochran wrote: »
    ...
    But I did not have the 100% packet loss the previous person have, I had 0% on all mine, that's why I said it tested OK.

    And the Network connection latency ??? (either 'Path Ping' or 'Trace Route' results) and sustained connection throughput and port access? (Net Test results)...

    If the problem was being caused by the wireless receiver, then it would have shown up in the 'Trace Route' latency results, which is why you should have posted them...
  • deathus0deathus0 Member Posts: 6 Arc User
    edited August 2014
    After checking/patching and I hit Engage, I get the Cryptic Logo with the load bar across the sceen. After that, I get the LOR logo followed by a black screen and the STO cursor and nothing else.

    Tracert:

    Tracing route to patchserver2.crypticstudios.com [208.95.185.41] over a maximum of 30 hops:
    1 2 ms 1 ms 1 ms dslrouter.westell.com [10.0.0.1]
    2 61 ms 62 ms 61 ms nc-184-3-104-1.dhcp.embarqhsd.net [184.3.104.1]
    3 79 ms 78 ms 80 ms rcmt-agw1.inet.qwest.net [71.32.28.177]
    4 94 ms 94 ms 94 ms bst-edge-05.inet.qwest.net [67.14.30.126]
    5 98 ms 97 ms 99 ms 65.120.117.250
    6 91 ms 106 ms 93 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    7 109 ms 106 ms 109 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    8 91 ms 91 ms 91 ms patchserver2.crypticstudios.com [208.95.185.41]
    Trace complete.


    I have been getting the following error appearing in the Clientservercomm log on and off:

    Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.13:7422). Reason: socket was shutdown(0:No error) (socket error 0: No error)


    Restarting my computer, the STO application, and forcing a file integrity check have done nothing.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited August 2014
    deathus0 wrote: »
    ...
    Tracert:

    Tracing route to patchserver2.crypticstudios.com [208.95.185.41] over a maximum of 30 hops:
    1 2 ms 1 ms 1 ms dslrouter.westell.com [10.0.0.1]
    2 61 ms 62 ms 61 ms nc-184-3-104-1.dhcp.embarqhsd.net [184.3.104.1]
    3 79 ms 78 ms 80 ms rcmt-agw1.inet.qwest.net [71.32.28.177]
    4 94 ms 94 ms 94 ms bst-edge-05.inet.qwest.net [67.14.30.126]
    5 98 ms 97 ms 99 ms 65.120.117.250
    6 91 ms 106 ms 93 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    7 109 ms 106 ms 109 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    8 91 ms 91 ms 91 ms patchserver2.crypticstudios.com [208.95.185.41]
    Trace complete.


    I have been getting the following error appearing in the Clientservercomm log on and off:

    Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.13:7422). Reason: socket was shutdown(0:No error) (socket error 0: No error)


    Restarting my computer, the STO application, and forcing a file integrity check have done nothing.

    Nothing particularly bad with the 'Trace Route' results, so next we need the 'Net Test' and 'Path Ping' diagnostic results for further information on what could be causing your problems...

    See this thread for instructions to do so...

    http://sto-forum.perfectworld.com/showthread.php?t=1192081
  • deathus0deathus0 Member Posts: 6 Arc User
    edited August 2014
    As requested...

    Pathping:

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 PC
    1 dslrouter.westell.com [10.0.0.1]
    2 nc-184-3-104-1.dhcp.embarqhsd.net [184.3.104.1]
    3 71-32-28-177.rcmt.qwest.net [71.32.28.177]
    4 bst-edge-05.inet.qwest.net [67.14.30.126]
    5 65.120.117.250
    6 border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    7 perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    8 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 200 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 PC
    0/ 100 = 0% |
    1 1ms 0/ 100 = 0% 0/ 100 = 0% dslrouter.westell.com [10.0.0.1]
    0/ 100 = 0% |
    2 74ms 0/ 100 = 0% 0/ 100 = 0% nc-184-3-104-1.dhcp.embarqhsd.net[184.3.104.1]
    0/ 100 = 0% |
    3 77ms 1/ 100 = 1% 1/ 100 = 1% 71-32-28-177.rcmt.qwest.net [71.32.28.177]
    0/ 100 = 0% |
    4 --- 100/ 100 =100% 100/ 100 =100% bst-edge-05.inet.qwest.net [67.14.30.126]
    0/ 100 = 0% |
    5 93ms 0/ 100 = 0% 0/ 100 = 0% 65.120.117.250
    0/ 100 = 0% |
    6 99ms 1/ 100 = 1% 1/ 100 = 1% border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    0/ 100 = 0% |
    7 113ms 0/ 100 = 0% 0/ 100 = 0% perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    1/ 100 = 1% |
    8 104ms 1/ 100 = 1% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]
    Trace complete.


    Nettest:

    contacting nettest server..
    Local IP: 184.3.109.143
    Ping: 90.9 msec
    Port: 80: 184 KB/sec 18 KB/sec 205 KB/sec 500
    Port: 80: 117 KB/sec 15 KB/sec 136 KB/sec 500
    Port: 443: 200 KB/sec 20 KB/sec 221 KB/sec 500
    Port: 443: 136 KB/sec 14 KB/sec 155 KB/sec 500
    Port: 7255: 184 KB/sec 18 KB/sec 207 KB/sec 500
    Port: 7255: 107 KB/sec 14 KB/sec 126 KB/sec 500
    Port: 7003: 200 KB/sec 20 KB/sec 222 KB/sec 500
    Port: 7003: 162 KB/sec 16 KB/sec 181 KB/sec 500
    Port: 7202: 105 KB/sec 14 KB/sec 125 KB/sec 500
    Port: 7202: 199 KB/sec 20 KB/sec 220 KB/sec 500
    Port: 7499: 110 KB/sec 15 KB/sec 130 KB/sec 500
    Port: 7499: 202 KB/sec 20 KB/sec 224 KB/sec 500
    Port: 80: 107 KB/sec 11 KB/sec 122 KB/sec 500
    Idle NIC bandwidth Send: 2 KB/sec Recv: 3 KB/sec
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited August 2014
    deathus0 wrote: »
    As requested...

    Pathping:

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 PC
    1 dslrouter.westell.com [10.0.0.1]
    2 nc-184-3-104-1.dhcp.embarqhsd.net [184.3.104.1]
    3 71-32-28-177.rcmt.qwest.net [71.32.28.177]
    4 bst-edge-05.inet.qwest.net [67.14.30.126]
    5 65.120.117.250
    6 border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    7 perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    8 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 200 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 PC
    0/ 100 = 0% |
    1 1ms 0/ 100 = 0% 0/ 100 = 0% dslrouter.westell.com [10.0.0.1]
    0/ 100 = 0% |
    2 74ms 0/ 100 = 0% 0/ 100 = 0% nc-184-3-104-1.dhcp.embarqhsd.net[184.3.104.1]
    0/ 100 = 0% |
    3 77ms 1/ 100 = 1% 1/ 100 = 1% 71-32-28-177.rcmt.qwest.net [71.32.28.177]
    0/ 100 = 0% |
    4 --- 100/ 100 =100% 100/ 100 =100% bst-edge-05.inet.qwest.net [67.14.30.126]
    0/ 100 = 0% |
    5 93ms 0/ 100 = 0% 0/ 100 = 0% 65.120.117.250
    0/ 100 = 0% |
    6 99ms 1/ 100 = 1% 1/ 100 = 1% border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    0/ 100 = 0% |
    7 113ms 0/ 100 = 0% 0/ 100 = 0% perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    1/ 100 = 1% |
    8 104ms 1/ 100 = 1% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]
    Trace complete.

    ...

    So 'Path Ping' shows what the problem is... Packet Drop along the Qwest Communications backbone, starting with just after the gateway from your local ISP to the Qwest Backbone.

    You could contact your ISP and see if they can talk to Qwest about the packet drop on their backbone (as your ISP is paying for the Qwest Backbone bandwidth...)

    You could also try the 'Proxy' options in the Launcher Options Menu, to see if this can bypass the congestion on the Qwest Backbone (This May or May Not work, but it doesn't hurt to try, as you can always change the settings back if it doesn't work...)
Sign In or Register to comment.