FAForever Forums
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Login
    The current pre-release of the client ("pioneer" in the version) is only compatible to itself. So you can only play with other testers. Please be aware!

    Problems connecting FAF game lobbies

    Scheduled Pinned Locked Moved I need help
    2 Posts 1 Posters 250 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      Tripod
      last edited by Tripod

      I have issues connecting to the game lobby. Restarting my machine normally fixes it (at least temporarily). Any idea what could be causing it? Below is the last part of the log. I think the game might be confused as I have multiple networks attached to my PC. I run VMware machines for development. I notice it sets the NAT handler twice.

      info: /country
      info: /init
      info: /numgames
      info: /mean
      info: /clan
      info: /deviation
      info: GPGNET: setting nat handler to 0x11837004
      info: LOBBY: Game port 48073[UDP] opened.
      info: LOBBY: starting with local uid of 263413 [YouTheNoob]
      info: GPGNET: entering lobby state.
      info: NET: using deflate compression for sends to %CPU_NAME%:61193.
      info: LOBBY: Connecting to host "NotInsanity" [%CPU_NAME%:61193, uid=373906]
      info: Can't add chat text -- no chat display
      info: text=Connecting to game host...
      info: Minimized true
      info: Minimized false
      info: GPGNET: setting nat handler to 0x00000000
      info: CNetTCPBuf::Read(): recv() failed: WSAEINTR
      info: Run time: 0h00m49s

      1 Reply Last reply Reply Quote 0
      • T Offline
        Tripod
        last edited by

        If you are looking at this in the future, I figured out what the problem was. I have dual stack: IPv4 and IPv6. I think that the system was switching between IP versions, causing the NAT to fail. I disabled IPv6 on the network interface and it seems to have fixed it.

        1 Reply Last reply Reply Quote 1
        • First post
          Last post