Port-Forwarding Troubleshooting
Last modified:
Port-Forwarding Troubleshooting
The following articles explain some of the common issues which can occur to prevent port-forwarding from applying correctly and interfere with connectivity. We have arranged these topics based on what issues we often see crop up and their common solutions.
Hamachi & Tunneling Software
In some cases where your computer is running tunneling software such as Hamachi you may find that the port forwarding test does not result in a success. This is because network adapters for such software are often prioritized above your normal internet connection and the ULink networking middleware attempts to communicate outwards on these adapters.
This means you may not be able to host, even if your port forwarding has truly been successful, because the game is listening on the wrong adapter. In order to work around this we advise temporarily disabling any tunneling adapters.
UPNP & Port-Forwarding Conflicts
In some cases UPNP (The service responsible for automatically opening ports for applications) can generate a faulty config, so when you port forward it can consider both the UPNP and Manual forward active. If for some reason your port forward is still failing try disabling UPNP and restarting your router with the Manual forward enabled.
You should also take this opportunity to check your Port Forwarding table to confirm no other entries have been made for 27015 and 27016, especially if they are sent to another PC. This will prevent clients from connecting.
Firewalls
This one may speak for itself, but a firewall running on your PC also blocks ports. Make sure that you allow WftO in your firewall. Most firewalls pop up an "allow/deny" dialog which allows you to let the program accept connections.
In some cases it may be necessary to explicitly add WftO to a whitelist. It is known that in some cases WFTO is blocked in Windows Firewall and rules should be checked to ensure that network traffic is allowed to WFTO. Even if Windows Firewall is disabled it can still prevent traffic if not explicitly allowed.
To check Windows Firewall follow these instructions:
- On Windows 7, 8 and 10 type Windows Firewall into your search bar and choose "Windows Defender Firewall (Control Panel) from the list
- In the new window click "Allow an App or Feature through Windows Defender Firewall"
- Scroll through the list of allowed apps and features to find War for the Overworld and "wftogame" ensure that these applications are ticked both in the left hand checkbox and for the appropriate Private or Puublic checkbox depending on your network setup
- If these apps are missing from the list then you should add them by clicking "Allow another app" and browsing to the installation directory of War for the Overworld. Then choose to add both "wfto.exe" and "wftogame.exe"
- Check to see if your connection problems are resolved.
Static and dynamic IP-addresses
You may find that after restarting your PC, the local IP address found in step 1 has changed. This means your IP is dynamic: it is automatically obtained from your router, and may change every now and then. Especially with multiple PC's on the network, the IP addresses may be scrambled every day.
When the IP address changes, this means that the ports are now forwarded to the wrong IP, and it won't work anymore.
You will have to find the new IP and change it to that.
However, it is also possible to change your IP address into a static IP, so that your PC will always request the same IP from the router, and your forwarding stays intact.
For more information on how to do that, visit these guides onhttp://portforward.com/networking/staticip.htm
If your issue is not resolved after checking all these things then contact us directly by submitting a help ticket or on our discord.