Closed Thread
Page 15 of 32 FirstFirst ... 5 11 12 13 14 15 16 17 18 19 25 ... LastLast
Results 211 to 225 of 476
Like Tree60Likes

  Click here to go to the first Rift Team post in this thread.   Thread: Lagggggggg!!!!!!!!!!

  1. #211
    Shadowlander
    Join Date
    Aug 2013
    Posts
    38

    Default

    Had some minor issues Wednesday, but nothing serious until today. Apparently some server in Seattle (according to WHOIS) is dead and making it so I can't even finish the trace to Trion.

    Region: US/Great Lakes/WI
    ISP: ATT U-Verse

    traceroute 208.94.26.5 with 64 packetsize

    1: 99-73-140-3.lightspeed.milwwi.sbcglobal.net (99.73.140.3) 33 ms
    2: * *
    3: 12.83.79.141 27 ms
    4: * ggr6.dlstx.ip.att.net (12.122.138.113) 55 ms
    5: 12.90.228.14 62 ms
    6: border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 56 ms
    7: * *
    8: * *
    9: * *
    10: * *
    11: * *
    12: * *
    13: * *
    14: * *
    15: * *
    16: * *
    17: * *
    18: * *
    19: * *
    20: * *
    21: * *
    22: * *
    23: * *
    24: * *
    25: * *
    26: * *
    27: * *
    28: * *
    29: * *
    max ttl 30 exceeded

  2. #212
    Champion
    Join Date
    Jun 2011
    Posts
    587

    Default

    Your Service Providers Name: Comcast
    Your IP Address (Use whatismyip.com): 76.20.11.92
    A copy of a traceroute to 208.94.26.5

    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 8 ms 7 ms 7 ms 96.120.14.181
    3 7 ms 7 ms 7 ms xe-11-1-2-32767-sur02.sacramento.ca.ccal.comcast.net [69.139.197.241]
    4 13 ms 13 ms 13 ms xe-1-0-0-0-ar04.fresno.ca.fresno.comcast.net [68.87.202.241]
    5 21 ms 22 ms 22 ms pos-1-2-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.95.37]
    6 51 ms 51 ms 51 ms he-0-11-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.87.38]
    7 50 ms 51 ms 51 ms be-11-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.134]
    8 51 ms 51 ms 51 ms 66.208.216.210
    9 51 ms 51 ms * dal-r09-fcp.dal.triongames.com [208.94.26.5]
    10 51 ms 52 ms 50 ms dal-r09-fcp.dal.triongames.com [208.94.26.5]

    Trace complete.
    Last edited by EchoesIE; 08-29-2013 at 12:10 PM.
    [CENTER]
    Cleric Tank - Trinity - 100k HP Club
    3/3 IG | 4/5 PB

  3. #213
    Shadowlander Frumious's Avatar
    Join Date
    Jun 2011
    Posts
    28

    Default

    Quote Originally Posted by Techie Will View Post
    To clarify your post in a TL;DR format:

    The science behind that forum post is nonsense, the workaround is valid.

    Using a virtual private network connection will allow players to bypass this route but this is like putting a band aid on the situation (it will last but it is a hassle until Comcast corrects their issue).
    I think even that is giving it too much credit. Getting a new IP address is very unlikely to change anything and even a VPN is no guarantee, since the VPN endpoint could very well have the same routing issues.

    In fact, looking at a trace from another starting point, I believe the problem is actually directly at Trion's datacenter now, and not a routing issue. From another network, I get a clear path straight through to the endpoint, which it abruptly gets packet loss. This suggests it's the last hop that's very broken, most likely whatever device they have on 208.94.26.5 (presumably, a firewall), assuming 66.208.216.210 is their datacenter's router. You can also see that it's not an overloaded line, as the ping times are consistent. Usually, you'll see widely varying ping times when a line is overloaded. On this one, the packets that are getting through, are getting through clean.

    This situation started either today or last night, and is not related to the issues people were having in previous days.

    Code:
                                                      Packets               Pings
     Host                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. n1.localdomain                               0.0%    93    0.2   0.2   0.1   0.8   0.1
     2. 209.123.145.3                                0.0%    93    1.0   4.9   0.4 279.9  30.3
     3. vlan803.tbr1.mmu.nac.net                     0.0%    93    1.1   1.8   0.4  11.5   2.7
     4. 0.e1-2.tbr1.ewr.nac.net                      0.0%    93    1.2   2.3   0.9  12.8   2.7
     5. be-20-404-cr01.newyork.ny.ibone.comcast.net  0.0%    93    3.5   5.1   2.7   8.2   1.2
     6. he-4-10-0-0-cr01.ashburn.va.ibone.comcast.n  0.0%    93   11.1   9.3   7.1  11.3   1.2
     7. he-4-10-0-0-cr01.56marietta.ga.ibone.comcas  0.0%    93   24.3  23.0  21.1  27.2   1.1
     8. pos-1-7-0-0-cr01.dallas.tx.ibone.comcast.ne  0.0%    93   41.1  42.9  40.6  45.4   1.3
     9. be-16-pe02.1950stemmons.tx.ibone.comcast.ne  0.0%    92   41.2  41.3  40.8  45.7   0.6
    10. 66.208.216.210                               0.0%    92   43.7  48.3  40.6 328.7  39.6
    11. 140.26.94.208.dal.triongames.com            32.6%    92   40.7  40.8  40.4  48.5   1.1

  4. #214
    Prophet of Telara
    Join Date
    Jun 2013
    Posts
    1,011

    Default

    Quote Originally Posted by Frumious View Post
    I think even that is giving it too much credit. Getting a new IP address is very unlikely to change anything and even a VPN is no guarantee, since the VPN endpoint could very well have the same routing issues.

    In fact, looking at a trace from another starting point, I believe the problem is actually directly at Trion's datacenter now, and not a routing issue. From another network, I get a clear path straight through to the endpoint, which it abruptly gets packet loss. This suggests it's the last hop that's very broken, most likely whatever device they have on 208.94.26.5 (presumably, a firewall), assuming 66.208.216.210 is their datacenter's router. You can also see that it's not an overloaded line, as the ping times are consistent. Usually, you'll see widely varying ping times when a line is overloaded. On this one, the packets that are getting through, are getting through clean.

    This situation started either today or last night, and is not related to the issues people were having in previous days.

    Code:
                                                      Packets               Pings
     Host                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. n1.localdomain                               0.0%    93    0.2   0.2   0.1   0.8   0.1
     2. 209.123.145.3                                0.0%    93    1.0   4.9   0.4 279.9  30.3
     3. vlan803.tbr1.mmu.nac.net                     0.0%    93    1.1   1.8   0.4  11.5   2.7
     4. 0.e1-2.tbr1.ewr.nac.net                      0.0%    93    1.2   2.3   0.9  12.8   2.7
     5. be-20-404-cr01.newyork.ny.ibone.comcast.net  0.0%    93    3.5   5.1   2.7   8.2   1.2
     6. he-4-10-0-0-cr01.ashburn.va.ibone.comcast.n  0.0%    93   11.1   9.3   7.1  11.3   1.2
     7. he-4-10-0-0-cr01.56marietta.ga.ibone.comcas  0.0%    93   24.3  23.0  21.1  27.2   1.1
     8. pos-1-7-0-0-cr01.dallas.tx.ibone.comcast.ne  0.0%    93   41.1  42.9  40.6  45.4   1.3
     9. be-16-pe02.1950stemmons.tx.ibone.comcast.ne  0.0%    92   41.2  41.3  40.8  45.7   0.6
    10. 66.208.216.210                               0.0%    92   43.7  48.3  40.6 328.7  39.6
    11. 140.26.94.208.dal.triongames.com            32.6%    92   40.7  40.8  40.4  48.5   1.1
    If it were the last hop, it would be affecting everybody, not just certain people.

  5. #215
    Soulwalker
    Join Date
    Aug 2013
    Posts
    1

    Default Latency Supreme

    Been having latency issues for about three days. Get lag spikes upwards of 23000 latency. If I'm solo, only lasts a few seconds, then goes down to normal 60-90 range. If I'm in a group or raid, lasts minutes at a time, sometimes disconnects me entirely. Occurs every 30-60 seconds. Really does make the game unplayable.

    Internet provider: Comcast
    IP: 50.142.248.151
    Traceroute:
    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:

    1 7 ms 7 ms 11 ms 96.70.158.1
    2 8 ms 7 ms 7 ms te-9-2-ur02.sharpsridge.tn.knox.comcast.net [69.
    139.205.197]
    3 11 ms 8 ms 7 ms xe-0-0-3-0-ar02.bluelight.tn.knox.comcast.net [6
    8.85.171.205]
    4 15 ms 15 ms 15 ms xe-0-0-1-0-ar01.goodslettvll.tn.nash.comcast.net
    [68.85.171.190]
    5 36 ms 23 ms 23 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net
    [68.86.90.101]
    6 43 ms 43 ms 43 ms pos-1-3-0-0-cr01.dallas.tx.ibone.comcast.net [68
    .86.85.157]
    7 42 ms 41 ms 41 ms be-13-pe02.1950stemmons.tx.ibone.comcast.net [68
    .86.82.142]
    8 42 ms 41 ms 45 ms 66.208.216.210
    9 41 ms * 42 ms dal-r09-fcp.dal.triongames.com [208.94.26.5]

    Trace complete.

  6. #216
    Soulwalker
    Join Date
    Mar 2011
    Posts
    2

    Default

    Provider: Time Warner
    IP: 67.252.44.240



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

    C:\Users\user>tracert 208.94.26.5

    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms [192.168.1.1]
    2 43 ms 26 ms 29 ms cable-mac1.nadmma01-ar4002.nyroc.rr.com [67.252.
    32.1]
    3 10 ms 11 ms 12 ms gig2-29.nadmma01-rtr001.alb.northeast.rr.com [24
    .29.44.65]
    4 14 ms 40 ms 16 ms rdc-74-76-241-142.alb.northeast.rr.com [74.76.24
    1.142]
    5 28 ms 27 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.24
    1.193]
    6 26 ms 23 ms 27 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
    7 37 ms 21 ms 21 ms 107.14.17.216
    8 24 ms 25 ms 24 ms 66.208.216.49
    9 26 ms 26 ms 23 ms be-14-cr01.newyork.ny.ibone.comcast.net [68.86.8
    2.241]
    10 43 ms 31 ms 31 ms he-4-13-0-0-cr01.ashburn.va.ibone.comcast.net [6
    8.86.85.97]
    11 72 ms 47 ms 47 ms he-4-6-0-0-cr01.56marietta.ga.ibone.comcast.net
    [68.86.89.162]
    12 62 ms 64 ms 63 ms pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net [6
    8.86.86.129]
    13 59 ms 59 ms 61 ms be-17-pe02.1950stemmons.tx.ibone.comcast.net [68
    .86.83.122]
    14 60 ms 60 ms 60 ms 66.208.216.210
    15 59 ms 60 ms * dal-r09-fcp.dal.triongames.com [208.94.26.5]
    16 71 ms 73 ms 60 ms dal-r09-fcp.dal.triongames.com [208.94.26.5]

    Trace complete.

  7. #217
    res
    res is offline
    Soulwalker
    Join Date
    Mar 2011
    Posts
    2

    Default

    Quote Originally Posted by Daglar View Post

    Your Service Providers Name:
    Your IP Address (Use whatismyip.com):
    A copy of a traceroute to 208.94.26.5
    ATT UVerse
    99.108.112.93

    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:

    1 3 ms 1 ms 1 ms homeportal [192.168.1.254]
    2 29 ms 24 ms 27 ms 99-108-112-3.lightspeed.stlsmo.sbcglobal.net [99.108.112.3]
    3 23 ms 24 ms * 71.144.225.48
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 23 ms 30 ms 26 ms 12.83.40.5
    7 43 ms 43 ms 42 ms ggr6.dlstx.ip.att.net [12.122.138.113]
    8 * * * Request timed out.
    9 44 ms 43 ms 43 ms border1.pc2-bbnet2.dal004.pnap.net [216.52.191.81]
    10 46 ms 44 ms 43 ms trionwn-4.border1.dal004.pnap.net [72.5.252.66]
    11 44 ms * 43 ms dal-r09-fcp.dal.triongames.com [208.94.26.5]

  8. #218
    Rift Disciple
    Join Date
    Apr 2011
    Posts
    171

    Default

    TineWarner Ultimate Internet Southern California




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

    C:\Users\>tracert www.riftgame.com

    Tracing route to RiftgameLB-273652324.us-east-1.elb.amazonaws.com [23.21.162.226
    ]
    over a maximum of 30 hops:

    1 48 ms 25 ms 29 ms cpe-98-151-192-1.socal.res.rr.com [98.151.192.1]

    2 14 ms 15 ms 20 ms tge7-1.sntlcasm01h.socal.rr.com [76.166.10.161]

    3 16 ms 53 ms 17 ms tge0-8-0-6.chwocadq01r.socal.rr.com [72.129.25.1
    28]
    4 32 ms 19 ms 19 ms agg24.lsancarc-ccr01.socal.rr.com [72.129.25.0]

    5 19 ms 19 ms 19 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10
    9.6.102]
    6 24 ms 18 ms 35 ms 66.109.9.24
    7 19 ms 22 ms 38 ms las-bb1-link.telia.net [213.248.86.189]
    8 83 ms 85 ms 83 ms ash-bb3-link.telia.net [213.155.137.89]
    9 84 ms 109 ms 86 ms ash-b1-link.telia.net [213.155.130.86]
    10 78 ms 79 ms 79 ms vadata-ic-157233-ash-bb1.c.telia.net [62.115.9.7
    0]
    11 104 ms 100 ms 93 ms 72.21.220.31
    12 103 ms 92 ms 91 ms 72.21.222.155
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 86 ms 88 ms 97 ms 216.182.224.85
    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.

  9. #219
    Ascendant Techie Will's Avatar
    Join Date
    Mar 2011
    Posts
    5,418

    Default

    Quote Originally Posted by Frumious View Post
    I think even that is giving it too much credit. Getting a new IP address is very unlikely to change anything and even a VPN is no guarantee, since the VPN endpoint could very well have the same routing issues.

    In fact, looking at a trace from another starting point, I believe the problem is actually directly at Trion's datacenter now, and not a routing issue. From another network, I get a clear path straight through to the endpoint, which it abruptly gets packet loss. This suggests it's the last hop that's very broken, most likely whatever device they have on 208.94.26.5 (presumably, a firewall), assuming 66.208.216.210 is their datacenter's router. You can also see that it's not an overloaded line, as the ping times are consistent. Usually, you'll see widely varying ping times when a line is overloaded. On this one, the packets that are getting through, are getting through clean.

    This situation started either today or last night, and is not related to the issues people were having in previous days.

    Code:
                                                      Packets               Pings
     Host                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. n1.localdomain                               0.0%    93    0.2   0.2   0.1   0.8   0.1
     2. 209.123.145.3                                0.0%    93    1.0   4.9   0.4 279.9  30.3
     3. vlan803.tbr1.mmu.nac.net                     0.0%    93    1.1   1.8   0.4  11.5   2.7
     4. 0.e1-2.tbr1.ewr.nac.net                      0.0%    93    1.2   2.3   0.9  12.8   2.7
     5. be-20-404-cr01.newyork.ny.ibone.comcast.net  0.0%    93    3.5   5.1   2.7   8.2   1.2
     6. he-4-10-0-0-cr01.ashburn.va.ibone.comcast.n  0.0%    93   11.1   9.3   7.1  11.3   1.2
     7. he-4-10-0-0-cr01.56marietta.ga.ibone.comcas  0.0%    93   24.3  23.0  21.1  27.2   1.1
     8. pos-1-7-0-0-cr01.dallas.tx.ibone.comcast.ne  0.0%    93   41.1  42.9  40.6  45.4   1.3
     9. be-16-pe02.1950stemmons.tx.ibone.comcast.ne  0.0%    92   41.2  41.3  40.8  45.7   0.6
    10. 66.208.216.210                               0.0%    92   43.7  48.3  40.6 328.7  39.6
    11. 140.26.94.208.dal.triongames.com            32.6%    92   40.7  40.8  40.4  48.5   1.1
    It was confirmed yesterday that the 66.208.216.210 device is a Comcast owned router. It could be on the premises of the data center, we do not know.

    Quote Originally Posted by szalkerous View Post
    I have spoken at length with Comcast's network team and I have helped identify that a specific IP address (which IS actually owned by Comcast Business Communications in Tuscon, AZ) is the problem point.

    IP address 66.208.216.210 is a Comcast owned router that is dropping the packets. This has been dispatched to the team responsible for review.

    If you run a tracert command to the Rift servers and 66.208.216.210 is in the list (usually second to last) you are probably experiencing this problem.

    Problem is, without Trion getting on Comcast's ***, this won't be considered a high severity ticket. We need Trion to get on this ASAP with Comcast.
    A quick who.is of the IP shows that it is indeed part of their network.

    Code:
    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #
     
    
    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=66.208.216.210?showDetails=true&showARIN=false&ext=netref2
    #
     
    Comcast Business Communications, LLC COMCAST-43 (NET-66-208-216-0-1) 66.208.216.0 - 66.208.216.255
    Comcast Business Communications, LLC CBC-CM (NET-66-208-192-0-1) 66.208.192.0 - 66.208.255.255
     
    
     
    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #
    EDIT: And yes, it very well could be an issue that Comcast spawned after making changes to that device I'm talking about. We could see the symptoms changing as they work through the issues with that device.
    Last edited by Techie Will; 08-29-2013 at 12:17 PM.

  10. #220
    Shadowlander
    Join Date
    Jun 2011
    Posts
    35

    Default

    C:\Users\Chris>tracert auth2.login.trionworlds
    Unable to resolve target system name auth2.login.trionworlds.

    C:\Users\Chris>tracert 208.94.26.5

    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 27 ms 14 ms 29 ms c-69-250-184-1.hsd1.md.comcast.net [69.250.184.1]
    3 10 ms 10 ms 9 ms xe-4-0-0-32767-sur01.newtowson.md.bad.comcast.net [68.85.80.45]
    4 17 ms 14 ms 10 ms xe-4-1-1-0-ar04.whitemarsh.md.bad.comcast.net [68.85.115.33]
    5 20 ms 16 ms 18 ms pos-0-8-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.88.253]
    6 18 ms 19 ms 19 ms he-4-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.85.93]
    7 42 ms 35 ms 31 ms he-4-9-0-0-cr01.56marietta.ga.ibone.comcast.net[68.86.89.174]
    8 53 ms 51 ms 51 ms pos-1-4-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.88.226]
    9 51 ms 50 ms 50 ms be-10-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.130]
    10 51 ms 50 ms 49 ms 66.208.216.210
    11 50 ms 49 ms 80 ms dal-r09-fcp.dal.triongames.com [208.94.26.5]

    Trace complete.

    C:\Users\Chris>tracert auth2.triongames.com

    Tracing route to auth2.triongames.com [208.94.26.140]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 34 ms 45 ms 42 ms c-69-250-184-1.hsd1.md.comcast.net [69.250.184.1]
    3 10 ms 10 ms 10 ms xe-4-0-0-32767-sur01.newtowson.md.bad.comcast.net [68.85.80.45]
    4 10 ms 11 ms 10 ms xe-4-1-1-0-ar04.whitemarsh.md.bad.comcast.net [68.85.115.33]
    5 29 ms 17 ms 15 ms be-20-415-cr01.losangeles.ca.ibone.comcast.net [68.86.88.121]
    6 20 ms 19 ms 17 ms he-4-9-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.87.61]
    7 30 ms 31 ms 31 ms he-4-3-0-0-cr01.56marietta.ga.ibone.comcast.net[68.86.89.150]
    8 50 ms 53 ms 50 ms pos-1-11-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.88.230]
    9 52 ms 50 ms 66 ms be-13-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.142]
    10 51 ms 49 ms 50 ms 66.208.216.210
    11 50 ms * 50 ms 140.26.94.208.dal.triongames.com [208.94.26.140]


    Trace complete.

    So here's my experience with the whole process. I'd like to just go ahead and volunteer that we blame texas for this.
    /r/rift

  11. #221
    Soulwalker
    Join Date
    Aug 2013
    Posts
    9

    Default

    At risk of being very stupid and/or getting flamed, what's the real likelihood of this getting solved soon, or ever? And will the 'fix' work for those outside the USA (if I can be bothered to screw around with my PC/network for this?)

    I ask because I've only just started playing (I've bought the box and subbed a month now too *mutters grumbles*) but if this is going to be an ongoing issue I'm going to have a problem. I play on US servers because that's where my gamer friends are and whilst I'm really enjoying the game, I'm not going to play on EU servers instead.

    Incidentally, a more detailed response from Trion would be really welcome.

  12. #222
    Ascendant Techie Will's Avatar
    Join Date
    Mar 2011
    Posts
    5,418

    Default

    Quote Originally Posted by Presi View Post
    C:\Users\Chris>tracert auth2.login.trionworlds
    Unable to resolve target system name auth2.login.trionworlds.

    C:\Users\Chris>tracert 208.94.26.5

    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 27 ms 14 ms 29 ms c-69-250-184-1.hsd1.md.comcast.net [69.250.184.1]
    3 10 ms 10 ms 9 ms xe-4-0-0-32767-sur01.newtowson.md.bad.comcast.net [68.85.80.45]
    4 17 ms 14 ms 10 ms xe-4-1-1-0-ar04.whitemarsh.md.bad.comcast.net [68.85.115.33]
    5 20 ms 16 ms 18 ms pos-0-8-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.88.253]
    6 18 ms 19 ms 19 ms he-4-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.85.93]
    7 42 ms 35 ms 31 ms he-4-9-0-0-cr01.56marietta.ga.ibone.comcast.net[68.86.89.174]
    8 53 ms 51 ms 51 ms pos-1-4-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.88.226]
    9 51 ms 50 ms 50 ms be-10-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.130]
    10 51 ms 50 ms 49 ms 66.208.216.210
    11 50 ms 49 ms 80 ms dal-r09-fcp.dal.triongames.com [208.94.26.5]

    Trace complete.

    C:\Users\Chris>tracert auth2.triongames.com

    Tracing route to auth2.triongames.com [208.94.26.140]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.0.0.1
    2 34 ms 45 ms 42 ms c-69-250-184-1.hsd1.md.comcast.net [69.250.184.1]
    3 10 ms 10 ms 10 ms xe-4-0-0-32767-sur01.newtowson.md.bad.comcast.net [68.85.80.45]
    4 10 ms 11 ms 10 ms xe-4-1-1-0-ar04.whitemarsh.md.bad.comcast.net [68.85.115.33]
    5 29 ms 17 ms 15 ms be-20-415-cr01.losangeles.ca.ibone.comcast.net [68.86.88.121]
    6 20 ms 19 ms 17 ms he-4-9-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.87.61]
    7 30 ms 31 ms 31 ms he-4-3-0-0-cr01.56marietta.ga.ibone.comcast.net[68.86.89.150]
    8 50 ms 53 ms 50 ms pos-1-11-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.88.230]
    9 52 ms 50 ms 66 ms be-13-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.142]
    10 51 ms 49 ms 50 ms 66.208.216.210
    11 50 ms * 50 ms 140.26.94.208.dal.triongames.com [208.94.26.140]


    Trace complete.

    So here's my experience with the whole process. I'd like to just go ahead and volunteer that we blame texas for this.
    The basic rule of thumb here is, if you have 66.208.216.210 in your route, you're gonna' have a bad time.

  13. #223
    Ascendant Fragasm's Avatar
    Join Date
    Dec 2010
    Location
    Saint Paul, MN
    Posts
    3,157

    Default

    Quote Originally Posted by Tarante11a View Post
    At risk of being very stupid and/or getting flamed, what's the real likelihood of this getting solved soon, or ever? And will the 'fix' work for those outside the USA (if I can be bothered to screw around with my PC/network for this?)

    I ask because I've only just started playing (I've bought the box and subbed a month now too *mutters grumbles*) but if this is going to be an ongoing issue I'm going to have a problem. I play on US servers because that's where my gamer friends are and whilst I'm really enjoying the game, I'm not going to play on EU servers instead.

    Incidentally, a more detailed response from Trion would be really welcome.
    What these people are saying makes no sense unless its just a Comcast thing - on Verizon I've been completely fine.
    The only way that someone from Cluster 2 is actually as bad as you all say is if they started playing this game in 2.3 (Free to Play launch).

    Proud officer and Mage class lead of <Zombies>

  14. #224
    Ascendant Shattered's Avatar
    Join Date
    Feb 2011
    Posts
    3,389

    Default

    Service Provider: Comcast
    my IP Address: 98.234.242.58
    Code:
    tracert 208.94.26.5
    
    Tracing route to dal-r09-fcp.dal.triongames.com [208.94.26.5]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.2.1
      2    25 ms    20 ms    18 ms  98.234.242.1
      3     8 ms     9 ms     9 ms  te-7-1-ur01.sf19th.ca.sfba.comcast.net [68.87.19
    5.17]
      4    14 ms    11 ms    11 ms  te-1-14-0-2-ar01.sfsutro.ca.sfba.comcast.net [68
    .85.154.206]
      5    12 ms    11 ms    11 ms  he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68
    .86.91.229]
      6    20 ms    19 ms    20 ms  68.86.89.210
      7    51 ms    52 ms    51 ms  he-0-11-0-0-cr01.dallas.tx.ibone.comcast.net [68
    .86.87.38]
      8    48 ms    50 ms    49 ms  be-12-pe02.1950stemmons.tx.ibone.comcast.net [68
    .86.82.138]
      9    50 ms    50 ms    50 ms  66.208.216.210
     10    50 ms    50 ms    50 ms  dal-r09-fcp.dal.triongames.com [208.94.26.5]
    
    Trace complete.
    Everything's perfect about the past except how it led to the present. ― Homer Simpson
    <Shattered Chain> of Faeblight

  15. #225
    Shadowlander Frumious's Avatar
    Join Date
    Jun 2011
    Posts
    28

    Default

    Quote Originally Posted by Sindala View Post
    On a more serious note, I would say to anyone popping their IP address on here. make sure you don't have 'allow remote connect to my PC' enabled. You could really regret it if what I just read on public posting of IP addresses is correct?

    Some more clever computer boffins could chime in on this and let us know if it's bad to do????
    Don't post your IP, but put in the second hop away. As far as the network routing is concerned, it's the same thing. In fact, just post the trace, really, since the trace will have your nearest router, but not your own IP address. If they can fix the routing to that router, then your connection will be fine.

    Another option is to post your class C, but not your actual ip address. For instance, if you IP address is 208.94.26.5, just point 208.94.26.0. Almost always will have the same routing.

    And, honestly, if you don't have a firewall, and are running a windows machine, your machine is likely already so riddled with malware that posting your IP here won't make a difference. If you do have a firewall, then that is what actually has your IP address, and any outside connections are made to it, not to your PC.

    Incidently, that's why he mentioned whatsmyip.org. If you just pull up the network control panel on your PC, you'll most likely have a 192.168.0.x ip address, which is a "local only" or non-routable IP address. It's effectively a "fake" address that your firewall translates when going out into the real internet.

Closed Thread
Page 15 of 32 FirstFirst ... 5 11 12 13 14 15 16 17 18 19 25 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts