Lt. Commander
Join Date: Dec 2007
Posts: 120
I've been playing this game for a good couple of weeks with no problems. However, the last 3 days it's become virtually unplayable. Either:
- Connection cannot be made to login server
- The game starts loading maps then dumps back to the login screen
- Account server cannot be contacted
- Or, when finally in game, it'll run for around half an hour or until it hits one too many loading screens, then gets the dreaded "server not responding"

This seems to be getting gradually worse; the "server not responding" error has moved from just occurring on load screens to in sector space/start of STFs as well. This is obviously becoming rather irritating! It's nothing wrong with my computer - it happens on both machines on the network. The router's been reset, updated, and tweaked to no end. All firewalls have been disabled. Nothing really helps! I've even contacted the ISP to verify there's nothing wrong with my connection. Speed test shows ping to be 33ms, more than good enough. No other browsing's affected, except when STO's open. I've got rid of Pando, done a full patch, and am compeltely out of ideas. Anyone help? Or do I just have to wait for the server tribbles to breed?
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 2
02-13-2012, 02:20 AM
How to Diagnose Lag and Rubberbanding
Tried?

Oh and turn the fricken firewall back up NOW!
It can NEVER the problem once you were successfully able to play a game. Luckily you have a router in between your computer and the internet. Otherwise you would´ve been infected in a matter of minutes.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 3
02-13-2012, 03:26 AM
I only took the firewall down briefly, to check if it was a port issue. It's back up already.

The tracert is more than mildly concerning, mind...

1st run:

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 18 ms 99 ms 99 ms ***.**.***.**
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 22 ms 23 ms 23 ms **.*.*.***
6 21 ms 22 ms 22 ms TenGigabitEthernet4-3.ar4.LON3.gblx.net [64.214.
106.253]
7 100 ms 100 ms 100 ms te0-1-0-3.ccr21.jfk07.atlas.cogentco.com [154.54
.11.61]
8 97 ms 97 ms 97 ms te0-2-0-4.ccr21.jfk02.atlas.cogentco.com [154.54
.2.185]
9 106 ms 107 ms 106 ms te0-3-0-2.ccr22.bos01.atlas.cogentco.com [154.54
.44.46]
10 112 ms * 111 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 97 ms 108 ms 108 ms 38.111.40.114
12 96 ms * * 208.95.185.41
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.

2nd:

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 81 ms 100 ms 99 ms ***.***.*.***
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * 25 ms 22 ms **.*.*.***
6 194 ms 119 ms 84 ms TenGigabitEthernet4-3.ar4.LON3.gblx.net [64.214.
106.253]
7 100 ms 100 ms 100 ms te0-1-0-3.ccr21.jfk07.atlas.cogentco.com [154.54
.11.61]
8 97 ms 97 ms 97 ms te0-2-0-4.ccr21.jfk02.atlas.cogentco.com [154.54
.2.185]
9 107 ms 106 ms 106 ms te0-3-0-2.ccr22.bos01.atlas.cogentco.com [154.54
.44.46]
10 * 111 ms 113 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 104 ms 107 ms 108 ms 38.111.40.114
12 96 ms 94 ms * 208.95.185.41
13 94 ms 96 ms 95 ms 208.95.185.41

Trace complete.

I'm not liking all them timeouts - not good...
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 4
02-13-2012, 03:51 AM
Not sure what happened in your first trace, as it should have finished at the 12th step. Cryptic servers are a bit wonky ATM, so maybe it´s that.

But your timeouts in steps 2-4 are indeed a bit odd.
That usually points to ISP problems. Though you´re also getting " * " in other steps. Follow the other instructions in the thread and a Dev will eventually help you.
I´m a bit stumped why you have so high lag in your 1st step though. WiFi?

BTW, edit out the addresses of your first two steps when posting them openly on the internet.
No need to pin that "hack me" post-it to your own forehead.

Though 1st is usually the router, so not that critical. You can leave it there usually.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 5
02-13-2012, 04:01 AM
Oops, I thought I'd already blanked those...

That early lag confused me too. I'm running cables all the way, so it's not a wifi issue.

I've submitted a ticket, so hopefully someone'll get back to me soonish and this can be stamped out.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 6
02-13-2012, 12:37 PM
Quote:
Originally Posted by ivarST
Oh and turn the fricken firewall back up NOW!
It can NEVER the problem once you were successfully able to play a game. Luckily you have a router in between your computer and the internet. Otherwise you would´ve been infected in a matter of minutes.
Sorry to be the cranky old man here, but I gotta say, I love it when people learn about technology from Hollywood.

Back on topic though, I could give you the runthrough that helped my stomp out this problem recently if you would like.
I'll need you to go to StarTrekOnline/Live/logs/GameClient and open up Clientservercomm.LOG. Then copy and paste roughly the last 20 lines you see there, here.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 7
02-13-2012, 01:35 PM
Quote:
Originally Posted by themurgy
Sorry to be the cranky old man here, but I gotta say, I love it when people learn about technology from Hollywood.
If you say so Mr. "white elephant" Sir.
Guess my router log constantly showing the crudest netbios and other script kiddy fishing pings is just "Hollywood". Got it.

I guess if you´re too awesome you don´t need a router or firewall anymore.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 8
02-13-2012, 02:49 PM
Its a fault at cryptics ends which they refuse to even acknowledge.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 9
02-13-2012, 05:37 PM
Quote:
Originally Posted by themurgy
I'll need you to go to StarTrekOnline/Live/logs/GameClient and open up Clientservercomm.LOG. Then copy and paste roughly the last 20 lines you see there, here.
OK, here you go - any help graciously accepted at this point!


120213 10:45:47 54 Client[0]: GameServer link attempting connect (208.95.184.102:7313).
120213 10:45:47 55 Client[0]: GameServer link connected (208.95.184.102:7313).
120213 10:46:03 57 Client[0]: GameServer link disconnected (208.95.184.102:7313). Reason: socket was shutdown(0:No error) (socket error 0: No error)
120213 10:46:03 58 Client[0]: GameServer link attempting connect (208.95.184.105:7240).
120213 10:46:04 59 Client[0]: GameServer link connected (208.95.184.105:7240).
120213 10:46:15 60 Client[0]: GameServer link unresponsive for more than 5 seconds.
120213 10:47:15 61 Client[0]: GameServer link unresponsive for more than 5 seconds.
120213 10:48:21 63 Client[0]: GameServer link unresponsive for more than 5 seconds.
120213 10:50:40 14 Client[0]: LoginServer link attempting connect: 208.95.184.129:7001
120213 10:50:44 15 Client[0]: LoginServer link disconnected (208.95.184.129:7001). Reason: socket was shutdown(0:No error) (socket error 0: No error)
120213 10:50:44 16 Client[0]: GameServer link attempting connect (208.95.184.105:7240).
120213 10:50:49 17 Client[0]: GameServer link unresponsive for more than 5 seconds.
120213 10:50:54 18 Client[0]: GameServer link being forcibly disconnected by client (208.95.184.105:7240): Timed out connecting to GameServer
120213 10:51:03 19 Client[0]: LoginServer link attempting connect: 208.95.184.43:7001
120213 10:51:09 20 Client[0]: LoginServer link disconnected (208.95.184.43:7001). Reason: socket was shutdown(0:No error) (socket error 0: No error)
120213 10:51:09 21 Client[0]: GameServer link attempting connect (208.95.184.105:7240).
120213 10:51:09 22 Client[0]: GameServer link connected (208.95.184.105:7240).
120213 10:51:24 23 Client[0]: GameServer link unresponsive for more than 5 seconds.
120213 10:53:05 14 Client[0]: LoginServer link attempting connect: 208.95.184.43:7001
120213 10:53:09 15 Client[0]: LoginServer link disconnected (208.95.184.43:7001). Reason: socket was shutdown(0:No error) (socket error 0: No error)
120213 10:53:09 16 Client[0]: GameServer link attempting connect (208.95.184.105:7240).
120213 10:53:09 17 Client[0]: GameServer link connected (208.95.184.105:7240).
120213 10:53:29 22 Client[0]: GameServer link disconnected (208.95.184.105:7240). Reason: socket was shutdown(0:No error) (socket error 0: No error)
120213 10:53:29 23 Client[0]: GameServer link attempting connect (208.95.184.160:7387).
120213 10:53:29 27 Client[0]: GameServer link connected (208.95.184.160:7387).

The whole file's pretty much more of the same.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 10
02-14-2012, 01:12 AM
You have these odd constant timeouts.

Glancing at my own log it has the disconnects too, but they are immediately followed by successful reconnects. Also manages to stay connected for longer periods.
The client seems to routinely loose connects, probably because of the current server strain. But it usually manages to reconnect immediately.

Yours obviously doesn´t. Have you tried that nettest program?
How are other online games running on your computer?
Cute test would be Champions Online.
If that works then it´s clearly a STO server problem.
Reply

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 02:32 AM.