I am a frequent STO player who never really experienced frequent lag problems, and only now am I experiencing any trouble
The timing of which coincides when the STO server recently glitched and went down. Ever since, my game causes frequent rubberbanding and server not responding dialogues. I don't pretend to know anything about networks and servers, so disregard this sentence if it is not important.
Here are the results of my tests:
1)Tracert - Looks good to me (according to the instructions on the sticky thread)
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 3 ms 1 ms . [192.168.2.1]
2 2 ms 4 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
3 12 ms 8 ms 9 ms L100.NYCMNY-VFTTP-209.verizon-gni.net [108.6.171
.1]
4 10 ms 17 ms 11 ms G0-3-3-7.NYCMNY-LCR-21.verizon-gni.net [130.81.1
77.82]
5 17 ms 17 ms 8 ms ae5-0.NY325-BB-RTR1.verizon-gni.net [130.81.163.
208]
6 61 ms 92 ms 27 ms 0.ge-1-1-0.XL3.BOS4.ALTER.NET [152.63.6.149]
7 28 ms 52 ms 19 ms 0.xe-8-0-0.GW15.BOS4.ALTER.NET [152.63.24.26]
8 59 ms 57 ms 58 ms internap-gw.customer.alter.net [152.179.134.214]
9 61 ms * 64 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
10 65 ms 70 ms 71 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 * * 48 ms patchserver.crypticstudios.com [208.95.185.41]
Trace complete.
'
2) Nettest - These numbers look bad...
contacting nettest server..
Local IP: 108.6.171.127
Ping: 136.4 msec
Port: 80: 57 KB/sec 18 KB/sec 64 KB/sec 500
Port: 80: 40 KB/sec 2 KB/sec 43 KB/sec 500
Port: 443: 53 KB/sec 8 KB/sec 64 KB/sec 500
Port: 443: 83 KB/sec 9 KB/sec 99 KB/sec 500
Port: 7255: 100 KB/sec 8 KB/sec 110 KB/sec 500
Port: 7255: 79 KB/sec 6 KB/sec 88 KB/sec 500
Port: 7003: 49 KB/sec 10 KB/sec 102 KB/sec 500
Port: 7003: 61 KB/sec 11 KB/sec 142 KB/sec 500
Port: 7202: 30 KB/sec 13 KB/sec 249 KB/sec 500
Port: 7202: timed out
Port: 7499: 8 KB/sec 4 KB/sec 141 KB/sec 500
Port: 7499: 13 KB/sec 1 KB/sec 16 KB/sec 500
Port: 80: 11 KB/sec 1 KB/sec 14 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
3) ISP = Verizon
*EDIT* I only realize now that creating a new thread may have been superfluous...but alas, here we are.
Comments
STO please re-route the traffic. I am on verizon fios and I know its not the computer, this is a server side issue.
The game runs from from dawn to around 2 or 3 my time then it just starts with the server not responding, the lag, and around 6pm thats when it starts to become unbearable which is irritating because thats when I play the most is around 6pm till late.
FIX THIS
Anyone want to give me a Temporal Heavy Dreadnought pack? I'll be your friend
Nope, not a Server side issue, as I've had no problem playing STO today...
Other players have reported problems with Verizon, so this appears to be a Verizon ISP issue, and only Verizon can correct this problem...
Wrong. This is absolutely not an ISP issue. Problems are reported from all players across all ISPs. I log in with my account, all laggy directly or through all 3 proxies. I relog to my friend's account on this same connection at this same PC, runs perfectly. I make a new free account, runs perfectly. I log into my own account again, all laggy again.
It is not our connection, it's not even their connection, it is, in fact, within the server. The server is just TRIBBLE up some accounts, and they need to fix it.
CMD (Administrator):
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 dslrouter.westell.com [192.168.1.1]
2 40 ms 58 ms 25 ms c-24-30-96-1.hsd1.ga.comcast.net [24.30.96.1]
3 24 ms 23 ms * xe-10-1-0-32767-sur01.d7decatur.ga.atlanta.comca
st.net [68.85.90.137]
4 * 24 ms * xe-8-0-0-0-ar01.b0atlanta.ga.atlanta.comcast.net
[68.86.106.146]
5 * 12 ms 13 ms he-5-14-0-0-10-cr01.56marietta.ga.ibone.comcast.
net [68.86.91.253]
6 * * * Request timed out.
7 167 ms 30 ms 27 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.5
4.10.233]
8 40 ms 32 ms 26 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40
.249]
9 * * 29 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
.94]
10 * * * Request timed out.
11 * 91 ms 94 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
12 97 ms 85 ms 86 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
13 57 ms 53 ms 53 ms 38.111.40.114
14 3628 ms * 46 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
Troubleshoot Problems:
PrintWindows Network Diagnostics Publisher details
Issues found
Your computer appears to be correctly configured, but the device or resource (patchserver.crypticstudios.com) is not respondingYour computer appears to be correctly configured, but the device or resource (patchserver.crypticstudios.com) is not responding Detected Detected
Contact your network administrator or Internet service provider (ISP) Completed
Issues found Detection details
5 Your computer appears to be correctly configured, but the device or resource (patchserver.crypticstudios.com) is not responding Detected Detected
Contact your network administrator or Internet service provider (ISP) Completed
Windows can't communicate with the device or resource (patchserver.crypticstudios.com). The computer or service you are trying to reach might be temporarily unavailable.
Detection details Expand
InformationalDiagnostics Information (Network Adapter)
Details about network adapter diagnosis:
Network adapter Local Area Connection 2 driver information:
Description . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
Manufacturer . . . . . . . . . : Intel
Provider . . . . . . . . . . . : Intel
Version . . . . . . . . . . . : 12.6.45.0
Inf File Name . . . . . . . . . : C:\Windows\INF\oem9.inf
Inf File Date . . . . . . . . . : Thursday, May 16, 2013 12:05:02 AM
Section Name . . . . . . . . . : E1503.6.1.1
Hardware ID . . . . . . . . . . : pci\ven_8086&dev_1503
Instance Status Flags . . . . . : 0x180200a
Device Manager Status Code . . : 0
IfType . . . . . . . . . . . . : 6
Physical Media Type . . . . . . : 0
InformationalNetwork Diagnostics Log
File Name: 44FC9D14-4376-4CB0-8FD1-4664CC2D0130.Diagnose.0.etl
InformationalNetwork Diagnostics Log
File Name: 10C8E816-7E7C-4AAE-BACC-F32309E198EB.Diagnose.1.etl
InformationalOther Networking Configuration and Logs
File Name: NetworkConfiguration.cab
InformationalOther Networking Configuration and Logs
File Name: NetworkConfiguration.cab
Collection information
Computer Name: TYREEJSIMMONS
Windows Version: 6.1
Architecture: amd64
Time: Tuesday, January 07, 2014 12:47:45 PM
Publisher details Expand
Windows Network Diagnostics
Detects problems with network connectivity.
Package Version: 1.0
Publisher: Microsoft Windows
CMD (Administrator):
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert digimonmasters.com
Tracing route to digimonmasters.com [118.130.130.168]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 37 ms 40 ms 39 ms c-24-30-96-1.hsd1.ga.comcast.net [24.30.96.1]
3 27 ms 25 ms 10 ms xe-10-1-0-32767-sur01.d7decatur.ga.atlanta.comca
st.net [68.85.90.137]
4 10 ms 9 ms 10 ms xe-22-0-2-0-ar01.b0atlanta.ga.atlanta.comcast.ne
t [68.85.111.129]
5 14 ms 14 ms 13 ms he-5-13-0-0-10-cr01.56marietta.ga.ibone.comcast.
net [68.86.93.201]
6 23 ms 27 ms 23 ms he-0-11-0-0-cr01.miami.fl.ibone.comcast.net [68.
86.88.214]
7 25 ms 23 ms 23 ms be-17-pe02.nota.fl.ibone.comcast.net [68.86.83.1
54]
8 24 ms 23 ms 23 ms n-a.GW1.MIA19.ALTER.NET [152.179.236.1]
9 23 ms 24 ms 23 ms 0.xe-5-0-0.XL1.MIA19.ALTER.NET [152.63.84.181]
10 * * * Request timed out.
11 87 ms * 118 ms GigabitEthernet6-0-0.GW3.SCL2.ALTER.NET [152.63.
49.93]
12 89 ms 99 ms 89 ms lgdacom-gw.customer.alter.net [157.130.206.146]
13 89 ms 89 ms 98 ms 203.255.234.133
14 217 ms 215 ms 208 ms 203.233.52.165
15 233 ms 219 ms 219 ms 1.213.147.254
16 219 ms 219 ms 220 ms 182.162.0.114
17 232 ms 231 ms 233 ms 182.162.64.2
18 218 ms 233 ms 216 ms 110.45.150.34
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.
C:\Windows\system32>
Try substituting the 'pathping' command for the 'tracert' command, as unlike the other commands 'Path Ping' will test for dropped packets, and show where its occurring...
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>path ping patchserver.crypticstudios.com
C:\Windows\system32>pathping patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 TyreeJSimmons.westell.com [192.168.1.15]
1 dslrouter.westell.com [192.168.1.1]
2 c-24-30-96-1.hsd1.ga.comcast.net [24.30.96.1]
3 xe-10-1-0-32767-sur01.d7decatur.ga.atlanta.comcast.net [68.85.90.137]
4 xe-8-0-0-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.86.106.146]
5 he-5-15-0-0-11-cr01.56marietta.ga.ibone.comcast.net [68.86.87.205]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 TyreeJSimmons.westell.com [192.168
.1.15]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% dslrouter.westell.com [192.168.1.1
]
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% c-24-30-96-1.hsd1.ga.comcast.net [
24.30.96.1]
0/ 100 = 0% |
3 14ms 1/ 100 = 1% 1/ 100 = 1% xe-10-1-0-32767-sur01.d7decatur.ga
.atlanta.comcast.net [68.85.90.137]
0/ 100 = 0% |
4 18ms 0/ 100 = 0% 0/ 100 = 0% xe-8-0-0-0-ar01.b0atlanta.ga.atlan
ta.comcast.net [68.86.106.146]
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% he-5-15-0-0-11-cr01.56marietta.ga.
ibone.comcast.net [68.86.87.205]
Trace complete.
C:\Windows\system32>
So 'Path Ping' didn't complete, which is not good...
Hop #3 is showing dropped packets, and you shouldn't be having any this close to your connection...
And 'Path Ping' gives up at hop #6... Looks like its time to contact Comcast Tech Support and get them to help diagnose your connection problems...
Same problem, same ISP, roughly the same geographical location. I logged into STO through a VPN and that eliminated the problem; not a permanent solution, but it does seem to indicate that the problem is somewhere in the routing of traffic between Verizon and whatever network the STO server is on.
I submitted a bug ticket but we all know they go in the trash for no one to respond or fix.