Oh, and by the way, it may sound silly, but.. When I had the game open, not able to login though trying and was browsing the forums at the same time I had problems accesing various pages, they were loading slowly or not at all. Now as I closed the game everything went back to normal. It isn't the computer's fault, normally I can run many other programs while playing. Is it possible that me not being able to login has somehow affected my internet connection? It sounds improbable for me, but maybe?..
STO uses a greater number of simultaneous network connections then most other MMOs. If you're using a low budget wireless router, you could be approaching the upper limit on supported network connections, and have started to thrash the unit...
If these problems are really routing problem (which they are not) then cryptic should get a host who can handle their game? Like most companies they want profit, that means they wanna run the game as cheap as possible so they use inferior hardware and connections. I see these "routing problem" come by to many times. There are MMO's with way way more people without routing problems. This is what we people pay for lol.
When it was really a routing problem however I wouldn't be able to trace onto cryptics network where the timeouts start. I can post 1000 traces but they still blame it on good old routing problems, which seems to be their standard reply. Sad enough...
Is this at all related to me not getting an Account Verification email for my new computer? Been waiting for quite a while now, and that's after a VERY slow client download.
[SIGPIC][/SIGPIC]
The Big Home-Built Beast:
AMD FX-6300 3.5GHz Hex-Core, 8GB DDR3 RAM
MSI GeForce GTX 650 TI, 5.1-channel audio
Windows 7 Home Premium
I just wanted to say that a few hours after my last post I was able to login and play. Everything seems to be normal now. At first I got kicked out after trying to load other maps but now it seems to work fine!
Hi, I'm new here and it won't let me start my own thread to disuss the problem I'm having...
I'm just about to give up ever playing this game and I haven't even started yet. After spending a week trying to get Perfect World to recognize that my email address was not already registered with them, I was finally able to open Arc and select the game for download. Now I can open the launcher but that is about as far as I get since, after entering my login and password, pressing the "login" button or the enter key on my keyboard produces absolutely no result. Nothing.
This is very frustrating since I've heard a lot of good things about STO and was looking forward to playing.
Has anyone else had this problem? If so, would anyone be able to please direct me to a thread that deals with it?
HI guys iam experiencing massive problems with your server / network:
the plot show the cryptic gateway and server having problems. Please fix it as fast as you can want to play.
Routenverfolgung zu patchserver2.crypticstudios.com [208.95.185.41] ?ber maximal
30 Abschnitte:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 14 ms 15 ms 14 ms 8x.1xx.2xx.xx
3 20 ms 18 ms 19 ms 87.190.171.202
4 24 ms 23 ms 23 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.246]
5 76 ms 75 ms 75 ms te0-7-0-10.mag21.fra03.atlas.cogentco.com [130.1
17.14.105]
6 74 ms 75 ms 77 ms be2028.mpd21.fra03.atlas.cogentco.com [154.54.74
.137]
7 82 ms 80 ms 80 ms be2262.ccr22.ams03.atlas.cogentco.com [154.54.37
.33]
8 82 ms 81 ms 92 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
9 111 ms 112 ms 112 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44
.181]
10 115 ms 115 ms 115 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 * 155 ms * 38.111.40.114
12 * 156 ms * patchserver2.crypticstudios.com [208.95.185.41]
13 156 ms 155 ms 156 ms patchserver2.crypticstudios.com [208.95.185.41]
and it actually bounced me to the in game login cause the server timed itself to death..
Murphy's laws:
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
Thankfully it was working for me for most of the weekend, then late last night the problem popped up again.
Same server with the issue according to Tracert:
10 138 ms 230 ms 225 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
it's bos06 every time for me, there's no problem in the routing before that. bos01 is slow, but never goes above about 90ms. bos06 regularly spikes to over 200ms, if it responds at all.
Cryptic have to look into either getting a new host or providing some EU servers (although I understand that anyone in the US who is being routed the same way will experience the same issues).
I was going to spend some money on the game, but if I can't play it I'm not going to bother.
It's all well and good Cryptic saying that it's a network issue out of their control, but if it's their ISP with the issue they will certainly have the ability to raise a complaint on behalf of their customers.
I've contacted Cogent directly with some basic details. Will see what they say - maybe they've been conducting some work on the backbone or something.
EDIT: Apparently Cogent only want to talk to their customers or other ISP's, they aren't interested in anyone else advising them of a potential technical issue with their systems (even when providing evidence). That's nice and sensible. As a Software Analyst, personally I'd at least check out the reported issue.
EDIT2: Earlier response from Cogent UK. Cogent US provided the following information:
"Please be advised that the device you have provided is a Cogent core device that does deprioritize ICMP traffic. The high times and/or dropped ICMP requests you are seeing on some nodes are just specific to those nodes. They are largely due to the low priority which traceroute responses receive on most Layer 3 devices. Latency would show up on a traceroute as a jump in round trip time and would continue with high times for every node past that point. Packet loss would likewise affect every hop beyond the node in question. Since there are low times after the high times on your example, there is no real latency. The hops with 100% return beyond the troubled node(s) indicate that there isn't really any packet loss. What you are seeing is just an artifact of how traceroute works. "
That does actually make a lot of sense. On the downside, this would suggest that it's more than likely a problem with the Cryptic servers that they don't seem to want to acknowledge.
I wonder if they've actually fully investigated, or are making assumptions (as I was) based on the tracert results?
Thankfully it was working for me for most of the weekend, then late last night the problem popped up again.
Same server with the issue according to Tracert:
10 138 ms 230 ms 225 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
it's bos06 every time for me, there's no problem in the routing before that. bos01 is slow, but never goes above about 90ms. bos06 regularly spikes to over 200ms, if it responds at all.
Cryptic have to look into either getting a new host or providing some EU servers (although I understand that anyone in the US who is being routed the same way will experience the same issues).
seraphtc you are correct, the bos06 server ran a bit slow on my end.
I did two partial tracert (it auto-terminates when it finishes so that was all I could get) and one nettest and my results are below; I'm not holding out hope for Cryptic/PWE to figure out why there are so many Server Not Responding messages and d/c's lately.
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 139 ms 2 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 * 26 ms 26 ms 38.104.210.154
4 74 ms 73 ms 73 ms gi2-1.mag02.lax04.atlas.cogentco.com [38.104.211.157]
5 71 ms 73 ms 73 ms te0-7-0-12.ccr21.lax04.atlas.cogentco.com [154.54.87.70]
6 74 ms 74 ms 84 ms be2021.mpd21.lax01.atlas.cogentco.com [154.54.87.249]
7 109 ms 116 ms 109 ms be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.65]
8 136 ms 132 ms 131 ms be2174.mpd21.atl01.atlas.cogentco.com [154.54.29.201]
9 140 ms 141 ms 140 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
10 147 ms 141 ms 148 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 148 ms 156 ms 155 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
12 155 ms 154 ms 154 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
13 158 ms 160 ms 147 ms
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 724 ms 2 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 * 25 ms 26 ms 38.104.210.154
4 73 ms 73 ms 74 ms gi2-1.mag02.lax04.atlas.cogentco.com [38.104.211.157]
5 72 ms 73 ms 72 ms te0-7-0-12.ccr21.lax04.atlas.cogentco.com [154.54.87.70]
6 84 ms 75 ms 76 ms be2019.ccr21.lax01.atlas.cogentco.com [154.54.88.9]
7 109 ms 109 ms 117 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.161]
8 132 ms 131 ms 131 ms be2172.ccr21.atl01.atlas.cogentco.com [154.54.29.17]
9 141 ms 140 ms 139 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
10 149 ms 151 ms 141 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 155 ms 147 ms 148 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
12 276 ms 209 ms 216 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
13 154 ms 145 ms 159 ms
People assume that time is a strict progression of cause to effect. But actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly-wobbly timey-wimey ... stuff. --the Doctor, "Blink"
Try substituting 'pathping' for the 'tracert' command, and post the results, as network latency isn't the only issue that can effect a TCP/IP connection...
OK this is what I got for "pathping patchserver.crypticstudios.com" ... it's not like I have anything better to do like pelt snowmen with snowballs
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 GaryLi-PC.gateway.2wire.net [192.168.1.65]
1 192.168.1.254
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GaryLi-PC.gateway.2wire.net [192.168.1.65]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0%
Supplemental information:
All the game servers on http://www.mmoserverstatus.com/star_trek_online are working. Sometimes there is no warning, just sudden d/c. Other times Server Not Responding pops up and it disconnects after a while. Sector space seems to be a little bit more stable than ground maps.
People assume that time is a strict progression of cause to effect. But actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly-wobbly timey-wimey ... stuff. --the Doctor, "Blink"
OK I think I found a possible solution to the Server Not Responding messages and disconnects. A few hours ago I logged into the game and both my Rom and Klingon characters had SNR problems, both ground and space (actually Dyson sphere).
Here's what I did:
I used the Windows Run command to enter "ipconfig /release" (without the quotes)
Then disconnected the power to my wireless router for 60 seconds
After reconnecting my router and made sure it reset itself, and that all lights were normal: I used Run again and entered "ipconfig /renew" (again, no quotes).
That was it. Both chars worked again, no SNRs in two hours of gameplay! Try it and see if it works for you. Hope that helps!
People assume that time is a strict progression of cause to effect. But actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly-wobbly timey-wimey ... stuff. --the Doctor, "Blink"
Game froze up while playing, first chat went down then all characters just locked in place. When I tried to log back in I am getting disconnected from game server, anyone else?
If im not using a proxy (Option in the launcher) I will get the "Server not responding" followed by "Disconnected from server" every time I try to enter or leave a mission, map och instance.
If I use the proxy, I cant connect at all if its the eu1 proxy. The eu2 proxy works fine though; No disconnects, no lag, no nothing. It just works.
Seems like Cryptic should take a look at the eu1 proxy?
Comments
STO uses a greater number of simultaneous network connections then most other MMOs. If you're using a low budget wireless router, you could be approaching the upper limit on supported network connections, and have started to thrash the unit...
When it was really a routing problem however I wouldn't be able to trace onto cryptics network where the timeouts start. I can post 1000 traces but they still blame it on good old routing problems, which seems to be their standard reply. Sad enough...
The Big Home-Built Beast:
AMD FX-6300 3.5GHz Hex-Core, 8GB DDR3 RAM
MSI GeForce GTX 650 TI, 5.1-channel audio
Windows 7 Home Premium
I'm just about to give up ever playing this game and I haven't even started yet. After spending a week trying to get Perfect World to recognize that my email address was not already registered with them, I was finally able to open Arc and select the game for download. Now I can open the launcher but that is about as far as I get since, after entering my login and password, pressing the "login" button or the enter key on my keyboard produces absolutely no result. Nothing.
This is very frustrating since I've heard a lot of good things about STO and was looking forward to playing.
Has anyone else had this problem? If so, would anyone be able to please direct me to a thread that deals with it?
Thanks.
Perform the network diagnostics described in this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155
... and post the results, as this will provide some clues on what is causing your problem...
fixed it
the plot show the cryptic gateway and server having problems. Please fix it as fast as you can
Routenverfolgung zu patchserver2.crypticstudios.com [208.95.185.41] ?ber maximal
30 Abschnitte:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 14 ms 15 ms 14 ms 8x.1xx.2xx.xx
3 20 ms 18 ms 19 ms 87.190.171.202
4 24 ms 23 ms 23 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.246]
5 76 ms 75 ms 75 ms te0-7-0-10.mag21.fra03.atlas.cogentco.com [130.1
17.14.105]
6 74 ms 75 ms 77 ms be2028.mpd21.fra03.atlas.cogentco.com [154.54.74
.137]
7 82 ms 80 ms 80 ms be2262.ccr22.ams03.atlas.cogentco.com [154.54.37
.33]
8 82 ms 81 ms 92 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
9 111 ms 112 ms 112 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44
.181]
10 115 ms 115 ms 115 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 * 155 ms * 38.111.40.114
12 * 156 ms * patchserver2.crypticstudios.com [208.95.185.41]
13 156 ms 155 ms 156 ms patchserver2.crypticstudios.com [208.95.185.41]
Ablaufverfolgung beendet.
Thanks in advance
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
Same server with the issue according to Tracert:
10 138 ms 230 ms 225 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
it's bos06 every time for me, there's no problem in the routing before that. bos01 is slow, but never goes above about 90ms. bos06 regularly spikes to over 200ms, if it responds at all.
Cryptic have to look into either getting a new host or providing some EU servers (although I understand that anyone in the US who is being routed the same way will experience the same issues).
Im in europe and that happens all the time.
Btw I post this at the 245seconds SNR mark
EDIT: Not playable .SNR every 3 seconds ,rubberbanding.
I was going to spend some money on the game, but if I can't play it I'm not going to bother.
It's all well and good Cryptic saying that it's a network issue out of their control, but if it's their ISP with the issue they will certainly have the ability to raise a complaint on behalf of their customers.
I've contacted Cogent directly with some basic details. Will see what they say - maybe they've been conducting some work on the backbone or something.
EDIT: Apparently Cogent only want to talk to their customers or other ISP's, they aren't interested in anyone else advising them of a potential technical issue with their systems (even when providing evidence). That's nice and sensible. As a Software Analyst, personally I'd at least check out the reported issue.
EDIT2: Earlier response from Cogent UK. Cogent US provided the following information:
"Please be advised that the device you have provided is a Cogent core device that does deprioritize ICMP traffic. The high times and/or dropped ICMP requests you are seeing on some nodes are just specific to those nodes. They are largely due to the low priority which traceroute responses receive on most Layer 3 devices. Latency would show up on a traceroute as a jump in round trip time and would continue with high times for every node past that point. Packet loss would likewise affect every hop beyond the node in question. Since there are low times after the high times on your example, there is no real latency. The hops with 100% return beyond the troubled node(s) indicate that there isn't really any packet loss. What you are seeing is just an artifact of how traceroute works. "
That does actually make a lot of sense. On the downside, this would suggest that it's more than likely a problem with the Cryptic servers that they don't seem to want to acknowledge.
I wonder if they've actually fully investigated, or are making assumptions (as I was) based on the tracert results?
The EU proxy won't connect to anything at all (I can't even load the game as the launcher can't get to the tracker).
seraphtc you are correct, the bos06 server ran a bit slow on my end.
I did two partial tracert (it auto-terminates when it finishes so that was all I could get) and one nettest and my results are below; I'm not holding out hope for Cryptic/PWE to figure out why there are so many Server Not Responding messages and d/c's lately.
1 139 ms 2 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 * 26 ms 26 ms 38.104.210.154
4 74 ms 73 ms 73 ms gi2-1.mag02.lax04.atlas.cogentco.com [38.104.211.157]
5 71 ms 73 ms 73 ms te0-7-0-12.ccr21.lax04.atlas.cogentco.com [154.54.87.70]
6 74 ms 74 ms 84 ms be2021.mpd21.lax01.atlas.cogentco.com [154.54.87.249]
7 109 ms 116 ms 109 ms be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.65]
8 136 ms 132 ms 131 ms be2174.mpd21.atl01.atlas.cogentco.com [154.54.29.201]
9 140 ms 141 ms 140 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
10 147 ms 141 ms 148 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 148 ms 156 ms 155 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
12 155 ms 154 ms 154 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
13 158 ms 160 ms 147 ms
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 724 ms 2 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 * 25 ms 26 ms 38.104.210.154
4 73 ms 73 ms 74 ms gi2-1.mag02.lax04.atlas.cogentco.com [38.104.211.157]
5 72 ms 73 ms 72 ms te0-7-0-12.ccr21.lax04.atlas.cogentco.com [154.54.87.70]
6 84 ms 75 ms 76 ms be2019.ccr21.lax01.atlas.cogentco.com [154.54.88.9]
7 109 ms 109 ms 117 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.161]
8 132 ms 131 ms 131 ms be2172.ccr21.atl01.atlas.cogentco.com [154.54.29.17]
9 141 ms 140 ms 139 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
10 149 ms 151 ms 141 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 155 ms 147 ms 148 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
12 276 ms 209 ms 216 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
13 154 ms 145 ms 159 ms
contacting nettest server..
Local IP: 72.234.177.114
Ping: 150.3 msec
Port: 80: 28 KB/sec 2 KB/sec 30 KB/sec 500
Port: 80: 12 KB/sec 1 KB/sec 13 KB/sec 500
Port: 443: 412 KB/sec 16 KB/sec 436 KB/sec 500
Port: 443: 272 KB/sec 10 KB/sec 287 KB/sec 500
Port: 7255: 406 KB/sec 15 KB/sec 430 KB/sec 500
Port: 7255: 21 KB/sec 1 KB/sec 23 KB/sec 500
Port: 7003: 16 KB/sec 1 KB/sec 17 KB/sec 500
Port: 7003: 132 KB/sec 5 KB/sec 139 KB/sec 500
Port: 7202: 402 KB/sec 15 KB/sec 426 KB/sec 500
Port: 7202: 15 KB/sec 1 KB/sec 16 KB/sec 500
Port: 7499: 14 KB/sec 1 KB/sec 15 KB/sec 500
Port: 7499: 43 KB/sec 1 KB/sec 45 KB/sec 500
Port: 80: 60 KB/sec 3 KB/sec 64 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
OK this is what I got for "pathping patchserver.crypticstudios.com" ... it's not like I have anything better to do like pelt snowmen with snowballs
over a maximum of 30 hops:
0 GaryLi-PC.gateway.2wire.net [192.168.1.65]
1 192.168.1.254
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GaryLi-PC.gateway.2wire.net [192.168.1.65]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0%
Supplemental information:
All the game servers on http://www.mmoserverstatus.com/star_trek_online are working. Sometimes there is no warning, just sudden d/c. Other times Server Not Responding pops up and it disconnects after a while. Sector space seems to be a little bit more stable than ground maps.
It happened about 6-7 times within 3-4 minutes and about 10-12 times yesterday over the course of the day.
They really need to fix this.
Here's what I did:
That was it. Both chars worked again, no SNRs in two hours of gameplay!
If I use the proxy, I cant connect at all if its the eu1 proxy. The eu2 proxy works fine though; No disconnects, no lag, no nothing. It just works.
Seems like Cryptic should take a look at the eu1 proxy?