Ensure port forwarding is straightforward...
Ensure port forwarding is straightforward...
You're trying to set up a Rust server for your friends and you've already tried a few things. The Windows Firewall is blocking the port, and the Port Check Tool shows it as closed. It seems the problem lies in your network configuration rather than the server setup itself. Have you double-checked which WAN interface you're using on Windows 10? Also, ensure that the server's local IP address matches what you're using in the firewall rules. Let me know if you need further guidance!
Verified the host's IP address remains consistent; it hasn't shifted and is configured as static.
Since the WAN IP isn't required, it seems unnecessary. I don't understand its purpose. If you'd like, you can reset your router—it might resolve any issues.
I've attempted both with and without the WAN IP, but it hasn't worked. I haven't tried the ultimate tech support option—restarting the device—but will share an update soon! 😊
It seems unnecessary to mention the WAN IP. It feels like an awkward requirement given how it can change and your router should handle identifying the correct interface. Are you certain your device is set to use 192.168.200.52? Also, confirm that the firewall on your desktop allows traffic on that port. If you're using Windows Firewall, you might not need to specify an IP when opening the port. Verify that your Rust server is set up to use those ports—28015 is the standard, but double-check its configuration and ensure it's active. If the server runs, you should be able to connect to itself by typing `net.connect 127.0.0.1:28015` on the Rust start screen. If this fails, the issue likely lies with the server itself.
It suggests the client connection failed because the firewall rules permit the port but there is a problem with the command execution or network path. The error indicates the connection attempt was dropped, possibly due to missing dependencies or incorrect parameters.