Where are you getting this information? I still think it is incorrect. All clients (and the server because it is just a client) want to talk on the same port, and if they can't, it fails.FishSandwich wrote:Your scenario assumes that the port is a fixed number for all clients, which isn't the case.
Just tried:
Server on local network at 34199 (external port forwarded to server)
Local client on another machine at config set to 34197 (external port port forwarded to corresponding machine)
Remote client with config set to 34197 (must connect by using ADDRESS:34199")
Remote client can try to connect to ADDRESS:34197 or ADDRESS:34199 (both are valid connection points since everything is peer to peer). I see the connection attempts in the server console window. If i connect form the local client first, the remote client can't connect. If remote connects first, the local client can't connect. Both fail with the same error, can't connect to peer. It fails the same if the ports are reversed with the server on 34197 and the clients set to 34199 (and corrected on the router).
All players try to talk on the same port, and if they can't, connection fails.
MF- has mentioned the only likely way around this...with private VPN, hamachi, etc.