Pandanym
commented
4 years ago I seem to have the same problem.
After a few successful connections clients can't connect anymore and I have to restart natholepunch.exe
Some of my client can never connect though, but I'm unsure if that's a firewall problem on their part.
I'm using a VM on Google Cloud Compute Engine running Debian
Version Number and Operating System(s):
Unity 2019.2.21f1 - Latest NAT server build from Git. Windows Server 2016 Datacenter (10.0.14393 Build 14393) Running on AWS EC2 instance. (t2.medium | us-east-1d)
Summary:
I'm currently running the included NAT server on a Windows Server 2016 instance being hosted by AWS. Roughly 60% of the time the functionality is as you would expect, clients can connect to each other using the NAT server.
Often though, the NAT server will stop registering new hosts. My temporary solution is to simply close and reopen the NAT server executable. This isn't acceptable as I don't want to interrupt users games at random intervals.
I'm also unable to have clients connect to a host more than once via NAT. Meaning if a host begins a game, then closes the game, and relaunches a new server. It's not registered on the NAT and users are unable to connect.
Both TCP & UDP ports are open on the server and Windows firewall on the server has been disabled.
Expected behavior:
NAT server should register a new host when they begin to host a session.
Actual behavior:
(See summary)
Steps to reproduce:
Install Forge, setup an Amazon EC2 instance, and launch the NAT server.
[Optional] Discord Username:
Funnyguy77#3828