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

Game Keeps disconnecting me from server issue

xcom43xcom43 Member Posts: 723 Arc User
edited April 2015 in Windows and General: PC, Network, and Other Technical Issues
I am trying to play the game on a Gateway NV57H notebook.

Intel core I5-2430m
Intel HD Graphics 3000
640GB HDD
6GB DDR3 RAM

This should be more then enough to play STO with out issue.

And it seems that the game it self is having Server respond issue constantly.Now I have not played STO for about 2 to 3 years.Since season 8 came out.I started playing in 2011 life time subber.

Back in the day i never really have had an issue.Can any one help me so that it stops giving me this issue.I have played SWTOR for 2 years with out an issue with high video settings.

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

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
2 14 ms 12 ms 9 ms dynamic-acs-24-101-158-1.zoominternet.net [24.10
1.158.1]
3 12 ms 11 ms 13 ms static-acs-24-129-240-197.zoominternet.net [24.1
29.240.197]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 21 ms 19 ms 93 ms COGENT-COMM.edge3.Washington4.Level3.net [4.68.6
3.174]
8 99 ms 24 ms 19 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.
170]
9 72 ms 26 ms 25 ms be2518.ccr41.jfk02.atlas.cogentco.com [154.54.80
.161]
10 33 ms 117 ms 38 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
11 31 ms 33 ms 31 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
12 33 ms 33 ms 34 ms 38.111.40.114
13 34 ms 35 ms 32 ms xboxpatchserver.crypticstudios.com [208.95.185.4
1]

Trace complete.
The fear of death follows from the fear of life. A man who lives fully is prepared to die at any time.
Post edited by xcom43 on

Comments

  • fraethirfraethir Member Posts: 2 Arc User
    edited April 2015
    Currently shows the classic signs of dramatic congestion (from too much traffic somewhere along the path), often caused by alt-routing during a circuit outage but sometimes simply because you don't have enough link at a critical point in the path.
    C:\Users\Paul>ping -t patchserver.crypticstudios.com

    Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
    Reply from 208.95.185.41: bytes=32 time=364ms TTL=249
    Reply from 208.95.185.41: bytes=32 time=697ms TTL=249
    Reply from 208.95.185.41: bytes=32 time=409ms TTL=249
    Reply from 208.95.185.41: bytes=32 time=661ms TTL=249
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=81ms TTL=249
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=536ms TTL=249
    Request timed out.
    Request timed out.
    Reply from 208.95.185.41: bytes=32 time=196ms TTL=249
    Reply from 208.95.185.41: bytes=32 time=820ms TTL=249
    Reply from 208.95.185.41: bytes=32 time=23ms TTL=249

    Ping statistics for 208.95.185.41:
    Packets: Sent = 13, Received = 9, Lost = 4 (30% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 820ms, Average = 420ms

    Latency ranges from 23ms to 820ms. There's no way i'm going from 23ms terrestrial to satcom connections, so the magnified latency is from buffering along the way. The 30% packetloss is probably from things dropped, or packets where the latency rose above the general 2000ms/2 second max.
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms router.asus.com [192.168.3.1]
    2 25 ms 19 ms 16 ms Wireless_Broadband_Router.home [192.168.1.1]
    3 45 ms 60 ms 8 ms L100.CLPPVA-VFTTP-11.verizon-gni.net [98.118.244.1]
    4 67 ms 40 ms 59 ms G0-1-0-4.CLPPVA-LCR-22.verizon-gni.net [130.81.223.62]
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 76 ms 47 ms 20 ms 0.ae2.GW15.BOS4.ALTER.NET [140.222.231.203]
    8 91 ms 74 ms 36 ms internap-gw.customer.alter.net [152.179.134.214]
    9 58 ms 55 ms 50 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    10 32 ms 87 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
    11 37 ms 183 ms 139 ms patchserverrebirth.crypticstudios.com [208.95.185.41]

    Trace complete.
    From that (run a few times to look at min/max), once it gets to bbnet1.bsn.pnap.net, it starts doing wild latency swings (one patchserver response was 521ms 24ms 190ms, one perfectworld was 104ms 26ms 102ms. Generally speaking it looks clean to Boston (BOS4 Alternet), and starts to flake out at the internap-gw.
Sign In or Register to comment.