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

Fatal Error: Unable to initialize on-demand patching and connect to the Patch Server;

2

Comments

  • slayerofbloodslayerofblood Member Posts: 18 Arc User
    edited November 2013
    Oh, that's dandy. And here I thought upgrading to Hughes.net would maybe fix the problem. Hardy-har-har... Thought maybe it was Wildblue fazing out my state giving me issues.

    Also, anyone else get a "please refrain from sending tickets with information already contained in our system" email? I thought maybe I'd submitted two tickets, but no, I didn't... [EDIT] I just realized that they deleted my ticket, too... *Rageface*

    Also tried the disconnect modem from power supply trick mentioned, and it doesn't work. I left it off for two solid days (gasp!) and no go.

    *taps fingers irately on desk*
    FED TAC: Ty'irren Micybos, USS Mistake Not... NX-93023.
  • mook22mook22 Member Posts: 3 Arc User
    edited December 2013
    i had same problem .i got it to work.the only thing i did was download few games wed.and i deleted all them today lol. and some how its working again
  • slayerofbloodslayerofblood Member Posts: 18 Arc User
    edited December 2013
    mook22 wrote: »
    i had same problem .i got it to work.the only thing i did was download few games wed.and i deleted all them today lol. and some how its working again


    Maybe new month=problem fixed?

    Edit: Nope. Still the same problem. Anyone else getting the "Game has encountered a problem, would you like to verify the files?" error message just before patching starts?
    FED TAC: Ty'irren Micybos, USS Mistake Not... NX-93023.
  • draconissnoctumdraconissnoctum Member Posts: 0 Arc User
    edited December 2013
    slayerofblood wrote: »
    Maybe new month=problem fixed?

    Edit: Nope. Still the same problem. Anyone else getting the "Game has encountered a problem, would you like to verify the files?" error message just before patching starts?

    I get that I was in the other forums for crashing until I realized no-one else had my ticket #. I have wildblue also and had no problems until season 8. Also had my laptop along on vacation to do the updates without using my bandwidth, logged on and it worked today at home same crashing problem. So glad I'm not alone...sad we are stuck here
  • slayerofbloodslayerofblood Member Posts: 18 Arc User
    edited December 2013
    draconissnoctum wrote: »
    I get that I was in the other forums for crashing until I realized no-one else had my ticket #. I have wildblue also and had no problems until season 8. Also had my laptop along on vacation to do the updates without using my bandwidth, logged on and it worked today at home same crashing problem. So glad I'm not alone...sad we are stuck here

    If my laptop had the MRAM/CPU power and OS to handle STO, I'd probably download it and go sit in the Safeway parking lot to play, since wireless works just fine... *Chuckles* Thinking seriously about downloading Neverwinter to see if it at least works... but what will happen to my speed? Yours?! *laughs* Don't you just love being on an outdated system with rolling usage rates? *Taps fingers*
    FED TAC: Ty'irren Micybos, USS Mistake Not... NX-93023.
  • lapsanszki96lapsanszki96 Member Posts: 4 Arc User
    edited December 2013
    So we are going to sit here and wait to fix the game? Great! That is just greay!
    :eek:
  • draconissnoctumdraconissnoctum Member Posts: 0 Arc User
    edited December 2013
    lapsanszki96 wrote: »
    So we are going to sit here and wait to fix the game? Great! That is just greay!
    :eek:

    I've gotten some troubleshooting emails from them but now that I think ive tracked it down to the Sat connection I hope they can figure out what they did with season 8 that stopped sat connections from being able to connect, because after almost 3 years of playing this just fine on a sat connection I am not going to buy the "STO is just not playable on sat" excuse. It worked before it was a bit laggy but it worked...
  • lapsanszki96lapsanszki96 Member Posts: 4 Arc User
    edited December 2013
    I've gotten some troubleshooting emails from them but now that I think ive tracked it down to the Sat connection I hope they can figure out what they did with season 8 that stopped sat connections from being able to connect, because after almost 3 years of playing this just fine on a sat connection I am not going to buy the "STO is just not playable on sat" excuse. It worked before it was a bit laggy but it worked...

    Well thanks...at least i know that i can't do anything about it...
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    I give up. This is the latest response for my Ticket.....

    Hello,

    Do make sure to disable any progam that isn't needed to run the game, including Raptr. Check for any driver updates as well as Windows Updates.

    The developers have suggested trying the following:

    1) Verify all files, and try again
    2) Reboot and verify all files, and try again (this can be skipped)
    3) Reinstall, and try again

    Regards,

    The Perfect World Tech Support Team
    https://support.perfectworld.com/
    http://techsupport.perfectworld.com/

    Are you kidding me?

    I already said in my ticked that I did this. :mad:
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    Patch Notes for tomorrow...
    Resolved issue some players to crash at loading screen (including those with crash #18897741).

    Hope this will fix the problem :(
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    Today's patch has not resolved my launch issue. :mad:

    http://sto.perfectworld.com/news/?p=1055611

    I have been unable to play since S8 started.
    I have been playing since launch and have a LTS :mad:
  • plowboy1dplowboy1d Member Posts: 8 Arc User
    edited December 2013
    Didn't work for me either, this is getting ridiculous:mad:
  • seannewboyseannewboy Member Posts: 667 Arc User
    edited December 2013
    I just started having this problem 12-6.
    New home of the Romulan Republic.
    I have an idea for what Season 11 should be; Season 11: The Big Bug Fix.
    I have not been able to read my bug tickets in over a year, not even the tickets about not being able to see my tickets.
    I find the drama of your signature proof of your immaturity, this means you, DR whiners.
  • slayerofbloodslayerofblood Member Posts: 18 Arc User
    edited December 2013
    Decided I should test the theory that it is only STO that isn't running on Sat. Went to friend's place again, downloaded Neverwinter. Unbeknownst to me, they had a module release same day. Works fine on cable, but home with Sat, same issue as STO. Now I'm wondering if any of you running other CRYPTIC games can play them? Any games with new seasons/patch releases not work?

    Still downloading newest patch for STO, so unknown if it works yet.
    FED TAC: Ty'irren Micybos, USS Mistake Not... NX-93023.
  • kojirohellfirekojirohellfire Member Posts: 1,606 Arc User
    edited December 2013
    I just got this on the patch today. Same for Champions as well, which also had a winter patch.
  • draconissnoctumdraconissnoctum Member Posts: 0 Arc User
    edited December 2013
    slayerofblood wrote: »
    Decided I should test the theory that it is only STO that isn't running on Sat. Went to friend's place again, downloaded Neverwinter. Unbeknownst to me, they had a module release same day. Works fine on cable, but home with Sat, same issue as STO. Now I'm wondering if any of you running other CRYPTIC games can play them? Any games with new seasons/patch releases not work?

    Still downloading newest patch for STO, so unknown if it works yet.

    So today I got my latest email from cryptic with their brilliant problem solving ideas...."you may just have to wait and try again later." took every ounce of self control not to scream at my computer....

    When originally searching for this problem I found that Neverwinter players had it like a year or so ago.
  • quickbuckquickbuck Member Posts: 6 Arc User
    edited December 2013
    jkstocbr wrote: »
    Wow got a support ticket response after 2 days ...

    Will try this tonight

    I tried it and after replacing the launcher it's even worse.
    "Trying to update the launcher.
    Please be patient.
    Tried to connect 5 times."

    Then it's stuck there.

    Seriously, what's going on?
  • cilcoynecilcoyne Member Posts: 4 Arc User
    edited December 2013
    I haven't played STO in months. I wouldn't know if in my case it's because of S8 because I wasn't playing immediately before then. My issue is pretty much identical to what jkstocbr has described and I'm also on a sat connection with NBN iiNet. University is finally over and I'm going insane without my sto...
  • maximilianthevmaximilianthev Member Posts: 7 Arc User
    edited December 2013
    Don't get your hopes up on getting it fixed..lots of us haven't been able too get into the game since season 8 started..its either the launcher not working..crash to desktop on the Cryptic loading screen or crash to desktop on the character choose screen....every attempt they did resulted in nothing getting fixed and now that they have closed the "crash to desktop" post thread it seems Cryptic is washing their hands in innocence and giving us the middle finger by saying "sorry cant help you it must be you then..BYE !!!" I played perfectly hours before the S8 patch and after the patch BAM..nothing...yeah ..its our fault...jeesh where do they get these people..
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    Here is an update...

    After support suggesting I reinstall, reboot and force verify 3 times, I finally convinced them it is a connectivity issue, not an installation issue. I can launch on my laptop at a friends house (ADSL) but not at home (SAT).

    The suggested Tracert to the regular locations worked;
    - patchserver.crypticstudios.com [208.95.185.41] ... OK
    - controllertracker.crypticstudios.com [208.95.185.166] ... OK
    - support.crypticstudios.com [208.95.185.46] ... OK


    Except a new one they suggested which failed ....


    C:\>tracert 208.95.184.0

    Tracing route to 208.95.184.0 over a maximum of 30 hops

    1 1 ms <1 ms <1 ms 192.168.1.1
    2 1 ms 1 ms 1 ms 220-235-121-177.dyn.iinet.net.au [220.235.121.177]
    3 591 ms 679 ms 619 ms 10.253.50.78
    4 628 ms 639 ms 639 ms 10.253.50.124
    5 728 ms 709 ms 735 ms 10.250.50.1
    6 724 ms 779 ms 758 ms 10.250.50.30
    7 657 ms 709 ms 729 ms gi3-35.syd-mas-bdr2.on.iinet.net.au [203.215.18.42]
    8 668 ms 718 ms * po3-100.syd-mas-bdr1.on.ii.net [203.215.20.153]
    9 778 ms 719 ms 699 ms ae2.syd-mas-core1.on.ii.net [203.215.20.94]
    10 670 ms 787 ms * xe-7-0-10-10.br1.syd4.on.ii.net [150.101.33.100]
    11 879 ms 899 ms 919 ms te0-1-1-2.bd1.lax1.on.ii.net [203.16.213.65]
    12 868 ms 908 ms 839 ms los-brdr-01.inet.qwest.net [63.146.27.41]
    13 * * * Request timed out.
    14 903 ms 908 ms 899 ms 65.120.117.250
    15 929 ms 939 ms 990 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    16 908 ms 919 ms 919 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    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.


    ... now waiting what support have to say
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited December 2013
    jkstocbr wrote: »
    ...


    C:\>tracert 208.95.184.0

    Tracing route to 208.95.184.0 over a maximum of 30 hops

    1 1 ms <1 ms <1 ms 192.168.1.1
    2 1 ms 1 ms 1 ms 220-235-121-177.dyn.iinet.net.au [220.235.121.177]
    3 591 ms 679 ms 619 ms 10.253.50.78
    4 628 ms 639 ms 639 ms 10.253.50.124
    5 728 ms 709 ms 735 ms 10.250.50.1
    6 724 ms 779 ms 758 ms 10.250.50.30
    7 657 ms 709 ms 729 ms gi3-35.syd-mas-bdr2.on.iinet.net.au [203.215.18.42]
    8 668 ms 718 ms * po3-100.syd-mas-bdr1.on.ii.net [203.215.20.153]
    9 778 ms 719 ms 699 ms ae2.syd-mas-core1.on.ii.net [203.215.20.94]
    10 670 ms 787 ms * xe-7-0-10-10.br1.syd4.on.ii.net [150.101.33.100]
    11 879 ms 899 ms 919 ms te0-1-1-2.bd1.lax1.on.ii.net [203.16.213.65]
    12 868 ms 908 ms 839 ms los-brdr-01.inet.qwest.net [63.146.27.41]
    13 * * * Request timed out.
    14 903 ms 908 ms 899 ms 65.120.117.250
    15 929 ms 939 ms 990 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    16 908 ms 919 ms 919 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    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.


    ... now waiting what support have to say

    Over half a second delay the moment the packet enters your ISP private network!! Before it even hits the public Internet!!! Support won't be able to do anything about this....

    I would suggest reboot/power cycle your ISP router/gateway and try again. If this does not improve the condition, then you will have to contact your ISP and ask why your router is not working correctly...
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    grouchyotaku wrote: »
    Over half a second delay the moment the packet enters your ISP private network!! Before it even hits the public Internet!!! Support won't be able to do anything about this....

    I would suggest reboot/power cycle your ISP router/gateway and try again. If this does not improve the condition, then you will have to contact your ISP and ask why your router is not working correctly...

    Why?

    It's very normal for Satellite just like others in this thread.

    It worked without any problem before Season 8 (but had this issue on Tribble).

    I can play Champions Online currently without any issue (not to mention other MMO's like SWTOR TSW)
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited December 2013
    jkstocbr wrote: »
    Why?
    ....

    If you look at this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155

    ... you will see that 180ms is the recommended upper limit on latency. Considering that the STO Client and Servers have to stay in Synch within a fraction of a second, a latency of over 9 tenths of a second is starting to risk IP packet lifetime timeout...

    This is also the reason why the vast majority of Internet traffic uses ocean cable instead of satellite, considering the Geo-synchronous orbit is two thirds of the way to the Moon...
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    grouchyotaku wrote: »
    If you look at this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155

    ... you will see that 180ms is the recommended upper limit on latency. Considering that the STO Client and Servers have to stay in Synch within a fraction of a second, a latency of over 9 tenths of a second is starting to risk IP packet lifetime timeout...

    This is also the reason why the vast majority of Internet traffic uses ocean cable instead of satellite, considering the Geo-synchronous orbit is two thirds of the way to the Moon...

    Yeah I know.

    180ms is nice on paper but excludes the majority of people outside USA, like us Aussies. As an example, here is a typically Tracert from my work on a ADSL2 connection ....
    computers-imac:~ Computer42$ traceroute 208.95.185.41
    traceroute to 208.95.185.41 (208.95.185.41), 64 hops max, 52 byte packets
    1 10.0.0.138 (10.0.0.138) 0.773 ms 0.450 ms 0.467 ms
    2 gw8.dkn5.canberra.telstra.net (203.45.244.1) 106.055 ms 104.501 ms 59.238 ms
    3 tengigabitethernet0-8-0-2.civ-core2.canberra.telstra.net (203.50.10.129) 29.529 ms 96.501 ms 219.120 ms
    4 bundle-ether15.chw-core2.sydney.telstra.net (203.50.6.81) 102.446 ms 87.202 ms 146.801 ms
    5 bundle-ether1.oxf-gw2.sydney.telstra.net (203.50.6.90) 81.201 ms 120.022 ms 80.303 ms
    6 203.50.9.46 (203.50.9.46) 68.049 ms 35.325 ms 48.139 ms
    7 i-0-3-2-0.sydo-core02.bi.telstraglobal.net (202.84.220.189) 70.453 ms
    i-0-6-0-6.sydo-core02.bi.telstraglobal.net (202.84.223.38) 91.858 ms *
    8 i-0-2-0-1.1wlt-core01.bx.telstraglobal.net (202.84.249.50) 226.280 ms *
    i-0-2-0-5.1wlt-core01.bx.telstraglobal.net (202.84.140.202) 295.344 ms
    9 i-0-4-0-0.eqla01.bi.telstraglobal.net (202.84.251.174) 247.230 ms
    i-0-4-0-6.eqla01.bi.telstraglobal.net (202.40.149.250) 301.286 ms *
    10 cogent-peer.eqla01.pr.telstraglobal.net (134.159.63.198) 379.819 ms * 351.513 ms
    11 be2181.mpd21.lax01.atlas.cogentco.com (154.54.41.113) 252.187 ms
    be2180.ccr21.lax01.atlas.cogentco.com (154.54.41.57) 249.700 ms
    be2181.mpd21.lax01.atlas.cogentco.com (154.54.41.113) 240.530 ms
    12 be2067.mpd21.iah01.atlas.cogentco.com (154.54.7.161) 264.815 ms
    be2068.mpd22.iah01.atlas.cogentco.com (154.54.7.157) 350.830 ms
    be2066.ccr22.iah01.atlas.cogentco.com (154.54.7.53) 421.551 ms
    13 be2174.mpd21.atl01.atlas.cogentco.com (154.54.29.201) 421.515 ms
    be2175.mpd22.atl01.atlas.cogentco.com (154.54.29.221) 493.989 ms
    be2173.ccr22.atl01.atlas.cogentco.com (154.54.29.117) 370.966 ms
    14 be2169.ccr22.dca01.atlas.cogentco.com (154.54.31.98) 434.423 ms 322.677 ms
    be2170.mpd21.dca01.atlas.cogentco.com (154.54.31.106) 402.044 ms
    15 be2149.ccr22.jfk02.atlas.cogentco.com (154.54.31.126) 346.605 ms
    be2150.mpd21.jfk02.atlas.cogentco.com (154.54.31.130) 375.784 ms
    be2148.ccr21.jfk02.atlas.cogentco.com (154.54.31.118) 367.840 ms
    16 be2094.ccr21.bos01.atlas.cogentco.com (154.54.30.14) 425.441 ms
    be2095.ccr21.bos01.atlas.cogentco.com (154.54.30.38) 411.297 ms
    be2094.ccr21.bos01.atlas.cogentco.com (154.54.30.14) 318.686 ms
    17 te3-2.ccr01.bos06.atlas.cogentco.com (154.54.46.130) 355.091 ms
    te4-2.ccr01.bos06.atlas.cogentco.com (66.28.4.254) 312.609 ms 408.180 ms
    18 38.111.40.114 (38.111.40.114) 356.891 ms 430.331 ms 306.824 ms
    19 patchserver2.crypticstudios.com (208.95.185.41) 337.043 ms 481.834 ms 371.870 ms


    But the fact is that I can still connect and pay CO without any problems. I played STO for the last 6 months on my slow Satellite connection without drama other than the occasional minor rubberbanding (3 years prior on ADSL2). The week leading up to S8 I could play Holodeck but not Tribble. Now the issue has moved to tribble. There are other players in this thread based in USA also using Satellite with the same problem.
  • cilcoynecilcoyne Member Posts: 4 Arc User
    edited December 2013
    I can't believe that Cryptic would neglect us. Seeing that other thread which had thousands of posts on it since s8 being closed, even though people still have unsolved issues, was annoying to say the least. Missing this game a lot and I've tried everything.
  • slayerofbloodslayerofblood Member Posts: 18 Arc User
    edited December 2013
    draconissnoctum wrote: »
    So today I got my latest email from cryptic with their brilliant problem solving ideas...."you may just have to wait and try again later." took every ounce of self control not to scream at my computer....

    When originally searching for this problem I found that Neverwinter players had it like a year or so ago.



    Peachy.... And yet Champions works? I wonder how many other games are going to end up a frelling waste of disk space..?

    What I don't get is that I could play STO through the first couple days of the S8 patch, but I never actually played the missions in the patch. I did that at my BF's place, and then BAM! it stopped working, probably a week after the patch release...

    Also, I'm now curious and want to run a "Tracert" but am pulling a blank on how to do so... help? I pinged "208.95.184.0" to see if I could get anything at all, but each and every packet was lost.
    FED TAC: Ty'irren Micybos, USS Mistake Not... NX-93023.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited December 2013
    slayerofblood wrote: »
    ...

    Also, I'm now curious and want to run a "Tracert" but am pulling a blank on how to do so... help?

    Look at this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155

    And if you can, try substituting the 'pathping' command for the 'tracert' command and post those results, to see if you are suffering from packet drop on your connection...
  • slayerofbloodslayerofblood Member Posts: 18 Arc User
    edited December 2013
    grouchyotaku wrote: »
    Look at this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155

    And if you can, try substituting the 'pathping' command for the 'tracert' command and post those results, to see if you are suffering from packet drop on your connection...

    *Facepalm* Duh. Computer tech and I end up having to read the instructions anyway... :o All I needed was the destination. Heh. Thanks.

    Tracert Results:
    C:\>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.1.1
    2 1321 ms 1424 ms 1380 ms 10.0.128.1
    3 1463 ms 916 ms 1364 ms 10.246.20.17
    4 1395 ms 1462 ms 1412 ms 10.246.30.21
    5 1400 ms 1318 ms 1443 ms 10.246.30.1
    6 1465 ms 1410 ms 1408 ms 10.246.100.2
    7 2107 ms 1557 ms 1380 ms 10.246.110.2
    8 1528 ms 1426 ms 1360 ms chy-edge-04.inet.qwest.net [72.164.128.69]
    9 1684 ms 1390 ms 1814 ms chy-core-02.inet.qwest.net [205.171.158.102]
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 1533 ms 1529 ms 1535 ms bst-edge-05.inet.qwest.net [67.14.30.130]
    13 2083 ms 1479 ms 1509 ms 65.120.117.250
    14 1407 ms 1408 ms 1497 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    15 1613 ms 1640 ms 1510 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    16 2145 ms 1500 ms 1416 ms patchserver2.crypticstudios.com [208.95.185.41]

    Trace complete.

    PathPing Results:
    C:\>pathping patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 OWNER-PC.wildblue.com [192.168.1.104]
    1 192.168.1.1
    2 10.0.128.1
    3 10.246.20.17
    4 10.246.30.21
    5 10.246.30.1
    6 10.246.100.2
    7 10.246.110.2
    8 chy-edge-04.inet.qwest.net [72.164.128.69]
    9 chy-core-02.inet.qwest.net [205.171.158.102]
    10 * * *
    Computing statistics for 225 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 OWNER-PC.wildblue.com [192.168.1.104]
    0/ 100 = 0% |
    1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 --- 100/ 100 =100% 100/ 100 =100% 10.0.128.1
    0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% 10.246.20.17
    0/ 100 = 0% |
    4 --- 100/ 100 =100% 100/ 100 =100% 10.246.30.21
    0/ 100 = 0% |
    5 --- 100/ 100 =100% 100/ 100 =100% 10.246.30.1
    0/ 100 = 0% |
    6 --- 100/ 100 =100% 100/ 100 =100% 10.246.100.2
    0/ 100 = 0% |
    7 --- 100/ 100 =100% 100/ 100 =100% 10.246.110.2
    0/ 100 = 0% |
    8 1439ms 0/ 100 = 0% 0/ 100 = 0% chy-edge-04.inet.qwest.net [72.164.128.69]
    0/ 100 = 0% |
    9 1671ms 0/ 100 = 0% 0/ 100 = 0% chy-core-02.inet.qwest.net [205.171.158.102]

    Trace complete.


    Looking at this, I think I must have the worst connection of everyone here...

    For the heck of it, ran nettest.exe too:
    contacting nettest server..
    Local IP: 75.104.42.178
    Ping: 1500.0 msec
    Port: 80: 150 KB/sec 3 KB/sec 158 KB/sec 500
    Port: 80: 160 KB/sec 4 KB/sec 169 KB/sec 500
    Port: 443: 132 KB/sec 3 KB/sec 140 KB/sec 500
    Port: 443: timed out
    Port: 7255: timed out
    Port: 7255: timed out
    Port: 7003: timed out
    Port: 7003: timed out
    Port: 7202: timed out
    Port: 7202: timed out
    Port: 7499: timed out
    Port: 7499: timed out
    Port: 80: 124 KB/sec 2 KB/sec 131 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec

    *Mad, despairing laughter*
    FED TAC: Ty'irren Micybos, USS Mistake Not... NX-93023.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited December 2013
    slayerofblood wrote: »
    *Facepalm* Duh. Computer tech and I end up having to read the instructions anyway... :o All I needed was the destination. Heh. Thanks.

    Tracert Results:

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 1321 ms 1424 ms 1380 ms 10.0.128.1

    So the first hop is your router...
    The second hop is your ISP modem/gateway with a greater then 1.3 second delay.... with 0.18 seconds the recommended upper limit for network latency... hmmmmm....

    Try rebooting/powercycling the modem/gateway and see if this improves things...

    If it doesn't, then you should contact your ISP and have them send someone to take a look at that modem/gateway...
  • jkstocbrjkstocbr Member Posts: 0 Arc User
    edited December 2013
    I have changed ISP's (which took 8 weeks since my application) and I am now able to connect to STO at last! Still no idea what was causing the problem in the first place. This last resort may work for others that are having this problem.
Sign In or Register to comment.