Where, specifically, is it hanging? About 2 hours ago I was kicked off and have been unable to log in since; for me, it keeps hanging at the character selection screen.
This is a technical description of the precise nature of the failure, not just "what you see on the screen". That particular server returns a TCP connection refused response to any connection attempt to the relevant game ports. It's simply not listening, and thus what you'll see in-game is that it just hangs there, repeatedly banging on the port despite receiving an explicit refused response, because the game does not apparently actually process the response and just mindlessly retries the same server over and over instead of picking a different one.
As of this writing, that particular server is still down.
This is a technical description of the precise nature of the failure, not just "what you see on the screen". That particular server returns a TCP connection refused response to any connection attempt to the relevant game ports. It's simply not listening, and thus what you'll see in-game is that it just hangs there, repeatedly banging on the port despite receiving an explicit refused response, because the game does not apparently actually process the response and just mindlessly retries the same server over and over instead of picking a different one.
As of this writing, that particular server is still down.
Why not instead just modify the local config to insure this server is never accessed, thus problem is solved!
Why not instead just modify the local config to insure this server is never accessed, thus problem is solved!
This would be difficult to do, as no doubt a 'round-robin DNS' scheme (where multiple servers are listed under the same host name for load sharing) is being used. The Server that your network connection reaches is basically a TRIBBLE shoot chosen by your network DNS service.
Comments
My Foundry missions | My STO Wiki page | My Twitter home page
As of this writing, that particular server is still down.
Why not instead just modify the local config to insure this server is never accessed, thus problem is solved!
This would be difficult to do, as no doubt a 'round-robin DNS' scheme (where multiple servers are listed under the same host name for load sharing) is being used. The Server that your network connection reaches is basically a TRIBBLE shoot chosen by your network DNS service.