Forum

Results 1 to 5 of 5
  1. #1
    Join Date
    December 2009
    Location
    Taiwan
    Posts
    313

    Same old problem, exist since Beta 14 - Server Connection Lost (with temp fix)

    First of all, yes, it still haunts me, (and probably alot of users too)

    I'm sure alot of you encounters this kind of issue

    Note: the [TSServerClient] represents the client that is installed on the server (aka client + server are on same box), where as [OtherTSClient] represents clients from outside of the network mask.

    - Sequence Log Start -

    Phase 1 - (initial self test)

    [Server] Starts up server on port AAAA, everything a-ok.

    [TSServerClient] Establishing connection to server with IP 127.0.0.1, on port AAAA
    [Server] Saw the incoming connection from [TSServerClient]
    [TSServerClient] Connected and all functioning. Disconnecting.
    (loopback check, functioning)

    [Server] Saw [TSServerClient] disconnectes from the server.
    [TSServerClient] Establishing connection to server with server.wan.ip.address, on port AAAA
    [Server] Saw the incoming connection from [TSServerClient]
    (wan IP check, functioning)

    [TSServerClient] Connected and all functioning. Tells [OtherTSClient] that his server is running

    Phase 2 - (endless connection lost)

    [OtherTSClient] Establishing connection to server with server.wan.ip.address, on port AAAA
    [Server] Saw the incoming connection from [OtherTSClient]
    [TSServerClient] Saw [OtherTSClient] has entered to the default channel.
    [OtherTSClient] is actually still waiting to connect to the server
    (screen is still blank on [OtherTSClient])

    [Server] connection lost with [OtherTSClient]
    [TSServerClient] Saw [OtherTSClient] has quit the server with (connection lost) error message.
    [OtherTSClient] recieved an error message saying "Unable to connect to server"

    (the above instructions were repeated many times at different time intervals, and with many other people, and no one was able to connect successfully)

    [TSServerClient] and [OtherTSClient] were totally annoyed.

    Phase 3 - (temp fix)

    [TSServerClient] logs into [server]'s ServerQuery via telnet
    [Server] accepted the login from serveradmin
    [TSServerClient] changes [server]'s virtual server port to BBBB
    [Server] acknoledges the change
    [TSServerClient] shuts off the [server]'s process and restarts
    [Server] restarts with the new settings.

    [Server] Starts up server on port BBBB, everything a-ok.
    [TSServerClient] Establishing connection to server with IP 127.0.0.1, on port BBBB
    [Server] Saw the incoming connection from [TSServerClient]
    [TSServerClient] Connected and all functioning. Disconnecting.
    [Server] Saw [TSServerClient] disconnectes from the server.
    [TSServerClient] Establishing connection to server with server.wan.ip.address, on port BBBB
    [Server] Saw the incoming connection from [TSServerClient]
    [TSServerClient] Connected and all functioning. Tells [OtherTSClient] that his server is running

    [OtherTSClient] Establishing connection to server with server.wan.ip.address, on port BBBB
    [Server] Saw the incoming connection from [OtherTSClient]
    [TSServerClient] Saw [OtherTSClient] has entered to the default channel.
    [OtherTSClient] finally saw the content of the server, connected and all functioning

    - Sequence Log Ends -

    So, here's some observations

    1. The temp fix effect works as fast as soon first sign of multiple incident of connection lost was sighted
    - Port AAAA was originally functioning until some random unknown issue happens, causing the mass connection lost, and quickly (or whenever) switching to port BBBB will immidiately resolve this issue

    2. clients running under same host masks will have no problem connecting to the server, but any one that doesn't will.

    3. The previously stated port AAAA was orignally functioning, nothing was blocking it and such.

    4. Appearently this happens alot on server running on WINDOWS, and when the owner just want a quick reload of the server (aka log in the server with serverquery, shuts the server down with serverprocess stop, and executes the server again) after the server has been running for a while.

    This error is somewhat easily reproduced with following factors:
    - the server is running on windows
    - Server that has been running for a while (like few days +)
    - Force shut down the server process (via taskkill / task manager / power loss)
    - Networking issue (like unplug network cable/router)
    - shut down and restarts server too many times (and quickly?) in a short period of time
    - shuts off the server while there are still users in it.

    So. this does sounds like an networking issue, but what troubles me is that what EXACTLY is the issue here?

    My assumptions was that it was the server's ack reply was not recieved by the client (or the packet got dropped/blocked somewhere)

    But, hey, let me know if you are up for some testing, because my server is currently under this state. (yet again)

    === attached trace log ===

    Tracing route to my.tsserver.com [my.ts3.svr.ip]
    over a maximum of 30 hops:

    1 32 ms 24 ms 24 ms h254.s98.ts.hinet.net [168.95.98.254]
    2 12 ms 12 ms 12 ms PHMK-3501.hinet.net [168.95.176.50]
    3 16 ms 17 ms 17 ms SKC1-3011.hinet.net [220.128.24.82]
    4 16 ms 15 ms 15 ms TNCD-3101.hinet.net [220.128.26.33]
    5 16 ms 16 ms 15 ms TNCD-3301.hinet.net [220.128.29.93]
    6 16 ms 16 ms 15 ms 211-20-206-53.HINET-IP.hinet.net [211.20.206.53]
    7 18 ms 16 ms 16 ms my.building.gateway.ip
    8 22 ms 16 ms 17 ms my.ts3.svr.ip

  2. #2
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,192
    Hi,

    it is hard to guess at these problems, but I believe this is probably a router problem. Some routers have very weird (broken!) rules concerning blocking of UDP "spam", and sometimes it happens that the router thinks the packets coming for the TS3 server constitute such spam, and starts to drop them (or some of them). This of course leads to connection problems.

    We had a similar problem with our router too, we didn't host a server but when we connected to a server and this server went offline, the auto-reconnect packets tripped up the router and it blocked us for spamming - so even when the server came back online the client would not reconnect (because the router was blocking the packets). Connecting in a "new tab", or restarting the TS3 client fixed the problem - since that made the TS3 Client use a new Port.

  3. #3
    Join Date
    December 2009
    Location
    Taiwan
    Posts
    313
    Quote Originally Posted by Peter View Post
    Connecting in a "new tab", or restarting the TS3 client fixed the problem - since that made the TS3 Client use a new Port.
    Nope, that's not it. I'm sure many definetly have tried closing their client&server multiple times just to try to connect, but that's not the problem

  4. #4
    Join Date
    January 2010
    Location
    Germany
    Posts
    2,029
    not in case of the Server no, because Server uses the same Ports again.

    The Problem is that some Firewall decided to drop packets on the Serverport which is why the Clients drop and also why another Serverport fixes the issue temporarily until the firewall decides that the new Port is getting flooded too.

  5. #5
    Join Date
    December 2009
    Location
    Taiwan
    Posts
    313
    but what if there is no firewall AT ALL? Because that's what happens here.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Rejected] Specify DNS hostname connection default channel similar to temp passwords system.
    By Morthawt in forum Suggestions and Feedback
    Replies: 3
    Last Post: July 8th, 2013, 08:17 AM
  2. PROBLEM! - connection lost
    By Smietana in forum Linux / FreeBSD
    Replies: 8
    Last Post: January 30th, 2012, 09:46 AM
  3. Help Please!! connection lost problem!!
    By Magnum in forum General Questions
    Replies: 1
    Last Post: September 12th, 2011, 08:19 PM
  4. [Resolved] Current Beta using 25% CPU, increasing CPU temp by 12 degrees
    By xyster in forum Bug Reports [EN/DE]
    Replies: 3
    Last Post: March 4th, 2011, 06:45 PM
  5. Failed to connect to server !!! problem exist
    By Rafalsky in forum Windows
    Replies: 12
    Last Post: July 28th, 2010, 06:53 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •