Career Officer
Join Date: Jun 2012
Posts: 2,217
# 471
10-13-2013, 08:50 PM
Quote:
Originally Posted by furiontassadar View Post
What does it mean when you can't even get nettest to work? Whenever I run it, it says "timed out".
...
If you want to be technical, it means that 'Net Test' and the diagnostic server on the STO network could not complete the TCP/IP three way handshake used to establish a connection...

In simpler layman terms, it can't connect...

And this is a connection to a much simpler diagnostic server, so any additional overhead and load on the STO Servers are out of the picture here. So if you can't connect to the Net Test Server, its highly unlikely you can connect to the STO Server, showing that this is a Internet connection issue and not a STO Server issue...

Now why it can't connect, it could be router issues, firewall misconfiguration, ISP blocking or throttling, excessive network congestion, etc. etc. Thats what the other network diagnostics are for, to rule out other causes and try to pinpoint what the exact issue is. The 'Trace Route' diagnostic is useful for looking at ISP issues and network congestion on the route to the STO servers....

Last edited by grouchyotaku; 10-13-2013 at 08:54 PM.
Lt. Commander
Join Date: Aug 2013
Posts: 113
# 472
10-13-2013, 09:46 PM
Quote:
Originally Posted by grouchyotaku View Post
Now why it can't connect, it could be router issues, firewall misconfiguration, ISP blocking or throttling, excessive network congestion, etc. etc. Thats what the other network diagnostics are for, to rule out other causes and try to pinpoint what the exact issue is. The 'Trace Route' diagnostic is useful for looking at ISP issues and network congestion on the route to the STO servers....
I think it may have been an "etc." on my computer's end. I had some theories as to what may have been causing the problem, and did a system restore just to see. That seems to have fixed the problem: I was able to log on and play.

Thanks for all that info though. If I have problems of a similar nature, next time I'll try posting what my Trace Route diagnostic came up with, too.
Lieutenant
Join Date: Jun 2012
Posts: 77
# 473 rubberbanding
10-15-2013, 11:29 AM
Over the past month lag and rubberbanding has gotten steadily worse for me, to the point where I generally can't pvp. I ran the tests outlined by the OP and these were my results, which I certainly have no idea how to interpret.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\ServicePackFiles\i386>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.1.1
2 * * * Request timed out.
3 10 ms 9 ms 11 ms ten0-7-0-0.ORLD23-ser2.bhn.net [72.31.194.42]
4 10 ms 11 ms 11 ms ten0-1-0-7.orld31-car2.bhn.net [97.69.194.196]
5 27 ms 23 ms 22 ms ten0-4-0-6.orld71-car2.bhn.net [71.44.61.22]
6 13 ms 15 ms 15 ms 72-31-193-191.net.bhntampa.com [72.31.193.191]
7 19 ms 19 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
8 25 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
9 23 ms 23 ms 24 ms 107.14.19.13
10 93 ms 93 ms 88 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]
11 92 ms 91 ms 94 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.
165]
12 96 ms 103 ms 98 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31
.106]
13 104 ms 103 ms 102 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
14 109 ms 107 ms 108 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
15 127 ms 110 ms 108 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
16 116 ms 111 ms 110 ms 38.111.40.114
17 108 ms 108 ms 106 ms 208.95.185.41

Trace complete.


contacting nettest server..
Local IP: 142.197.65.31
Ping: 130.5 msec
Port: 80: 33 KB/sec 4 KB/sec 52 KB/sec 500
Port: 80: 33 KB/sec 3 KB/sec 51 KB/sec 500
Port: 443: 25 KB/sec 3 KB/sec 35 KB/sec 500
Port: 443: 32 KB/sec 4 KB/sec 49 KB/sec 500
Port: 7255: 28 KB/sec 3 KB/sec 43 KB/sec 500
Port: 7255: timed out
Port: 7003: 37 KB/sec 4 KB/sec 60 KB/sec 500
Port: 7003: 40 KB/sec 3 KB/sec 55 KB/sec 500
Port: 7202: 24 KB/sec 3 KB/sec 38 KB/sec 500
Port: 7202: 28 KB/sec 2 KB/sec 32 KB/sec 500
Port: 7499: 43 KB/sec 2 KB/sec 49 KB/sec 500
Port: 7499: 28 KB/sec 2 KB/sec 34 KB/sec 500
Port: 80: 25 KB/sec 3 KB/sec 47 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 10 KB/sec
hit return to exit


My ISP is Brighthouse/Roadrunner in the central Florida USA area. I'm curious what I can do to fix my issue
Career Officer
Join Date: Jun 2012
Posts: 2,217
# 474
10-15-2013, 11:55 AM
Quote:
Originally Posted by gueneyhallek0420 View Post

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.1.1
2 * * * Request timed out.
3 10 ms 9 ms 11 ms ten0-7-0-0.ORLD23-ser2.bhn.net [72.31.194.42][color="Red"]
4 10 ms 11 ms 11 ms ten0-1-0-7.orld31-car2.bhn.net [97.69.194.196]
5 27 ms 23 ms 22 ms ten0-4-0-6.orld71-car2.bhn.net [71.44.61.22]
6 13 ms 15 ms 15 ms 72-31-193-191.net.bhntampa.com [72.31.193.191]
7 19 ms 19 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
8 25 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
9 23 ms 23 ms 24 ms 107.14.19.13
10 93 ms 93 ms 88 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]

11 92 ms 91 ms 94 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.
165]
12 96 ms 103 ms 98 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31
.106]
13 104 ms 103 ms 102 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
14 109 ms 107 ms 108 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
15 127 ms 110 ms 108 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
16 116 ms 111 ms 110 ms 38.111.40.114
17 108 ms 108 ms 106 ms 208.95.185.41

Trace complete.


My ISP is Brighthouse/Roadrunner in the central Florida USA area. I'm curious what I can do to fix my issue
Your showing the same symptoms as other players who connect via the Road Runner service. The 'Net Test' results shows degraded performance, most likely from excessive packet drop. And the Trace Route hints that this is occurring on the gateway between the Road Runner and Cogent backbone. This is a ISP issue as only the ISP involved can correct this problem. Looks like its time to contact your ISP... (complain about severe packet drop on your connection to the STO Servers)
Ensign
Join Date: Mar 2013
Posts: 1
# 475 What the hell?!
10-15-2013, 05:15 PM
I'm not entirely sure where to post this, but starting since last night I haven't been able to log in AT ALL. I keep getting disconnected almost immediatly after managing to make my way into the game. Sometimes I can stay in or several minutes, but lately it's just effing broken. There's nothing wrong with my connection, but for some reason I am CONSTANTLY getting disconnected from the server everytime I get into game.
Career Officer
Join Date: Jun 2012
Posts: 2,217
# 476
10-16-2013, 07:52 AM
Quote:
Originally Posted by c01hamster View Post
I'm not entirely sure where to post this, but starting since last night I haven't been able to log in AT ALL. I keep getting disconnected almost immediatly after managing to make my way into the game. Sometimes I can stay in or several minutes, but lately it's just effing broken. There's nothing wrong with my connection, but for some reason I am CONSTANTLY getting disconnected from the server everytime I get into game.
So what does your 'Net Test' and 'Trace Route' results look like??? No one will be able to help you unless you provide some information...
Ensign
Join Date: Jun 2012
Posts: 5
# 477 Unplayable...
10-19-2013, 06:43 AM
Hi all,

I have been keeping a close eye on threads such as this one after last Thursday's update. Ever since then I have had the same symptoms as many other people are reporting, the Lag, rubber banding ETC. I have tried using both a static IP and a dynamic IP and there has been no difference. The Traceroute looks to be ok but my Nettest results seem terrible when compared with the good results marked in the first post. Any advice would be greatly appreciated! I managed to get through a CCE mission without any problems when I tried at 07:30GMT which I have been unable to do since Thursday night!

Traceroute 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 www.routerlogin.com [192.168.0.1]
2 36 ms 36 ms 35 ms 62.72.148.128
3 34 ms 35 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
4 37 ms 34 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
5 69 ms 60 ms 57 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
6 37 ms 35 ms 36 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
7 36 ms 35 ms 34 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

8 36 ms 37 ms 35 ms ge-7-0-0.mpr1.lhr2.uk.above.net [64.125.28.25]
9 108 ms 107 ms 108 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
10 108 ms 109 ms 108 ms xe-0-0-0.cr2.dca2.us.above.net [64.125.28.242]
11 120 ms 119 ms 119 ms xe-1-1-0.mpr4.bos2.us.above.net [64.125.24.117]

12 118 ms 119 ms 119 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
13 117 ms 116 ms 116 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
14 129 ms 115 ms 116 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 116 ms 124 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 116 ms 115 ms 115 ms 208.95.185.41

Trace complete.


Nettest Results:

contacting nettest server..
Local IP: 95.172.231.84
Ping: 115.4 msec
Port: 80: 34 KB/sec 1 KB/sec 36 KB/sec 500
Port: 80: 34 KB/sec 11 KB/sec 83 KB/sec 500
Port: 443: 41 KB/sec 6 KB/sec 51 KB/sec 500
Port: 443: 42 KB/sec 3 KB/sec 57 KB/sec 500
Port: 7255: 46 KB/sec 3 KB/sec 64 KB/sec 500
Port: 7255: 36 KB/sec 6 KB/sec 54 KB/sec 500
Port: 7003: 50 KB/sec 3 KB/sec 58 KB/sec 500
Port: 7003: 44 KB/sec 2 KB/sec 56 KB/sec 500
Port: 7202: 94 KB/sec 5 KB/sec 148 KB/sec 500
Port: 7202: 45 KB/sec 5 KB/sec 142 KB/sec 500
Port: 7499: 103 KB/sec 5 KB/sec 133 KB/sec 500
Port: 7499: 34 KB/sec 2 KB/sec 37 KB/sec 500
Port: 80: 36 KB/sec 2 KB/sec 49 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec


I am based in the UK if that helps... It would seem everyone else having the problem who has taken to the forums is Stateside...

Many thanks in advance!

D

Last edited by gijock1701; 10-19-2013 at 06:47 AM.
Career Officer
Join Date: Jun 2012
Posts: 2,217
# 478
10-19-2013, 07:34 AM
Quote:
Originally Posted by gijock1701 View Post
Hi all,

I have been keeping a close eye on threads such as this one after last Thursday's update. Ever since then I have had the same symptoms as many other people are reporting, the Lag, rubber banding ETC. I have tried using both a static IP and a dynamic IP and there has been no difference. The Traceroute looks to be ok ...

Traceroute 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 www.routerlogin.com [192.168.0.1]
2 36 ms 36 ms 35 ms 62.72.148.128
3 34 ms 35 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
4 37 ms 34 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
5 69 ms 60 ms 57 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
6 37 ms 35 ms 36 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
7 36 ms 35 ms 34 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

8 36 ms 37 ms 35 ms ge-7-0-0.mpr1.lhr2.uk.above.net [64.125.28.25]
9 108 ms 107 ms 108 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]

10 108 ms 109 ms 108 ms xe-0-0-0.cr2.dca2.us.above.net [64.125.28.242]
11 120 ms 119 ms 119 ms xe-1-1-0.mpr4.bos2.us.above.net [64.125.24.117]

12 118 ms 119 ms 119 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
13 117 ms 116 ms 116 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
14 129 ms 115 ms 116 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 116 ms 124 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 116 ms 115 ms 115 ms 208.95.185.41

Trace complete.
Looks like the above.net Trans-Atlantic link (uk - us) is suffering from network congestion issues, and most likely is the source of the severe packet drop that is causing your poor Net Test results....

This is a ISP issue, as only above.net can correct the problem with their Trans-Atlantic cable connection...
Ensign
Join Date: Jun 2012
Posts: 5
# 479 Cheers!
10-19-2013, 08:18 AM
Quote:
Originally Posted by grouchyotaku View Post
Looks like the above.net Trans-Atlantic link (uk - us) is suffering from network congestion issues, and most likely is the source of the severe packet drop that is causing your poor Net Test results....

This is a ISP issue, as only above.net can correct the problem with their Trans-Atlantic cable connection...
Many thanks Grouchy! I will get on them straight away!

Ensign
Join Date: Oct 2013
Posts: 2
# 480
10-25-2013, 11:19 PM
Interesting conclusion from that tracert you have, i'd be interested in how you get packet loss from it.

Do a pathping -n instead of tracert and this will help you understand it - http://technet.microsoft.com/en-us/l.../cc958876.aspx

A good read on tracert - http://www.nanog.org/meetings/nanog4...eroute_N45.pdf

Last edited by shannara4; 10-25-2013 at 11:28 PM.
Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 11:22 AM.