im getting quite annoyed with this... every time i try to play, the server crashes. wanted to play all day but havent been able to
get your TRIBBLE together Cryptic because people are getting right annoyed and your gonna start losing paying customers. im almost ready to un-install the game and never play it again!!!
I like it how they said "stay constructive" when basically everybody on the forums that is a player has no idea how to help with whatever is going on at all.
Unless you mean for me to build something with the various things I have, but that monstrosity would end up being a large lump of duct tape in the end.
I only talk about what I experience here in these threads in STO forums and if you ever say anything negative, you are a troll or a "******" like you guys like to say because you think it is funny to make fun of people with mental of physical handicaps. It's funny how everyone shouts TROLL or ******, god forbid you ever have negative experiences with STO
im getting quite annoyed with this... every time i try to play, the server crashes. wanted to play all day but havent been able to
get your TRIBBLE together Cryptic because people are getting right annoyed and your gonna start losing paying customers. im almost ready to un-install the game and never play it again!!!
Every time you try to play it happens? So it was your fault! :P
Network Admin Han Solo: Uh, everything's under control. Situation normal.
Community Manager BranFlakes: What happened?
Han Solo: [getting nervous] Uh, we had a slight equipment malfunction, but uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?
BranFlakes: Will we have the game back up soon?
Han Solo: Uh, uh... negative, negative. We had a data leak here now. Give us a few minutes to lock it down. Large leak, very dangerous.
BranFlakes: Who is this? What's your employee number?
Han Solo: Uh...
[Han shoots the intercom]
Han Solo: [muttering] Boring conversation, anyway. LUKE! IT'S THE COMPANY!
i'm not trolling actually, but dont care if it is taken that way, I really feel people like that, thinking playing a game is a grind or work are absolutely pathetic, I do not care their age they have the mind of a child. This is entertainment = fun , if your not having fun do something else, but to call it work or complain it is a hard grind or no to much effort. I pity them and hate them, they are the type that drag the world down.
As such, it is plenty obvious that the network is actually doing fine, and the fact that the response on the port is a flat out CONNECTION REFUSED indicates that the game daemon is simply DOWN.
Pretty solid investigative work. CONNECTION REFUSED means only one thing: that the server has been reached just fine, but that nothing is listening on the port in question (aka, game daemon crashed).
A quick ping test reveals the obvious falsity of this claim of "network issues". I have pinged all of the servers of the game. They DO, in fact, respond to pings, and what's more, those response times have never been better, perhaps because no one is actually on anymore.
As such, it is plenty obvious that the network is actually doing fine, and the fact that the response on the port is a flat out CONNECTION REFUSED indicates that the game daemon is simply DOWN.
This is NOT a network issue, the server program has CRASHED. If it were a network issue, I would be seeing terrible pings and connections not getting a response at all, not a prompt response from the server indicating it is not serving.
What about the login server? Packet testing will give you a limited view of a networks status. I've seen networks respond to ping in typical fashion but when subjected to real traffic it's a different story. Not saying this is what's going on, there are lots of possibilities.
Network Admin Han Solo: Uh, everything's under control. Situation normal.
Community Manager BranFlakes: What happened?
Han Solo: [getting nervous] Uh, we had a slight equipment malfunction, but uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?
BranFlakes: Will we have the game back up soon?
Han Solo: Uh, uh... negative, negative. We had a data leak here now. Give us a few minutes to lock it down. Large leak, very dangerous.
BranFlakes: Who is this? What's your employee number?
Han Solo: Uh...
[Han shoots the intercom]
Han Solo: [muttering] Boring conversation, anyway. LUKE! IT'S THE COMPANY!
Funny trying to change the subject when it's the worst anniversary ever and everyone knows it
The server crashed today. The server always crashes. What's the big deal? What makes today's crash any different from the 100 other crashes over the last 4 years; most of which have come on major updates?
You're acting like Cryptic attacked you because they crashed the server. It's just a crash. It's not a personal assault on you in any way. In a couple of days everything will be patched and you'll never even remember this day existed. Really.
It's not a traffic issue. They didn't fully test the patch and that is the problem.
I think you all missed my sarcasm. pushes up glasses See, the joke I was going for was that there was a causal relationship between this player trying to play and the server crashing. Thus, I suggested he not play, thereby keeping the servers running and allowing the rest of us to play.
I had enough with this game today... Server down again, I couldn't grind any of my stuff including Dilithium, fleet marks and do the daily today for the special..
Have you guys thought about extending the Tuvok mission? cause today is a "waste" day that we could not even log on and claim reward (Q-mendations)...
Content and testing isn't the problem here... it's network related. If it were content you would at least get to the login server and then get bumped after it tries to place you on the map. Instead you timeout trying to reach the login server.
No, it is not. You're not actually getting a timeout trying to reach the login server, that's just the behavior of the client when it fails to get a connection.
What is ACTUALLY happening is that the client is repeatedly attempting to open a connection to the login server, and getting a Connection Refused TCP-RST, meaning nothing is listening on that port and the server is returning an explicit response to that effect.
The client, not programmed to process this particular response, just treats it the same as any kind of failure and repeatedly tries again until its own internal clock indicates it should give up.
This is readily apparent if you manually attempt to connect to the same IP and Port that the client is attempting to:
All network diagnostics indicate that the network is FINE. If it were truly a network issue, you would get very slow responses or high packetloss on pings/traceroutes. Even if it was an internal network issue, you would still get a connection from the front-end server, followed by a total absence of meaningful response from the backend (this doesn't necessarily indicate that it truly is a network issue, but it makes it POSSIBLE that this is true).
Instead, however, we get immediate flat refusal. The network is fine. The game has crashed. Now, I'm entirely understanding of the fact that they have no QA department and rush these things out on a deadline.
Comments
Loooooooool
you wouldn't be the first.
"He"? You mean the other post? Oh, OK. I thought he meant me.
Unless you mean for me to build something with the various things I have, but that monstrosity would end up being a large lump of duct tape in the end.
Dude, just stop trying to play. Then the server won't crash.
http://www.youtube.com/watch?v=ERCUDmKHLoQ
sorry man i gotta disagree when not buggy sto is the shiznit
Every time you try to play it happens? So it was your fault! :P
Not cool, tacofangs!
Community Manager BranFlakes: What happened?
Han Solo: [getting nervous] Uh, we had a slight equipment malfunction, but uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?
BranFlakes: Will we have the game back up soon?
Han Solo: Uh, uh... negative, negative. We had a data leak here now. Give us a few minutes to lock it down. Large leak, very dangerous.
BranFlakes: Who is this? What's your employee number?
Han Solo: Uh...
[Han shoots the intercom]
Han Solo: [muttering] Boring conversation, anyway. LUKE! IT'S THE COMPANY!
It's not a traffic issue. They didn't fully test the patch(again this year) and that is the problem.
I hope D'angelo was serious about fixes because this would be the first thing to stop from happening. It's easy to do.
Pretty solid investigative work. CONNECTION REFUSED means only one thing: that the server has been reached just fine, but that nothing is listening on the port in question (aka, game daemon crashed).
Test your might! http://www.youtube.com/watch?v=gbcGX9zO1u8
What about the login server? Packet testing will give you a limited view of a networks status. I've seen networks respond to ping in typical fashion but when subjected to real traffic it's a different story. Not saying this is what's going on, there are lots of possibilities.
I've got to admit, I don't normally like hamsters, but that one was CUTE.
lol
LMAO Ahaahahahhahaha!
http://www.vice.com/read/online-gaming-is-south-koreas-most-popular-drug
You're acting like Cryptic attacked you because they crashed the server. It's just a crash. It's not a personal assault on you in any way. In a couple of days everything will be patched and you'll never even remember this day existed. Really.
I think you all missed my sarcasm. pushes up glasses See, the joke I was going for was that there was a causal relationship between this player trying to play and the server crashing. Thus, I suggested he not play, thereby keeping the servers running and allowing the rest of us to play.
Have you guys thought about extending the Tuvok mission? cause today is a "waste" day that we could not even log on and claim reward (Q-mendations)...
What is ACTUALLY happening is that the client is repeatedly attempting to open a connection to the login server, and getting a Connection Refused TCP-RST, meaning nothing is listening on that port and the server is returning an explicit response to that effect.
The client, not programmed to process this particular response, just treats it the same as any kind of failure and repeatedly tries again until its own internal clock indicates it should give up.
This is readily apparent if you manually attempt to connect to the same IP and Port that the client is attempting to:
~> telnet 208.95.184.129 7422
Trying 208.95.184.129...
telnet: connect to address 208.95.184.129: Connection refused
All network diagnostics indicate that the network is FINE. If it were truly a network issue, you would get very slow responses or high packetloss on pings/traceroutes. Even if it was an internal network issue, you would still get a connection from the front-end server, followed by a total absence of meaningful response from the backend (this doesn't necessarily indicate that it truly is a network issue, but it makes it POSSIBLE that this is true).
Instead, however, we get immediate flat refusal. The network is fine. The game has crashed. Now, I'm entirely understanding of the fact that they have no QA department and rush these things out on a deadline.
But I don't appreciate being lied to.