The Networking Tab In Settings

Parsec's networking and peer-to-peer connection system is pretty sophisticated, but there are situations that we cannot manage automatically. The peer-to-peer connection can actually be negotiated by either side of the connection. The only time that there's a problem is when both the client and the host are on a double NAT. This happens on about 5% of all Parsec connections each day. 

Why this tab is important

If your computer is having trouble making or accepting connections in Parsec, the new networking tab will really help. Also, if you prefer to turn off UPnP, you can do so on this tab. The settings are only available within the downloaded application.

The networking tab lets you do a few important things:

  • Define the ports that you are forwarding if you're on a double NAT as the server. We recommend starting with 8000 for UDP traffic when forwarding ports to your host using Parsec.
  • Define the ports that you are forwarding if your client is on a double NAT. We recommend starting with 9000 for UDP traffic when forwarding ports to your client, but you can really choose anything. We recommend 9000 for the client and 8000 for the server just so they're aren't any conflicts in the port ranges in case both the host and clients are on the same local network.
  • Turn UPnP off if you want to manage connections specifically through port forwarding.

Setting up Parsec for the connections

Once you've set up port forwarding on your router, visit the networking tab of Parsec's settings.

Annotation on 2020-01-10 at 14-35-18.png

Once you've forwarded your ports, if you're the server, add the first port to the Server Start Port. We recommend 8000 as a starting port. If you're the guest/client computer, we recommend 9000 as a start port. We also suggest turning of UPnP in case it gets in the way of your port forwarding - this is unlikely, but just in case, you might as well turn it off.

Annotation on 2020-01-10 at 14-36-31.png

Once you do that, you should be able to avoid the 6023 networking errors.