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

Connection Issues

raddamusraddamus Member Posts: 19 Arc User
edited October 2014 in Windows and General: PC, Network, and Other Technical Issues
I am returning to STO after a break of several months and have been having a lot of trouble with Server Not Responding messages. Almost every map transfer results in a SNR followed by a DC. I can usually log straight back in and my toon is on the map i was trying to reach.
Connection within a zone/map/instance is good - no rubberbanding and no noticable lag.

I have changed my ISP since last i played, but STO is the only game or site that I have trouble connecting to. I even installed STO on my sons PC (much better than mine) but got the same results. Also i ran the same tests with the same results.





C:\Windows\system32>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.0.1
2 79 ms 57 ms 89 ms v1.cpcak3-bng1.tranzpeer.net [101.98.0.90]
3 30 ms 30 ms 30 ms ae-5-10.cpcak3-r1.tranzpeer.net [101.98.3.47]
4 31 ms 31 ms 30 ms ae-4-10.cpcak3-r1.tranzpeer.net [101.98.3.46]
5 30 ms 29 ms 32 ms ad-cpcak3-r1.tranzpeer.net [101.98.3.163]
6 32 ms 30 ms 30 ms xe-4-0-3-10.cpcak4-r1.tranzpeer.net [101.98.3.97
]
7 30 ms 35 ms 33 ms xe-4-0-2-10.cpcak4-r1.tranzpeer.net [101.98.3.96
]
8 31 ms 31 ms 31 ms ten-0-2-0.bdr01.akl05.akl.VOCUS.net.nz [175.45.1
02.17]
9 155 ms 155 ms 154 ms ten-0-1-0-2.cor01.akl05.akl.VOCUS.net.nz [114.31
.202.122]
10 159 ms 155 ms 155 ms ten-0-1-0-7.cor01.sjc01.ca.VOCUS.net [114.31.199
.83]
11 * * * Request timed out.
12 155 ms 155 ms 155 ms te7-5.ccr01.sjc05.atlas.cogentco.com [38.122.92.
1]
13 165 ms 163 ms 156 ms te0-4-0-5.ccr22.sjc01.atlas.cogentco.com [154.54
.6.205]
14 157 ms 156 ms 160 ms be2165.ccr22.sfo01.atlas.cogentco.com [154.54.28
.65]
15 199 ms 196 ms 200 ms be2133.ccr22.mci01.atlas.cogentco.com [154.54.30
.66]
16 213 ms 207 ms 205 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
17 229 ms 229 ms 229 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
18 230 ms 231 ms 229 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
19 232 ms 229 ms 229 ms 38.111.40.114
20 229 ms 230 ms 228 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.


C:\Windows\system32>


contacting nettest server..
timed out
hit return to exit



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

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

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 Mike-PC [192.168.0.5]
1 192.168.0.1
2 v1.cpcak3-bng1.tranzpeer.net [101.98.0.90]
3 ae-5-10.cpcak3-r1.tranzpeer.net [101.98.3.47]
4 ae-4-10.cpcak3-r1.tranzpeer.net [101.98.3.46]
5 ad-cpcak3-r1.tranzpeer.net [101.98.3.163]
6 xe-4-0-3-10.cpcak4-r1.tranzpeer.net [101.98.3.97]
7 xe-4-0-2-10.cpcak4-r1.tranzpeer.net [101.98.3.96]
8 ten-0-2-0.bdr01.akl05.akl.VOCUS.net.nz [175.45.102.17]
9 ten-0-1-0-2.cor01.akl05.akl.VOCUS.net.nz [114.31.202.122]
10 ten-0-1-0-7.cor01.sjc01.ca.VOCUS.net [114.31.199.83]
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mike-PC [192.168.0.5]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 32ms 0/ 100 = 0% 0/ 100 = 0% v1.cpcak3-bng1.tranzpeer.net [101.
98.0.90]
0/ 100 = 0% |
3 32ms 0/ 100 = 0% 0/ 100 = 0% ae-5-10.cpcak3-r1.tranzpeer.net [1
01.98.3.47]
0/ 100 = 0% |
4 32ms 0/ 100 = 0% 0/ 100 = 0% ae-4-10.cpcak3-r1.tranzpeer.net [1
01.98.3.46]
0/ 100 = 0% |
5 33ms 0/ 100 = 0% 0/ 100 = 0% ad-cpcak3-r1.tranzpeer.net [101.98
.3.163]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% xe-4-0-3-10.cpcak4-r1.tranzpeer.ne
t [101.98.3.97]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% xe-4-0-2-10.cpcak4-r1.tranzpeer.ne
t [101.98.3.96]
0/ 100 = 0% |
8 33ms 0/ 100 = 0% 0/ 100 = 0% ten-0-2-0.bdr01.akl05.akl.VOCUS.ne
t.nz [175.45.102.17]
0/ 100 = 0% |
9 34ms 0/ 100 = 0% 0/ 100 = 0% ten-0-1-0-2.cor01.akl05.akl.VOCUS.
net.nz [114.31.202.122]
0/ 100 = 0% |
10 159ms 0/ 100 = 0% 0/ 100 = 0% ten-0-1-0-7.cor01.sjc01.ca.VOCUS.n
et [114.31.199.83]

Trace complete.

C:\Windows\system32>

ISP is Slingshot, location is New Zealand.
Any help here would be much appreciated!
Post edited by raddamus on

Comments

  • raddamusraddamus Member Posts: 19 Arc User
    edited October 2014
    Ok its into week 4 now, same issues.
    I spoke to my ISP and got all the usual scripted replies - as far as they are concerned everything is working fine. I asked about the lost packets at hop 6 and 7 and they said it wasnt a problem as long as the signal continued on to its final destination. I have no freakin idea.
    I have put in a support ticket as well, and although they have been replying quite quickly their suggested fixes havent made any difference.

    These are the tracert and pathping results from today while wired into the modem to bypass the router:


    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 <1 ms <1 ms <1 ms 192.168.0.1
    2 62 ms 29 ms 87 ms v1.cpcak3-bng1.tranzpeer.net [101.98.0.90]
    3 30 ms 29 ms 29 ms ae-5-10.cpcak3-r1.tranzpeer.net [101.98.3.47]
    4 29 ms 31 ms 30 ms ae-4-10.cpcak3-r1.tranzpeer.net [101.98.3.46]
    5 29 ms 29 ms 30 ms ad-cpcak3-r1.tranzpeer.net [101.98.3.163]
    6 29 ms 29 ms 55 ms xe-4-0-3-10.cpcak4-r1.tranzpeer.net [101.98.3.97
    ]
    7 * 30 ms 31 ms xe-4-0-2-10.cpcak4-r1.tranzpeer.net [101.98.3.96
    ]
    8 34 ms 31 ms 30 ms ten-0-2-0.bdr01.akl05.akl.VOCUS.net.nz [175.45.1
    02.17]
    9 153 ms 154 ms 154 ms ten-0-7-0-5.cor01.akl05.akl.VOCUS.net.nz [114.31
    .202.40]
    10 154 ms 156 ms 153 ms ten-0-3-0-1.cor01.sjc01.ca.VOCUS.net [114.31.199
    .31]
    11 * * * Request timed out.
    12 204 ms 212 ms 209 ms 38.122.93.1
    13 154 ms 155 ms 155 ms te0-2-0-4.ccr21.sjc01.atlas.cogentco.com [154.54
    .84.53]
    14 156 ms 156 ms 156 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28
    .33]
    15 193 ms 194 ms 194 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
    .54]
    16 206 ms 206 ms 205 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
    86]
    17 229 ms 229 ms 228 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
    .194]
    18 228 ms 229 ms 228 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
    ]
    19 228 ms 234 ms 232 ms 38.111.40.114
    20 228 ms 258 ms 259 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.

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

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Mike-PC [192.168.0.4]
    1 192.168.0.1
    2 v1.cpcak3-bng1.tranzpeer.net [101.98.0.90]
    3 ae-5-10.cpcak3-r1.tranzpeer.net [101.98.3.47]
    4 ae-4-10.cpcak3-r1.tranzpeer.net [101.98.3.46]
    5 ad-cpcak3-r1.tranzpeer.net [101.98.3.163]
    6 xe-4-0-3-10.cpcak4-r1.tranzpeer.net [101.98.3.97]
    7 xe-4-0-2-10.cpcak4-r1.tranzpeer.net [101.98.3.96]
    8 ten-0-2-0.bdr01.akl05.akl.VOCUS.net.nz [175.45.102.17]
    9 ten-0-7-0-5.cor01.akl05.akl.VOCUS.net.nz [114.31.202.40]
    10 ten-0-3-0-1.cor01.sjc01.ca.VOCUS.net [114.31.199.31]
    11 * * *
    Computing statistics for 250 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Mike-PC [192.168.0.4]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
    0/ 100 = 0% |
    2 29ms 0/ 100 = 0% 0/ 100 = 0% v1.cpcak3-bng1.tranzpeer.net [101.
    98.0.90]
    0/ 100 = 0% |
    3 29ms 0/ 100 = 0% 0/ 100 = 0% ae-5-10.cpcak3-r1.tranzpeer.net [1
    01.98.3.47]
    0/ 100 = 0% |
    4 29ms 0/ 100 = 0% 0/ 100 = 0% ae-4-10.cpcak3-r1.tranzpeer.net [1
    01.98.3.46]
    0/ 100 = 0% |
    5 30ms 0/ 100 = 0% 0/ 100 = 0% ad-cpcak3-r1.tranzpeer.net [101.98
    .3.163]
    0/ 100 = 0% |
    6 --- 100/ 100 =100% 100/ 100 =100% xe-4-0-3-10.cpcak4-r1.tranzpeer.ne
    t [101.98.3.97]
    0/ 100 = 0% |
    7 --- 100/ 100 =100% 100/ 100 =100% xe-4-0-2-10.cpcak4-r1.tranzpeer.ne
    t [101.98.3.96]
    0/ 100 = 0% |
    8 30ms 0/ 100 = 0% 0/ 100 = 0% ten-0-2-0.bdr01.akl05.akl.VOCUS.ne
    t.nz [175.45.102.17]
    0/ 100 = 0% |
    9 30ms 0/ 100 = 0% 0/ 100 = 0% ten-0-7-0-5.cor01.akl05.akl.VOCUS.
    net.nz [114.31.202.40]
    0/ 100 = 0% |
    10 154ms 0/ 100 = 0% 0/ 100 = 0% ten-0-3-0-1.cor01.sjc01.ca.VOCUS.n
    et [114.31.199.31]

    Trace complete.

    C:\Windows\system32>
  • krog11krog11 Member Posts: 11 Arc User
    edited October 2014
    doesn't take a genius to see its at atlas.cogentco.....
  • dpaul02dpaul02 Member Posts: 9 Arc User
    edited October 2014
    Yes !
    every tome i have had issues and ran a tracert test it ALWAYS shows that altas contenco is the problem ! EVERYTIME
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited October 2014
    raddamus wrote: »
    ...
    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.0.1
    2 62 ms 29 ms 87 ms v1.cpcak3-bng1.tranzpeer.net [101.98.0.90]
    3 30 ms 29 ms 29 ms ae-5-10.cpcak3-r1.tranzpeer.net [101.98.3.47]
    4 29 ms 31 ms 30 ms ae-4-10.cpcak3-r1.tranzpeer.net [101.98.3.46]
    5 29 ms 29 ms 30 ms ad-cpcak3-r1.tranzpeer.net [101.98.3.163]
    6 29 ms 29 ms 55 ms xe-4-0-3-10.cpcak4-r1.tranzpeer.net [101.98.3.97
    ]
    7 * 30 ms 31 ms xe-4-0-2-10.cpcak4-r1.tranzpeer.net [101.98.3.96
    ]
    8 34 ms 31 ms 30 ms ten-0-2-0.bdr01.akl05.akl.VOCUS.net.nz [175.45.1
    02.17]
    9 153 ms 154 ms 154 ms ten-0-7-0-5.cor01.akl05.akl.VOCUS.net.nz [114.31
    .202.40]
    10 154 ms 156 ms 153 ms ten-0-3-0-1.cor01.sjc01.ca.VOCUS.net [114.31.199
    .31]
    11 * * * Request timed out.
    12 204 ms 212 ms 209 ms 38.122.93.1
    13 154 ms 155 ms 155 ms te0-2-0-4.ccr21.sjc01.atlas.cogentco.com [154.54
    .84.53]
    14 156 ms 156 ms 156 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28
    .33]
    15 193 ms 194 ms 194 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
    .54]
    16 206 ms 206 ms 205 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
    86]
    17 229 ms 229 ms 228 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
    .194]
    18 228 ms 229 ms 228 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
    ]
    19 228 ms 234 ms 232 ms 38.111.40.114
    20 228 ms 258 ms 259 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.
    ....

    Just from the 'Trace Route' it looks like their isn't much that you or your ISP can actually do to fix this issue... Problems appear to start with the Trans-Pacific cable link from New Zealand to San Fransico, and within the industry its well known that the majority of the Pacific cable links are over-subscribed for their capacity... (and 180 ms is the recommended upper limit for connection latency for reliable game play...) So this is a basic Internet infrastructure capacity issue...

    You can always hope that Google hurries up with their half a billion dollar Trans-Pacific cable project that they've been talking about...
  • rakija879rakija879 Member Posts: 646 Arc User
    edited October 2014
    I have the same change zone dc problem for some looooong time! Try the US proxy maybe you won't dc so often.:)
  • raddamusraddamus Member Posts: 19 Arc User
    edited October 2014
    grouchyotaku wrote: »
    Just from the 'Trace Route' it looks like their isn't much that you or your ISP can actually do to fix this issue... Problems appear to start with the Trans-Pacific cable link from New Zealand to San Fransico, and within the industry its well known that the majority of the Pacific cable links are over-subscribed for their capacity... (and 180 ms is the recommended upper limit for connection latency for reliable game play...) So this is a basic Internet infrastructure capacity issue...

    You can always hope that Google hurries up with their half a billion dollar Trans-Pacific cable project that they've been talking about...


    Thanks grouchy, at least I kinda know whats happening now. I got pretty much the same info from PWE support a few moments ago.
    Ahh well, looks like its time to fade back into retirement; logging back in every map change is just too annoying. Just when the KDF is finally getting a decent raptor too :mad:
Sign In or Register to comment.