View Poll Results: Are you able to log into Stage 2 without problems?

Voters
4. You may not vote on this poll
  • Yes

    0 0%
  • No

    4 100.00%
Results 1 to 17 of 17

Thread: Server login issues (with technical data)

  1. #1
    Join Date
    Jan 2017
    Posts
    13

    Server login issues (with technical data)

    TL;DR version:
    It appears the problem with people not being able to connect is related to the game servers located at 4v1game.net. From the looks of it, it might be a DNS issue that needs to be resolved by the developers or possibly a caching service has dumped them & Turtle Rock Studios just hasn't realized it yet. However after trying to force the IPs to be assigned correctly by editing the hosts file, it appears to be a server issue instead...

    ================================================== =============

    Extended version:
    I've been having the same problem for over a month now. Less than a week ago, I decided it was time to record a video of the problem:
    https://youtu.be/hc9ZhmpAwWI

    2 days ago, I started diagnosing the problem within a period of an hour & a half, I finally managed to connect after recycling the power on my modem, but it didn't work last night & I night. Within the time I had fought with it for over an hour & a half, I change my review of the game to not recommended & added additional information about the connection issues as this was the reason for the change in recommendation. It was within this time that I turned on monitoring of network traffic of Evolve.exe through my firewall to try & diagnose the problem. I also attempted to link my Steam account to my 2K account, but when I realized that wasn't helping, I unlinked it today before I tried to diagnose it again.

    Yesterday I didn't even manage to get logged into the game & gain the Daily Sign In Reward until about 10 minutes before the cut off of that reward today (must've worked on the issue upwards of 6 hours).

    I created a forum account today to get the technical details out to the developers in hope they would use them to fix this ongoing problem. They added Gold Keys to the game to gain money from it after they changed it to F2P on PC, so I'm not sure how they think they're going to continue making money on a game that players are rarely able to succeed in connecting to...

    ------------------------------------------------------------------------------------------------------------

    Technical details
    This is an extensive log of what I have done through the command prompt to locate the problem using logs from my firewall:

    Firewall logs show IP 52.52.80.127 (dsx-1-b.4v1game.net) accessed over port 443 when starting the game:
    • Command
      Code:
      ping dsx-1-b.4v1game.net
      Results
      Code:
      Pinging dsx-1-b.4v1game.net [52.52.80.127] with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.
      
      Ping statistics for 52.52.80.127:
          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
      When I did this test early this morning, the IP from ping results did not match the IP from firewall logs
    • Command
      Code:
      tracert dsx-1-b.4v1game.net
      Results
      Code:
      Tracing route to dsx-1-b.4v1game.net [52.52.80.127] over a maximum of 30 hops:
      
        1    <1 ms    <1 ms    <1 ms  WonderGamer [192.168.1.1]
        2     4 ms     4 ms     4 ms  10.0.0.1
        3    11 ms    19 ms    14 ms  96.120.96.5
        4    47 ms    15 ms    19 ms  te-0-5-0-6-sur03.saltlakecity.ut.utah.comcast.net [68.87.171.85]
        5    14 ms    18 ms    14 ms  be-1-ar01.saltlakecity.ut.utah.comcast.net [162.151.49.133]
        6    28 ms    34 ms    25 ms  be-33660-cr02.denver.co.ibone.comcast.net [68.86.90.225]
        7    29 ms    29 ms    29 ms  be-11719-cr01.1601milehigh.co.ibone.comcast.net [68.86.86.78]
        8    39 ms    38 ms    39 ms  be-10919-cr01.sunnyvale.ca.ibone.comcast.net [68.86.85.153]
        9    43 ms    39 ms    39 ms  hu-0-13-0-0-pe02.529bryant.ca.ibone.comcast.net [68.86.86.94]
       10    38 ms    39 ms    40 ms  as16509-1-c.529bryant.ca.ibone.comcast.net [50.242.148.82]
       11    58 ms    59 ms    54 ms  54.240.243.132
       12    43 ms    44 ms    60 ms  54.240.243.147
       13    44 ms    44 ms    44 ms  72.21.222.19
       14     *        *        *     Request timed out.
       15     *        *        *     Request timed out.
       16     *        *        *     Request timed out.
       17     *        *        *     Request timed out.
       18     *        *        *     Request timed out.
       19     *        *        *     Request timed out.
       20     *        *        *     Request timed out.
       21     *        *        *     Request timed out.
       22     *        *        *     Request timed out.
       23     *        *        *     Request timed out.
       24     *        *        *     Request timed out.
       25     *        *        *     Request timed out.
       26     *        *        *     Request timed out.
       27     *        *        *     Request timed out.
       28     *        *        *     Request timed out.
       29     *        *        *     Request timed out.
       30     *        *        *     Request timed out.
      
      Trace complete.
    • Command
      Code:
      ping 52.52.80.127
      Results
      Code:
      Pinging 52.52.80.127 with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.
      
      Ping statistics for 52.52.80.127:
          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    • Command
      Code:
      tracert 52.52.80.127
      Results
      Code:
      Tracing route to ec2-52-52-80-127.us-west-1.compute.amazonaws.com [52.52.80.127]
      
      over a maximum of 30 hops:
      
        1    <1 ms    <1 ms    <1 ms  WonderGamer [192.168.1.1]
        2     1 ms     4 ms     4 ms  10.0.0.1
        3    13 ms    14 ms    11 ms  96.120.96.5
        4    15 ms    14 ms    14 ms  te-0-5-0-6-sur03.saltlakecity.ut.utah.comcast.net [68.87.171.85]
        5    13 ms    16 ms    12 ms  be-1-ar01.saltlakecity.ut.utah.comcast.net [162.151.49.133]
        6    26 ms    29 ms    30 ms  be-33660-cr02.denver.co.ibone.comcast.net [68.86.90.225]
        7    29 ms    29 ms    30 ms  be-11719-cr01.1601milehigh.co.ibone.comcast.net [68.86.86.78]
        8    40 ms    40 ms    39 ms  be-10919-cr01.sunnyvale.ca.ibone.comcast.net [68.86.85.153]
        9    43 ms    44 ms    44 ms  hu-0-13-0-0-pe02.529bryant.ca.ibone.comcast.net [68.86.86.94]
       10    44 ms    44 ms    65 ms  as16509-1-c.529bryant.ca.ibone.comcast.net [50.242.148.82]
       11    58 ms    60 ms    49 ms  54.240.243.132
       12    43 ms    44 ms    44 ms  54.240.243.147
       13    43 ms    44 ms    45 ms  72.21.222.19
       14     *        *        *     Request timed out.
       15     *        *        *     Request timed out.
       16     *        *        *     Request timed out.
       17     *        *        *     Request timed out.
       18     *        *        *     Request timed out.
       19     *        *        *     Request timed out.
       20     *        *        *     Request timed out.
       21     *        *        *     Request timed out.
       22     *        *        *     Request timed out.
       23     *        *        *     Request timed out.
       24     *        *        *     Request timed out.
       25     *        *        *     Request timed out.
       26     *        *        *     Request timed out.
       27     *        *        *     Request timed out.
       28     *        *        *     Request timed out.
       29     *        *        *     Request timed out.
       30     *        *        *     Request timed out.
      
      Trace complete.
      Notice domain from tracert results does not match firewall logs

    Second firewall log after starting the game shows IP 205.251.215.108 (89oy3rnjqlo2u849.4v1game.net) accessed over port 443. From what I've seen, IPs can differ between login attempts, as well an random variables defining sub-domains (as seen in the domain here), so I won't get into extensive testing on this one.

    Firewall logs show IP 52.207.193.204 (profile-prd-1-9.4v1game.net) accessed over port 443 when trying to force login by clicking on Play:
    • Command
      Code:
      ping profile-prd-1-9.4v1game.net
      Results
      Code:
      Pinging profile-prd-1-9.4v1game.net [52.22.231.49] with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.
      
      Ping statistics for 52.22.231.49:
          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
      Notice IP from ping results does not match firewall logs
    • Command
      Code:
      tracert profile-prd-1-9.4v1game.net
      Results
      Code:
      Tracing route to profile-prd-1-9.4v1game.net [52.207.193.204] over a maximum of 30 hops:
      
        1    <1 ms    <1 ms    <1 ms  WonderGamer [192.168.1.1]
        2     6 ms     4 ms     1 ms  10.0.0.1
        3    12 ms    14 ms    14 ms  96.120.96.5
        4    13 ms    13 ms    15 ms  te-0-5-0-6-sur03.saltlakecity.ut.utah.comcast.net [68.87.171.85]
        5    14 ms    14 ms    19 ms  be-1-ar01.saltlakecity.ut.utah.comcast.net [162.151.49.133]
        6    28 ms    32 ms    28 ms  be-33660-cr02.denver.co.ibone.comcast.net [68.86.90.225]
        7    42 ms    44 ms    44 ms  be-11724-cr02.dallas.tx.ibone.comcast.net [68.86.84.230]
        8    39 ms    39 ms    39 ms  be-12441-pe01.1950stemmons.tx.ibone.comcast.net [68.86.89.206]
        9    38 ms    39 ms    39 ms  50.242.148.102
       10     *        *        *     Request timed out.
       11     *        *        *     Request timed out.
       12     *        *        *     Request timed out.
       13     *        *        *     Request timed out.
       14     *        *        *     Request timed out.
       15    71 ms    75 ms    74 ms  54.239.110.247
       16    72 ms    71 ms    73 ms  54.239.109.183
       17    69 ms    82 ms    84 ms  205.251.245.121
       18     *        *        *     Request timed out.
       19     *        *        *     Request timed out.
       20     *        *        *     Request timed out.
       21     *        *        *     Request timed out.
       22     *        *        *     Request timed out.
       23     *        *        *     Request timed out.
       24     *        *        *     Request timed out.
       25     *        *        *     Request timed out.
       26     *        *        *     Request timed out.
       27     *        *        *     Request timed out.
       28     *        *        *     Request timed out.
       29     *        *        *     Request timed out.
       30     *        *        *     Request timed out.
      
      Trace complete.
    • Command
      Code:
      ping 52.207.193.204
      Results
      Code:
      Pinging 52.207.193.204 with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.
      
      Ping statistics for 52.207.193.204:
          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    • Command
      Code:
      tracert 52.207.193.204
    • Results
      Code:
      Tracing route to ec2-52-207-193-204.compute-1.amazonaws.com [52.207.193.204] over a maximum of 30 hops:
      
        1    <1 ms    <1 ms    <1 ms  WonderGamer [192.168.1.1]
        2     4 ms     4 ms     1 ms  10.0.0.1
        3    14 ms    14 ms    14 ms  96.120.96.5
        4    19 ms    19 ms    14 ms  te-0-5-0-6-sur03.saltlakecity.ut.utah.comcast.net [68.87.171.85]
        5    18 ms    19 ms    19 ms  be-1-ar01.saltlakecity.ut.utah.comcast.net [162.151.49.133]
        6    28 ms    29 ms    29 ms  be-33660-cr02.denver.co.ibone.comcast.net [68.86.90.225]
        7    59 ms    44 ms    44 ms  be-11724-cr02.dallas.tx.ibone.comcast.net [68.86.84.230]
        8    39 ms    39 ms    49 ms  be-12441-pe01.1950stemmons.tx.ibone.comcast.net [68.86.89.206]
        9    43 ms    39 ms    39 ms  50.242.148.102
       10     *        *        *     Request timed out.
       11     *        *        *     Request timed out.
       12     *        *        *     Request timed out.
       13     *        *        *     Request timed out.
       14     *        *        *     Request timed out.
       15    72 ms    84 ms    74 ms  54.239.110.247
       16    74 ms    84 ms    74 ms  54.239.109.183
       17    72 ms    76 ms    72 ms  205.251.245.121
       18     *        *        *     Request timed out.
       19     *        *        *     Request timed out.
       20     *        *        *     Request timed out.
       21     *        *        *     Request timed out.
       22     *        *        *     Request timed out.
       23     *        *        *     Request timed out.
       24     *        *        *     Request timed out.
       25     *        *        *     Request timed out.
       26     *        *        *     Request timed out.
       27     *        *        *     Request timed out.
       28     *        *        *     Request timed out.
       29     *        *        *     Request timed out.
       30     *        *        *     Request timed out.
      
      Trace complete.
      Notice domain from tracert results does not match firewall logs

    Firewall logs show IP 52.201.98.70 (prd-news-feed-v1.4v1game.net) accessed over port 443 when exiting the game:
    • Command
      Code:
      ping prd-news-feed-v1.4v1game.net
      Results
      Code:
      Pinging news-feed-service-lb-852285383.us-east-1.elb.amazonaws.com [52.44.225.81] with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.
      
      Ping statistics for 52.44.225.81:
          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
      Notice IP from ping results does not match IP from firewall logs
    • Command
      Code:
      tracert prd-news-feed-v1.4v1game.net
      Results
      Code:
      Tracing route to news-feed-service-lb-852285383.us-east-1.elb.amazonaws.com [52.44.225.81] over a maximum of 30 hops:
      
        1    <1 ms    <1 ms    <1 ms  WonderGamer [192.168.1.1]
        2     3 ms     4 ms     4 ms  10.0.0.1
        3    14 ms    13 ms    16 ms  96.120.96.5
        4    11 ms    14 ms    14 ms  te-0-5-0-6-sur03.saltlakecity.ut.utah.comcast.net [68.87.171.85]
        5    14 ms    14 ms    14 ms  be-1-ar01.saltlakecity.ut.utah.comcast.net [162.151.49.133]
        6    29 ms    29 ms    30 ms  be-33660-cr02.denver.co.ibone.comcast.net [68.86.90.225]
        7    45 ms    44 ms    44 ms  be-11724-cr02.dallas.tx.ibone.comcast.net [68.86.84.230]
        8    43 ms    39 ms    39 ms  be-12495-pe03.1950stemmons.tx.ibone.comcast.net [68.86.85.194]
        9    39 ms    39 ms    39 ms  66.208.233.34
       10     *        *        *     Request timed out.
       11     *        *        *     Request timed out.
       12     *        *        *     Request timed out.
       13     *        *        *     Request timed out.
       14     *        *        *     Request timed out.
       15   103 ms   104 ms    94 ms  54.239.110.217
       16    71 ms    74 ms    74 ms  54.239.111.73
       17    72 ms    75 ms    74 ms  205.251.244.219
       18     *        *        *     Request timed out.
       19     *        *        *     Request timed out.
       20     *        *        *     Request timed out.
       21     *        *        *     Request timed out.
       22     *        *        *     Request timed out.
       23     *        *        *     Request timed out.
       24     *        *        *     Request timed out.
       25     *        *        *     Request timed out.
       26     *        *        *     Request timed out.
       27     *        *        *     Request timed out.
       28     *        *        *     Request timed out.
       29     *        *        *     Request timed out.
       30     *        *        *     Request timed out.
      
      Trace complete.
    • Command
      Code:
      ping 52.201.98.70
      Results
      Code:
      Pinging 52.201.98.70 with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.
      Request timed out.
      
      Ping statistics for 52.201.98.70:
          Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    • Command
      Code:
      tracert 52.201.98.70
      Results
      Code:
      Tracing route to ec2-52-201-98-70.compute-1.amazonaws.com [52.201.98.70]over a maximum of 30 hops:
      
        1    <1 ms    <1 ms    <1 ms  WonderGamer [192.168.1.1]
        2     3 ms     4 ms     4 ms  10.0.0.1
        3    11 ms    14 ms    15 ms  96.120.96.5
        4    14 ms    14 ms    14 ms  te-0-5-0-6-sur03.saltlakecity.ut.utah.comcast.net [68.87.171.85]
        5    18 ms    14 ms    24 ms  be-1-ar01.saltlakecity.ut.utah.comcast.net [162.151.49.133]
        6    29 ms    29 ms    29 ms  be-33660-cr02.denver.co.ibone.comcast.net [68.86.90.225]
        7    39 ms    39 ms    40 ms  be-11724-cr02.dallas.tx.ibone.comcast.net [68.86.84.230]
        8    38 ms    39 ms    44 ms  be-12495-pe03.1950stemmons.tx.ibone.comcast.net [68.86.85.194]
        9    40 ms    39 ms    38 ms  66.208.232.158
       10     *        *        *     Request timed out.
       11     *        *        *     Request timed out.
       12     *        *        *     Request timed out.
       13     *        *        *     Request timed out.
       14     *        *        *     Request timed out.
       15    75 ms    74 ms    89 ms  54.239.110.147
       16    71 ms    74 ms    74 ms  54.239.108.99
       17     *       75 ms    74 ms  205.251.245.121
       18     *        *        *     Request timed out.
       19     *        *        *     Request timed out.
       20     *        *        *     Request timed out.
       21     *        *        *     Request timed out.
       22     *        *        *     Request timed out.
       23     *        *        *     Request timed out.
       24     *        *        *     Request timed out.
       25     *        *        *     Request timed out.
       26     *        *        *     Request timed out.
       27     *        *        *     Request timed out.
       28     *        *        *     Request timed out.
       29     *        *        *     Request timed out.
       30     *        *        *     Request timed out.
      
      Trace complete.
      Notice domain from tracert results does not match firewall logs

    Second firewall log after exiting game shows IP 104.130.53.12 (evolve.hydra.agorangames.com) accessed over port 443. While the sub-domain can not be accessed over a web browser, the domain itself can & can be pinged, so I won't go into extensive testing here as this doesn't appear to be where the issue is.

    ================================================== ==============================================

    The following methods have already been attempted to fix this issue:
    • Verifying local cache of the game through Steam.
    • Disabled software firewall entirely while trying to connect.
    • Recycling the power on the modem; this worked once the first time I did it, but was very slow logging in & didn't work the next day when I tried it.
    • Clearing DNS cache using the following command at the command prompt:
      Code:
      ipconfig /flushdns
    • Deleting various configuration, cache & system files in the game folder (as stated by a user on the Steam forums after speaking to 2K support today); I had already attempted this with the configuration & cache files, but not the system files, however it did not work...
    • Forcing IP to DNS assignments by manually adding them into the hosts file (located in C:\Windows\System32\drivers\etc); if it was a DNS issue, this should have fixed it, however it didn't, so it looks to be a server issue that the developers need to fix.
    Last edited by WonderGamer; 03-08-2017 at 12:53 PM. Reason: Added steps already taken in an attempt to fix issue; problem now believed to a server issue, not DNS

  2. #2
    Join Date
    Oct 2016
    Posts
    12
    Hello. I suggest you also to post this on Steam forum. to have more visibility.

  3. #3
    Join Date
    Jan 2017
    Posts
    13
    Quote Originally Posted by StIwY View Post
    Hello. I suggest you also to post this on Steam forum. to have more visibility.
    There is a link leading here on there already; I posted there before I posted here, then updated with a link afterwards.
    Last edited by WonderGamer; 01-24-2017 at 07:25 PM.

  4. #4
    Join Date
    Jan 2017
    Posts
    13
    A shame that this issue is being ignored, so I'm going to show how much money I am out from purchasing this game (before it went F2P; so glad I hold onto all my online invoices) & why I won't be purchasing from the company anymore until the connection issue is fixed:

    12/27/2015
    • $27.19 - Evolve PC Monster Race pack
      • Evolve
      • Crow - Hunter (Trapper Class) DLC
      • Emit - Hunter (Medic Class) DLC
      • Evolve - Gorgon DLC
      • Evolve Founder DLC
      • Evolve Hunting Season 2 DLC
      • Evolve Evolve Season Pass DLC
      • Jack - Hunter (Trapper Class) DLC
      • Kala - Hunter (Support Class) DLC
      • Lennox - Hunter (Assault Class) DLC
      • PC Monster Race Skin Pack DLC
      • Slim - Hunter (Medic Class) DLC
      • Sunny - Hunter (Support Class) DLC
      • Torvald - Hunter (Assault Class) DLC

    1/03/2016
    • $4.99 - Evolve - Behemoth DLC
    • $2.49 - Assault Ragnarok Skin Pack DLC
    • $2.49 - Assault Sword Skin Pack DLC
    • $2.49 - Medic Phoenix Skin Pack DLC
    • $2.49 - Medic Valkyrie Skin Pack DLC
    • $2.49 - Medic Savior Skin Pack DLC
    • $2.49 - Trapper Bushman Skin Pack DLC
    • $2.49 - Trapper Blood Eagle Skin Pack DLC
    • $2.49 - Trapper Maneater Skin Pack DLC
    • $2.49 - Exterminator Weapon Skins Pack DLC
    • $3.49 - Wendigo Monster Skin Pack DLC
    • $2.49 - Support Tempest Skin Pack DLC
    • $2.49 - Support Nordita Skin Pack DLC
    • $2.49 - Support Leviathan Skin Pack DLC
    • $3.49 - Carnivore Monster Skin Pack DLC
    • $3.49 - Bog Monster Skin Pack DLC
    • $3.49 - Cosmic Monster Skin Pack DLC
    • $3.49 - Savage Monster Skin Pack DLC
    • $2.49 - Assault Night Hunter Skin Pack DLC
    • $2.49 - Trapper Night Hunter Skin Pack DLC
    • $2.49 - Support Night Hunter Skin Pack DLC
    • $2.49 - Medic Night Hunter Skin Pack DLC
    • $2.49 - Trapper Victory Skin Pack DLC
    • $2.49 - Medic Victory Skin Pack DLC
    • $2.49 - Support Victory Skin Pack DLC

    Total loss on this game, $96.94 without Gold Key purchases.

    EDIT: One user on the Steam forums is stating that he had to open a ticket with them get help in connecting by giving information from the command prompt, I would assume the same information I have provided here. I'll try the ticket method, but I really doubt that's going to fix the issue; I still don't intend on purchasing any further software here until the servers are stabilized...
    Last edited by WonderGamer; 01-26-2017 at 08:06 PM. Reason: Support ticket information added

  5. #5
    Join Date
    Mar 2014
    Posts
    12
    @WonderGamer:
    I appreciate the more detailed information you've provided here, and I hope it'll help someone on 2k's end look into the real problem. It's good to see that kind of effort, if nothing else so that we can continue to show that the community is interested in the game - if they just make it playable again.

    I also am with you in terms of how much was spent on the game - I got the PC monster race pack, among others. I continue to hold onto the hope that the back-end problem will get resolved, and people will be able to play the game as it is.

  6. #6
    Join Date
    Jan 2017
    Posts
    13
    2K support was contacted on the 26th, I received a response back on the 27th, asking for my Steam ID (SteamID64 if you're using steamid.io & requesting me to try deleting my Cache.m2k & Client.m2k files, restarting the game afterwards (something that was already attempted when the Steam user copies those directions to the Evolve forums on Steam). I gave them details on a better way to grab the Steam ID using the site previously mentioned (their steps apparently want you to go through the source code on a page, which will pose a problem in some web browsers) & again pointed them to this thread hoping they would use the information to attempt to fix the problem. According to the user on Steam, they were able to fix the issue after he provided them with some information from the command prompt, I would assume that would be the tracert reported I was in the middle of doing before that user even stated they were able to help him with the issue. I haven't heard from 2K since the 27th, so now I'm waiting to see if anything is going to be done, checking emails, this thread & the support ticket to see if anything positive comes out of it...
    Last edited by WonderGamer; 02-13-2017 at 04:39 PM.

  7. #7
    Join Date
    Jan 2017
    Posts
    13
    As of 1/29/2016 (in the middle of proofreading & correcting the response above) I appear to have been IP banned from these forums from my home IP address through the servers causing constant timeouts while attempting to access these forums; a full cutoff from the forums rather than a standard IP/account ban that would warrant an error message indicating this as being a ban. I was still able to access the forums using an anonymous proxy & using my neighbor's Xfinity wifi hotspot through my phone, which I only found out after making a comment on isitdownrightnow.com about the timing out. Take note that I was IP banned from the 2K forums for providing detailed information publicly that could have fixed the connection problems in Evolve were 2K to actually use it. 2K does not care about this game anymore, move on & stop paying for further 2K products if you have lost money put into this game, as I already intend on doing should the BBB complaint I intend on filing on 2/2/2017 (should I still not have access to the forums through my own connection; this is currently being posted through my neighbor's hotspot) not yield any results.
    Last edited by WonderGamer; 02-13-2017 at 04:42 PM.

  8. #8
    Join Date
    Mar 2014
    Posts
    12
    wait, what? O.o You were very detailed in your info, but nothing appears to be even legally gray area... wow. If you actually were IP banned, that's... a pretty crazy step to have taken. I dont know if we can get confirmation from any mods that that's happened, or what made them do it... wow.

  9. #9
    Join Date
    Jan 2017
    Posts
    13
    Currently I can only access the site thorugh a proxy, expecting to get banned again directly after I make this post.

  10. #10
    Join Date
    Jan 2017
    Posts
    13
    It appears to be automated when when posting an external link. To test this:

    steamid.io

  11. #11
    Join Date
    Jan 2017
    Posts
    13
    Seems to be a problem with Xfinity, I'll need to contact my ISP about it. Going to grab a tracert to the forums & give them the results; sorry for the post spam, but editing don't work through the proxy...

  12. #12
    Join Date
    Jan 2017
    Posts
    13
    Xfinity Technician (escalated tier) coming out on Saturday. I'll clean up th is mess of posts once I'm able to get the edit function to work (like I said, don't work through proxy). If I get a new modem, that will change my IP address; we'll see if posting to the forums after that makes me lose connection again...

  13. #13
    Join Date
    Jan 2017
    Posts
    13
    Situation is confirmed to be a ban on 2K's side after Xfinity Technician left, Technician confirmed suspicion of being banned on 2K's side using tracert to forums.2K.com, where hops are already out of Comcast servers proving it's not on Comcast's side. No new modem was provided, nor was connection issue to Evolve servers; additional information will be provided on the BBB complaint against 2K, as well as the review site review I intend on republishing if a resolution can not be found through that complaint before it is closed. Once again, this was posted through a proxy; still do not have the option to clean up prior posts seeing as edit does not work through proxy & delete option only available through edit option.

  14. #14
    Join Date
    Jan 2017
    Posts
    13
    Seems I've been unbanned after the last BBB response & so far haven't been rebanned. The video I posted on YouTube seems to have pointed out the method of ban & it doesn't seem to be effecting me at this point. As for the connection issues in the game, I'm still working on that with 2K & the BBB. I'll post an update later if I get the chance (provided I don't get IP banned again). I might ask anybody following this thread that you check to see if the issue has been resolved on your end, I'm still working on it on mine...

    EDIT: Also I can't find a deletion option on posts, so I don't believe I'll be able to delete the posts I intended on deleting (all I could do is wipe them to no less than 10 characters)...
    Last edited by WonderGamer; 02-13-2017 at 05:46 PM.

  15. #15
    Join Date
    Jan 2017
    Posts
    13
    The BBB complaint has been closed without a resolution & the support ticket that was running along side that complaint has been closed as (according to them) resolved (which it isn't). At this point I won't be purchasing from 2K ever again unless the Evolve server/profile problem gets resolved; the only thing I can do in it's current state is play Training until I run out of matches that award character XP & silver keys (about 3 times a day), which seems kind of pointless when silver keys are used on MP matches, but if anything I'll keep checking (once a day, not taking too much time to try connecting) to see if I'm ever able to properly log into the game in the future, although I'm certain I won't be able to get beyond day 1 in Daily Sign In rewards seeing as it's pretty well a miracle if I am able to log in at all...

  16. #16
    Join Date
    Jan 2017
    Posts
    13
    I've been going through the Evolve forums on Steam & appear to have found a workaround for this problem. The fix for the problem is simply to sit on the main menu for a minute or two before attempting to click on Play. I have tested this a couple times already & it seems to work. While the workaround may be simple, it's not obvious & many people are going to miss it...

    EDIT: Scratch that... The workaround allows me to get past the profile errors, however I'm still unable to connect to the multiplayer servers, throwing the following error directly after I click on play (after successfully logging into my profile):

    http://steamcommunity.com/sharedfile.../?id=879228714
    Last edited by WonderGamer; 03-08-2017 at 12:51 PM.

  17. #17
    Yeah I can't seem to connect either after having no issues for so long. It's really annoying and now I'm getting screwed out of some good Daily Rewards...

Posting Permissions

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