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

Cryptic Launcher Autoupdate Problem

1…6465676970…102

Comments

  • psymantispsymantis Member Posts: 329 Arc User
    edited January 2013
    Also unable to connect until I use a VPN like others in the thread. The (recent) problems starting happening yesterday but only went completing f'ed today. As soon as I disconnect the VPN the server disconnects.
  • linyivelinyive Member Posts: 1,086 Arc User
    edited January 2013
    hanover2 wrote: »
    Apparently a few people are having some success with ridiculous workarounds like cell phone tethering and 3rd party network software. That's nothing the "Team" has any business asking us to do just to wring some functionality out of their product, and so I won't.
    I agree. Unless the product works as intended, using a workaround will not solve the actual issue.
  • origcaptainquackorigcaptainquack Member Posts: 614 Arc User
    edited January 2013
    conspiracy? maybe, kinda, sorta. but i need bran flakes to send me a private message so i can reply with the problem as i earesed her last message and dont have a way to message her.
  • rcottamrcottam Member Posts: 3 Arc User
    edited January 2013
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\*****>tracert launcher.startrekonline.com

    Tracing route to launcher.startrekonline.com [208.95.185.44]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms BTHomeHub.home
    2 6 ms 6 ms 6 ms 217.32.143.224
    3 7 ms 6 ms 6 ms 217.32.144.14
    4 8 ms 8 ms 8 ms 213.120.181.214
    5 27 ms 9 ms 9 ms 217.41.169.59
    6 9 ms 9 ms 9 ms 217.41.169.107
    7 8 ms 8 ms 7 ms acc1-10GigE-9-3-0.sf.21cn-ipp.bt.net [109.159.25
    1.95]
    8 16 ms 15 ms 16 ms core1-te0-0-0-7.ealing.ukcore.bt.net [109.159.25
    1.33]
    9 12 ms 12 ms 12 ms transit1-pos1-0-0.telehouse.ukcore.bt.net [62.6.
    201.82]
    10 100 ms 14 ms 14 ms 166-49-211-153.eu.bt.net [166.49.211.153]
    11 14 ms 14 ms 14 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
    12 20 ms 19 ms 20 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
    7.14.49]
    13 18 ms 19 ms 20 ms te0-0-0-4.mpd21.lon13.atlas.cogentco.com [154.54
    .57.102]
    14 98 ms 98 ms 95 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com [154.5
    4.1.93]
    15 86 ms 86 ms 86 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    16 * * * Request timed out.
    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 * ^C
    C:\Users\*****>ping launcher.startrekonline.com

    Pinging launcher.startrekonline.com [208.95.185.44] with 32 bytes of data:
    Request timed out.
    Request timed out.

    Ping statistics for 208.95.185.44:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
    Control-C
    ^C
    C:\Users\*****>pathping launcher.startrekonline.com

    Tracing route to launcher.startrekonline.com [208.95.185.44]
    over a maximum of 30 hops:
    0 A*****tic
    1 BTHomeHub.home
    2 217.32.143.224
    3 217.32.144.14
    4 213.120.181.214
    5 217.41.169.59
    6 217.41.169.107
    7 acc1-10GigE-9-3-0.sf.21cn-ipp.bt.net [109.159.251.95]
    8 core1-te0-0-0-7.ealing.ukcore.bt.net [109.159.251.33]
    9 transit1-pos1-0-0.telehouse.ukcore.bt.net [62.6.201.82]
    10 166-49-211-153.eu.bt.net [166.49.211.153]
    11 t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
    12 te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.117.14.49]
    13 te0-5-0-3.mpd21.lon13.atlas.cogentco.com [154.54.74.42]
    14 te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.4.189]
    15 te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
    16 38.111.40.114
    17 * * *
    Computing statistics for 400 seconds...
    ^C
    C:\Users\*****>nslookup launcher.startrekonline.com
    Server: BTHomeHub.home
    Address: 192.168.1.254

    Non-authoritative answer:
    Name: launcher.startrekonline.com
    Address: 208.95.185.44


    C:\Users\*****>ping 208.95.185.44

    Pinging 208.95.185.44 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 208.95.185.44:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\*****>
  • evilmatt666evilmatt666 Member Posts: 0 Arc User
    edited January 2013
    I think somebody somewhere has a coffee cup they're hoping no one notices is broken and is busily trying to get rid of the coffee stains on the backs of the router stacks.
  • kahless4kahless4 Member Posts: 12 Arc User
    edited January 2013
    contacting nettest server..
    Local IP: 90.197.79.116
    Ping: 107.2 msec
    Port: 80: 521 KB/sec 10 KB/sec 548 KB/sec 500
    Port: 80: 511 KB/sec 15 KB/sec 539 KB/sec 500
    Port: 443: 481 KB/sec 21 KB/sec 511 KB/sec 500
    Port: 443: 476 KB/sec 20 KB/sec 502 KB/sec 500
    Port: 7255: 479 KB/sec 20 KB/sec 505 KB/sec 500
    Port: 7255: 476 KB/sec 20 KB/sec 502 KB/sec 500
    Port: 7003: 480 KB/sec 20 KB/sec 511 KB/sec 500
    Port: 7003: 478 KB/sec 20 KB/sec 505 KB/sec 500
    Port: 7202: 474 KB/sec 20 KB/sec 501 KB/sec 500
    Port: 7202: 486 KB/sec 20 KB/sec 514 KB/sec 500
    Port: 7499: 477 KB/sec 20 KB/sec 503 KB/sec 500
    Port: 7499: 477 KB/sec 20 KB/sec 504 KB/sec 500
    Port: 80: 519 KB/sec 15 KB/sec 548 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit
  • manw3manw3 Member Posts: 0 Arc User
    edited January 2013
    contacting nettest server..
    Local IP: **.***.***.***
    Ping: 100.3 msec
    Port: 80: 259 KB/sec 10 KB/sec 273 KB/sec 500
    Port: 80: 319 KB/sec 14 KB/sec 338 KB/sec 500
    Port: 443: 252 KB/sec 11 KB/sec 279 KB/sec 500
    Port: 443: 104 KB/sec 9 KB/sec 138 KB/sec 500
    Port: 7255: 137 KB/sec 6 KB/sec 147 KB/sec 500
    Port: 7255: 268 KB/sec 11 KB/sec 284 KB/sec 500
    Port: 7003: 608 KB/sec 20 KB/sec 642 KB/sec 500
    Port: 7003: 588 KB/sec 20 KB/sec 621 KB/sec 500
    Port: 7202: 614 KB/sec 22 KB/sec 649 KB/sec 500
    Port: 7202: 275 KB/sec 12 KB/sec 291 KB/sec 500
    Port: 7499: 133 KB/sec 5 KB/sec 141 KB/sec 500
    Port: 7499: 364 KB/sec 14 KB/sec 385 KB/sec 500
    Port: 80: 613 KB/sec 22 KB/sec 648 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit

    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 135 ms 1 ms 1 ms BThomehub.home [***.***.*.***]
    2 10 ms 10 ms 9 ms 217.32.141.3
    3 10 ms 10 ms 10 ms 217.32.140.206
    4 15 ms 15 ms 15 ms 217.41.216.130
    5 15 ms 15 ms 14 ms 31.55.164.47
    6 15 ms 14 ms 15 ms 31.55.164.107
    7 19 ms 19 ms 18 ms acc1-10GigE-0-2-0-4.bm.21cn-ipp.bt.net [109.159.
    248.104]
    8 142 ms 146 ms 143 ms core1-te0-15-0-15.ealing.ukcore.bt.net [109.159.
    248.40]
    9 19 ms 18 ms 19 ms transit1-pos1-0-0.telehouse.ukcore.bt.net [62.6.
    201.82]
    10 143 ms 144 ms 145 ms 166-49-211-157.eu.bt.net [166.49.211.157]
    11 141 ms 141 ms 144 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.49]
    12 142 ms 143 ms 145 ms te0-7-0-3.ccr21.lon01.atlas.cogentco.com [130.11
    7.14.49]
    13 29 ms 136 ms 148 ms te0-5-0-3.mpd21.lon13.atlas.cogentco.com [154.54
    .74.42]
    14 101 ms 98 ms 100 ms te0-7-0-33.ccr21.bos01.atlas.cogentco.com [154.5
    4.5.161]
    15 125 ms 204 ms 211 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
    134]
    16 * * * Request timed out.
    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 * * 101 ms 208.95.185.41

    Trace complete.

    C:\Windows\system32>

    no change with ipconfig/release/renew.
  • hagar3hagar3 Member Posts: 145 Arc User
    edited January 2013
    evilmatt666 wrote: »
    I think somebody somewhere has a coffee cup they're hoping no one notices is broken and is busily trying to get rid of the coffee stains on the backs of the router stacks.

    did anybody think to tell them that the little tray that comes out at the front is a dvd drive and not a coffee cup lol
    In case no one can hear you...scream
  • shawnkazishawnkazi Member Posts: 0 Arc User
    edited January 2013
    Same issue since today = 01/28/2013. Upon executing launcher, I see a message saying it's attempting to connect to the patch server, and after 2 attempts, I see an error message saying there's a connection problem and to contact support. Here's my trace route info:

    Tracing route to launcher.startrekonline.com [208.95.185.44] over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
    2 5 ms 6 ms 7 ms L100.NYCMNY-VFTTP-175.verizon-gni.net [71.167.34.1]
    3 6 ms 7 ms 6 ms G0-10-5-3.NYCMNY-LCR-22.verizon-gni.net [130.81.104.206]
    4 77 ms 15 ms 6 ms ae0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.209.126]
    5 10 ms 6 ms 10 ms 0.so-0-0-0.XT2.NYC4.ALTER.NET [152.63.17.21]
    6 20 ms 18 ms 18 ms 0.ge-7-0-0.XL4.BOS4.ALTER.NET [152.63.3.89]
    7 16 ms 18 ms 18 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
    8 27 ms 30 ms 30 ms internap-gw.customer.alter.net [65.207.236.58]
    9 26 ms 26 ms 25 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    10 28 ms 35 ms 34 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    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.

    Trace complete.
  • papabloodpapablood Member Posts: 6 Arc User
    edited January 2013
    I had this exact issue last week ... Did not want to send a ticket because we all know how slow they are answered so spent 3 hrs searching thru the support section and the forums until I ran across this in a forum post ... http://files.startrekonline.com/launcher/Star%20Trek%20Online.exe

    I downloaded it and installed it and other than the PC asking me everytime if I wanna run it it works just fine ....
    [SIGPIC][/SIGPIC]Target locked Captain....Alpha loaded....5,4,3,2,1.... Target dead captain, locking on next target
  • nighttremornighttremor Member Posts: 1 Arc User
    edited January 2013
    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 [192.168.1.1]
    2 8 ms 6 ms 6 ms L100.TAMPFL-VFTTP-22.verizon-gni.net [71.243.
    .1]
    3 10 ms 9 ms 12 ms G0-14-2-4.TAMPFL-LCR-22.verizon-gni.net [130.
    212.62]
    4 13 ms 11 ms 12 ms so-4-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130
    .199.28]
    5 63 ms 61 ms 61 ms so-0-1-0-0.BOS-BB-RTR2.verizon-gni.net [130.8
    9.67]
    6 66 ms 64 ms 74 ms 0.ge-1-0-0.XL4.BOS4.ALTER.NET [152.63.19.245]
    7 63 ms 59 ms 61 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
    8 65 ms 64 ms 64 ms internap-gw.customer.alter.net [65.207.236.58
    9 66 ms 64 ms 64 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.12
    04]
    10 66 ms 69 ms 69 ms perfectworldent-4.border11.bsn.pnap.net [216.
    61.78]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    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.

    Trace complete.
  • klaituklaitu Member Posts: 0 Arc User
    edited January 2013
    Well, it seems that Crypic sold the magic troubleshooting lamp to PWE during the merger, and that this is ultimately the cause for everything.
  • dukhatnaranekdukhatnaranek Member Posts: 24 Arc User
    edited January 2013
    Even though I can get in and play through my VPN, I'm getting a lot of "server not responding" messages during hot patching. The patches finish eventually, but seriously slow. Don't know if this means anything, but maybe?
  • fihillfihill Member Posts: 40 Arc User
    edited January 2013
    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 8 ms 7 ms 7 ms 10.247.160.1
    3 26 ms 47 ms 40 ms elpstxh6-rtr2.elp.rr.com [24.92.98.57]
    4 58 ms 48 ms 47 ms tge8-2.elpstx1-er02.texas.rr.com [24.175.60.219]

    5 26 ms 23 ms 23 ms tge0-8-0-1.elpstxhe-cr01.texas.rr.com [24.175.60
    .156]
    6 25 ms 23 ms 23 ms agg25.dllatxl3-cr01.texas.rr.com [24.175.60.220]

    7 32 ms 31 ms 31 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
    8 29 ms 26 ms 26 ms 107.14.17.232
    9 26 ms 23 ms 34 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
    4.11.49]
    10 24 ms 35 ms 23 ms te0-5-0-4.ccr21.dfw01.atlas.cogentco.com [154.54
    .88.74]
    11 33 ms 35 ms 33 ms te0-2-0-6.mpd21.mci01.atlas.cogentco.com [154.54
    .46.181]
    12 49 ms 50 ms 51 ms te0-3-0-7.mpd21.ord01.atlas.cogentco.com [154.54
    .84.82]
    13 73 ms 73 ms 74 ms te0-3-0-6.ccr21.bos01.atlas.cogentco.com [154.54
    .43.182]
    14 74 ms 73 ms 74 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
    ]
    15 * * 67 ms 38.111.40.114
    16 * * * Request timed out.
    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.

    Trace complete.
  • tovarintovarin Member Posts: 1 Arc User
    edited January 2013
    Reasonable compensation demand:

    Each member of the Cryptic team should submit apology Haikus for us to mock. Example:

    Rolling out content
    we didn't test enough
    Now they can't connect

    This should keep the rabble amused while they fix whatever they broke.
  • robintayl0rrobintayl0r Member Posts: 5 Arc User
    edited January 2013
    Using Verizon DSL in NY :(
    Tracing route to launcher.startrekonline.com [208.95.185.44]

    over a maximum of 30 hops:


    1 2 ms 1 ms 1 ms dslrouter.westell.com [192.168.1.1]
    2 27 ms 87 ms 24 ms 10.26.9.1
    3 32 ms 23 ms 24 ms G4-0-4-2203.PGHKNY-LCR-02.verizon-gni.net [130.81.196.30]
    4 26 ms 26 ms 36 ms 130.81.22.254
    5 54 ms 36 ms 37 ms ge-3-3-0-0.BOS-BB-RTR2.verizon-gni.net [130.81.23.254]
    6 41 ms 40 ms 39 ms 0.ge-1-1-0.XL4.BOS4.ALTER.NET [152.63.6.153]
    7 46 ms 46 ms 63 ms POS7-0.GW5.BOS4.ALTER.NET [152.63.25.57]
    8 39 ms 40 ms 40 ms internap-gw.customer.alter.net [65.207.236.58]
    9 674 ms 38 ms 38 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
    10 75 ms 49 ms 54 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 43 ms * * forums.startrekonline.com [208.95.185.44]
    15 * * * Request timed out.
    16 * * * Request timed out.
    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.



    Trace complete.
  • animusarcusanimusarcus Member Posts: 0 Arc User
    edited January 2013
    nomorenamesearch wrote: »
    You are a funny person. I like you. :)
    or give us 800 lobi crystals and we call it even unless it takes more then 8 hour then we return to the table to look at some new compensation :) like 1 lockbox key per hour ?
    "Good" and "Evil" are purely subjective concepts, given credence only by the prevailing opinion of the masses
  • willow6912willow6912 Member Posts: 0 Arc User
    edited January 2013
    sindrek wrote: »
    Here, here. I second

    i agree too not that it will happen
  • sindreksindrek Member Posts: 0 Arc User
    edited January 2013
    papablood wrote: »
    I had this exact issue last week ... Did not want to send a ticket because we all know how slow they are answered so spent 3 hrs searching thru the support section and the forums until I ran across this in a forum post ... http://files.startrekonline.com/launcher/Star%20Trek%20Online.exe

    I downloaded it and installed it and other than the PC asking me everytime if I wanna run it it works just fine ....

    Which forum post, where?
  • inthestarsinthestars Member Posts: 3 Arc User
    edited January 2013
    Seems this isnt regional as im in the uk and have the same issues
  • thlaylierahthlaylierah Member Posts: 2,987 Arc User
    edited January 2013
    captainhundley wrote: »
    In all honesty, we should have known when we saw a MONDAY patch, that something ridiculous like this was going to happen. I tend to overlook a lot of the little anoyances, like how the Thursday patch always occurs during my scheduled mining event of the day, but it's safe to say that we are all displeased. Counting the patchtime, I will be losing at least 8 hours of playtime today.
    Well, I just wanted to gripe for a little while. Thanks for reading.

    It happened on the last patch too, for the same reasons.

    Expect it on every patch from now on.
  • canadianmetalfancanadianmetalfan Member Posts: 50 Arc User
    edited January 2013
    klaitu wrote: »
    Well, it seems that Crypic sold the magic troubleshooting lamp to PWE during the merger, and that this is ultimately the cause for everything.

    and PWE rubbed it the wrong way lol.
    [SIGPIC][/SIGPIC]
    ODYSSEY SCIENCE CRUISER - U.S.S. MAIDEN TORONTO NX-971312-B
    VESTA MULTI-MISSION SURVEILLANCE EXPLORER - U.S.S. HOPE IN HELL NX-902013-A
  • cyralyncyralyn Member Posts: 17 Arc User
    edited January 2013
    Just checking to see if everyone else is still having the same problem. Still going on on my end. Hope they get it fixed before too long.
  • sindreksindrek Member Posts: 0 Arc User
    edited January 2013
    thlaylierah wrote: »
    It happened on the last patch too, for the same reasons.

    Expect it on every patch from now on.

    The guy from Cryptic said it had nothing to do with the patch. This was happening before the patch came out he said
  • prrgg1prrgg1 Member Posts: 30 Arc User
    edited January 2013
    So it seems we have issues from UK, USA, France, and they all seem to be coming from Boston... Who drove their car into a power station?
  • origcaptainquackorigcaptainquack Member Posts: 614 Arc User
    edited January 2013
    not true. it is not pwe fault. cryptic still has its own studios and does thier own work and pwe makes money off it. cryptic still uses cryptic engines and servers, they just need to fix the problem, and i think i know what the problem is.
  • qwertypwnedqwertypwned Member Posts: 0 Arc User
    edited January 2013
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 8 ms 10 ms 26 ms 10.114.128.1
    2 9 ms 13 ms 9 ms gi5-1-14-cmts.uninny01-rtr001.cny.northeast.rr.c
    om [24.94.35.60]
    3 9 ms 9 ms 9 ms ae13.ithcnycy-rtr001.cny.northeast.rr.com [74.74
    .108.110]
    4 31 ms 31 ms 31 ms rdc-74-74-108-116.cny.northeast.rr.com [74.74.10
    8.116]
    5 14 ms 15 ms 16 ms ae0-0.vstlny11-rtr000.nyroc.rr.com [24.24.21.210
    ]
    6 28 ms 31 ms 31 ms bundle-ether1.albynyyf-rtr000.nyroc.rr.com [24.2
    4.21.208]
    7 26 ms 31 ms 31 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
    8 25 ms 25 ms 23 ms ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
    9 27 ms 26 ms 25 ms te0-1-0-5.ccr21.jfk05.atlas.cogentco.com [154.54
    .13.81]
    10 26 ms 43 ms 27 ms te0-3-0-5.mpd21.jfk02.atlas.cogentco.com [154.54
    .26.61]
    11 32 ms 31 ms 31 ms te0-1-0-4.ccr21.bos01.atlas.cogentco.com [154.54
    .6.1]
    12 45 ms 32 ms 35 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
    ]
    13 47 ms 46 ms * 38.111.40.114
  • thesimdude1987thesimdude1987 Member Posts: 2 Arc User
    edited January 2013
    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\Nick>tracert patchserver.crypticstudios.com

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

    1 16 ms 16 ms 10 ms cpc13-mapp10-2-0-gw.12-4.cable.virginmedia.com [
    82.27.248.1]
    2 8 ms 7 ms 7 ms nott-core-2a-ae7-2364.network.virginmedia.net [8
    0.7.83.17]
    3 9 ms 10 ms 11 ms leed-bb-1c-ae4-0.network.virginmedia.net [62.253
    .174.61]
    4 13 ms 10 ms 11 ms nrth-bb-1c-ae9-0.network.virginmedia.net [62.253
    .174.122]
    5 12 ms 11 ms 11 ms nrth-bb-1a-ae3-0.network.virginmedia.net [62.253
    .174.105]
    6 11 ms 14 ms 10 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.10
    5.159.30]
    7 35 ms 27 ms 26 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.
    185.81]
    8 30 ms 29 ms 27 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.11
    7.14.133]
    9 30 ms 26 ms 26 ms te0-2-0-2.mpd22.ams03.atlas.cogentco.com [130.11
    7.3.85]
    10 43 ms 36 ms 36 ms te0-0-0-7.ccr22.lpl01.atlas.cogentco.com [154.54
    .37.106]
    11 107 ms 107 ms 99 ms te0-1-0-3.ccr22.bos01.atlas.cogentco.com [154.54
    .42.105]
    12 96 ms 99 ms 107 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
    130]
    13 * * 131 ms 38.111.40.114
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20


    Seriously guys im not a happy bunny!
  • zeewolf007zeewolf007 Member Posts: 1 Arc User
    edited January 2013
    Hello space jumpers, here my test result. I hope you can use it and solve the problem

    1 1 ms 3 ms 3 ms 192.168.1.1
    2 7 ms 8 ms 19 ms 10.15.85.1
    3 9 ms 16 ms 11 ms p55109.net.upc.nl [212.142.55.109]
    4 53 ms 11 ms 17 ms 84.116.244.17
    5 21 ms 15 ms 16 ms nl-ams04a-ri2-xe-2-3-0.aorta.net [84.116.134.89]

    6 15 ms 17 ms 14 ms 213.46.182.18
    7 112 ms 109 ms 111 ms xe-3-0-0.bos11.ip4.tinet.net [141.136.109.138]
    8 181 ms 108 ms 114 ms internap-gw.ip4.tinet.net [77.67.77.54]
    9 109 ms 115 ms 110 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
    1]
    10 121 ms 125 ms 122 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
    61.78]
    11 * * * Time-out bij opdracht.
    12 * * * Time-out bij opdracht.
    13 * * * Time-out bij opdracht.
    14 * * * Time-out bij opdracht.
    15 * * * Time-out bij opdracht.
    16 * * * Time-out bij opdracht.
    17 * * * Time-out bij opdracht.
    18 * * * Time-out bij opdracht.
    19 * *

    unable to allocate performance buffer
    contacting nettest server..
    Local IP: 77.249.73.24
    Ping: 107.4 msec
    Port: 80: 405 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 80: 568 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 443: 576 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 443: 575 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7255: 576 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7255: 562 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7003: 553 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7003: 598 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7202: 595 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7202: 576 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7499: 534 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 7499: 536 KB/sec 0 KB/sec 0 KB/sec 500
    Port: 80: 579 KB/sec 0 KB/sec 0 KB/sec 500
    Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
    hit return to exit
  • jplatimerjplatimer Member Posts: 54 Arc User
    edited January 2013
    Well, I got to work which uses a DSL connection, as opposed to my home connection which is Cable. And, lo and behold, it patched and loaded fine here.

    Trace for **working** connection:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\User>tracert patchserver.crypticstudios.com

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

    3 * 61 ms 62 ms 38.104.210.154
    4 247 ms 230 ms 233 ms gi2-1.mag02.lax04.atlas.cogentco.com [38.104.211
    .157]
    5 178 ms 183 ms 185 ms te0-7-0-12.ccr22.lax04.atlas.cogentco.com [154.5
    4.87.6]
    6 81 ms 96 ms 114 ms te0-2-0-7.ccr22.lax01.atlas.cogentco.com [154.54
    .6.241]
    7 221 ms 165 ms 116 ms te0-3-0-6.ccr22.iah01.atlas.cogentco.com [154.54
    .3.185]
    8 139 ms 141 ms 142 ms te0-1-0-3.mpd22.atl01.atlas.cogentco.com [154.54
    .5.54]
    9 176 ms 180 ms 182 ms te0-0-0-7.ccr22.dca01.atlas.cogentco.com [154.54
    .28.221]
    10 206 ms 210 ms 211 ms te0-0-0-8.ccr22.jfk02.atlas.cogentco.com [154.54
    .42.26]
    11 244 ms 250 ms 252 ms te0-0-0-6.ccr22.bos01.atlas.cogentco.com [154.54
    .6.9]
    12 174 ms 179 ms 177 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
    130]
    13 204 ms 208 ms 216 ms 38.111.40.114
    14 154 ms 154 ms 154 ms 208.95.185.41

    Trace complete.

    So THIS DSL route works. I'll check back on Cable when I get back home.
Sign In or Register to comment.