Results 1 to 3 of 3

Thread: Unable to rejoin game after Internet session disconnect (Dynamic I.P)

  1. #1
    Basic Member
    Join Date
    Sep 2013
    Posts
    70

    Unable to rejoin game after Internet session disconnect (Dynamic I.P)

    I have noticed If my Internet connection goes down mid game I am unable to rejoin the game once my connection has been re-established.

    The reason for this is because my ISP gives me a new I.P address which is not accepted when I try to rejoin the game because its different than before.

    If my game client was to crash for any reason but my net connection remains fine then I can always rejoin without issues because my I.P has not changed.

    Its only when my net goes down this happens which results in my account receiving an ABANDON.

    Will this issue ever be fixed as its unrealistic to assume residential household internet connections use Static I.P's as generally business use those and residential use Dynamic.

    There is absolutely no reason why a new I.P address cant rejoin.




    Console Log below:


    Connection problem (103.10.125.71:27051), requesting full update

    Server connection timed out.
    CHLClient::OnServerConnectionTimedOut Address: 103.10.125.71:27051
    NotifyClientSignon: 0
    NotifyClientSignon: 1
    Connecting to public(103.10.125.71:27051) ...
    3863.530: Sending UDP connect to public IP 103.10.125.71:27051
    CClientSteamContext OnSteamServersDisconnected logged on = 0
    Retrying public(103.10.125.71:27051) ...
    3869.547: Sending UDP connect to public IP 103.10.125.71:27051
    CClientSteamContext OnSteamServersConnected logged on = 1
    Current item schema is up-to-date with version D6612FC2.
    Retrying public(103.10.125.71:27051) ...
    3875.562: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3881.567: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3887.581: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3893.614: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3899.647: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3905.648: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3911.681: Sending UDP connect to public IP 103.10.125.71:27051
    Retrying public(103.10.125.71:27051) ...
    3917.714: Sending UDP connect to public IP 103.10.125.71:27051

  2. #2
    Basic Member
    Join Date
    Sep 2013
    Posts
    70
    Does anybody have any insight as to whether or not this is planned to be fixed?

  3. #3
    Basic Member
    Join Date
    Sep 2013
    Posts
    70
    Quote Originally Posted by blaity View Post
    Does anybody have any insight as to whether or not this is planned to be fixed?
    ^

Posting Permissions

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