test content
What is the Arc Client?
Install Arc

Launcher Message and Account server message

SystemSystem Member, NoReporting Posts: 178,019 Arc User
Wondering if someone can help me. I've submitted a tech support ticket, #913409. Here is my problem:

I was playing a day or so ago with no connection problems, but today when I go to launch the game, I get a Trying to update the launcher message. I've let it go up to about 15 or so, before stopping it. I've rebooted my machine, cleared my internet files, rebooted my router, but i'm still having this issue. when i bypass the launcher by running the gameclient.exe i get a connecting to account server message for a bit then it times out and says, Connection to the account server timed out. I haven't made any changes to either my router or my computer in several weeks.
in case anyone is interested my Traceroute to the patch server looks like:

Traceroute has started…

traceroute to patchserver.crypticstudios.com (208.95.184.25), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 4.716 ms 3.259 ms 3.259 ms
2 73.99.224.1 (73.99.224.1) 28.393 ms 12.242 ms 11.976 ms
3 ge-1-8-ur01.aberdeen.wa.seattle.comcast.net (68.85.241.201) 17.917 ms 13.155 ms 14.181 ms
4 ge-2-47-ur01.burien.wa.seattle.comcast.net (68.86.96.141) 21.376 ms 18.255 ms 18.191 ms
5 pos-1-5-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.213) 19.583 ms 19.714 ms 30.406 ms
6 pos-0-10-0-0-cr01.portland.or.ibone.comcast.net (68.86.85.106) 24.148 ms 23.114 ms 24.673 ms
7 pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.197) 35.499 ms 38.257 ms 34.761 ms
8 pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.181) 45.440 ms 37.715 ms 38.653 ms
9 te3-3.mpd01.sjc04.atlas.cogentco.com (154.54.11.105) 37.493 ms 38.808 ms 37.936 ms
10 te8-2.mpd01.sfo01.atlas.cogentco.com (154.54.2.165) 41.506 ms * 39.112 ms
11 te0-1-0-2.ccr22.mci01.atlas.cogentco.com (154.54.30.70) 84.430 ms
te0-3-0-3.mpd22.mci01.atlas.cogentco.com (154.54.7.225) 94.408 ms
te0-1-0-2.ccr22.mci01.atlas.cogentco.com (154.54.30.70) 85.223 ms
12 te0-2-0-3.ccr22.ord01.atlas.cogentco.com (154.54.6.202) 80.692 ms
te0-2-0-3.mpd22.ord01.atlas.cogentco.com (154.54.6.254) 79.582 ms
te0-1-0-2.ccr22.ord01.atlas.cogentco.com (154.54.5.174) 80.126 ms
13 te9-2.mpd01.bos01.atlas.cogentco.com (154.54.7.82) 123.437 ms
te7-3.ccr02.bos01.atlas.cogentco.com (154.54.24.57) 126.723 ms
te9-2.mpd01.bos01.atlas.cogentco.com (154.54.7.82) 123.500 ms
14 te4-2.ccr01.bos06.atlas.cogentco.com (66.28.4.254) 123.899 ms * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    well according to the tracert if that was the complete tracert show you have a routing problem you are not even making it to the server

    you also can not bypass the launcher by launching the gameclient.exe. the launcher passes information to the gameclient it needs to connect to the server.

    if you do get a good routing to the server and still cannot connect look to see if
    your firewall/antivirus have not reflagged the program as needing authorization to access the net.

    your IE browser did not get set to work offline or its internet option (communicationt tab lan settings) did not get set to use a proxy.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    That is pretty much the complete trace. I've run multiple trace's with differing number of maximum hops (all the way up to 100 hops, just in case), but after line 14, they are all time outs, never seeming to reach cryptic.

    I've also check my firewall/AV just in case and it's not being blocked there, and my IE is NOT set to work offline.

    I'm at a loss. I haven't see this problem since Open Beta and Launch.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    you can try clearing you dns cache
    at the run prompt enter ipconfig /flushdns it may give a change withthe new lookup for the server but more like you will need to either wait until the routing patch is fixed or contact your ISP show them the result of the trace (or have them do a check) and see if there is anything they can do about it.
    (they may or may not be able or will to)
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    He's got the right IP address there already, and this kind of traceroute failure is not conclusive. Nonetheless, it's hanging around in cogent's network far too long, which suggests a routing fault. Call your ISP.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    I don't remember the command string to do it but I just did a tracert and I made it all the way to the ip above on jump 14/

    the ms went in this order: 25ms 31ms 24ms

    Update:


    Just got in thru the launcher now.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    I'm hearing rumors that Comcast has done a firmware update and that the modem we have might not like the update. I don't go to a lot of websites, but others in the house have said that some don't load and other are to slow. I'll call comcast and see what they did this time.
Sign In or Register to comment.