Difference between revisions of "Ports"

Line 95: Line 95:
 
* Windows: Verify that the entries for HX.exe and/or HCC.exe in the Windows Firewall exception list have their boxes checked.
 
* Windows: Verify that the entries for HX.exe and/or HCC.exe in the Windows Firewall exception list have their boxes checked.
 
* Windows: Verify that the entries for HX.exe and/or HCC.exe actually match the path you are using HX from. This may happen after you move HX, install it a second time, etc.
 
* Windows: Verify that the entries for HX.exe and/or HCC.exe actually match the path you are using HX from. This may happen after you move HX, install it a second time, etc.
* General: Make sure you don't have another 3rd party desktop firewall installed, which actually blocks it.
+
* General: Make sure you don't have another 3rd party desktop firewall installed, which actually blocks it instead of the Windows Firewall.
 
* General: In case you wanted to use HCC.exe, make sure you didn't accidently use UCC.exe.
 
* General: In case you wanted to use HCC.exe, make sure you didn't accidently use UCC.exe.
 
* Otherwise: Sometimes it's plain out of your hands. Your ISP may not give you a public IPv4 address you need for server hosting, which is in particular common for mobile connections. Your ISP may also plain be filtering out these ports. Maybe let your friend try if he has more luck hosting a server.
 
* Otherwise: Sometimes it's plain out of your hands. Your ISP may not give you a public IPv4 address you need for server hosting, which is in particular common for mobile connections. Your ISP may also plain be filtering out these ports. Maybe let your friend try if he has more luck hosting a server.
 
* For the future: I have some ideas/plans for some more automated NAT traversal, which should eliminate the need for manual port forwarding for a majority of users.
 
* For the future: I have some ideas/plans for some more automated NAT traversal, which should eliminate the need for manual port forwarding for a majority of users.

Revision as of 17:29, 29 September 2020

Preamble

This is only needed if you intend to host a server on your computer. This is not required for joining a game.

Copy and pasted Ports.txt from HX

ServerPort is set as Port option under [URL] inside HX.ini. This needs to be forwarded to allow other clients to join.

ServerQuery/ServerUplink will use up the two next available ports, so for masterserver/gamelisting to work these need to be forwarded too. This will typcially be 7790-7792 unless other programs use these ports up already. So you might need to increase the range upwards, say 7790-7800.

You can check HXServer.log for: DevNet: TcpNetDriver on port 7790 Init: UdpServerQuery Port 7791 successfully bound. Init: UdpServerUplink Port 7792 successfully bound.

If the last two differ, you need to forward these ports.

Just UDP is required for forwarding.

Third party guides about port forwarding in general

https://www.wikihow.com/Set-Up-Port-Forwarding-on-a-Router

Support sites from router manufacturers

ASUS: https://www.asus.com/en/support/

D-Link: https://eu.dlink.com/uk/en/support

Linksys: https://www.linksys.com/us/support/

Netgear: https://www.netgear.com/support/

TP-Link: https://www.tp-link.com/en/support/

tl;dr;

Forward UDP 7790-7800

Adding exceptions to the Windows 10 Firewall for HX

On Windows 10 you also need to manually add HX.exe and HCC.exe to the Firewall exception list.

Step 1

Open Windows Security > Firewall & network protection page and click on Allow an app through the firewall.

Windows10Firewall 01.png

Step 2

Click "Change Settings" and confirm if needed.

Windows10Firewall 02.png

Step 3

Click Allow another app...

Windows10Firewall 03.png

Step 4

Click Browse, Pick HX.exe this time and click open.

Windows10Firewall 04.png

Step 5

Click Allow another app...

Windows10Firewall 03.png

Step 6

Click Browse, Pick HCC.exe this time and click open again.

Windows10Firewall 04b.png

Done

The End.

Troubleshooting

  • General: In case the server doesn't immediatly show up in the list, give it at least one or another minute.
  • General: If the server is showing up neither in the ingame server list, nor isn't showing up on http://333networks.com/s/hx let someone try directly join by public IP address. Try googling your public IP address: https://www.google.com/search?q=What%27s+my+IP
  • General: Make sure in the above step, you actually gave out your public IP address, not your LAN IP address (NOT 192.168.*.*, NOT 10.*.*.* and NOT 172.16.*.*-172.31.*.*).
  • General: In case joining by IP works, but the server is not showing up in the list: Make sure you didn't start a LAN game, or your friend is looking for LAN games.
  • Router: Verify you allow the UDP protocol on the port forward, and not just TCP only.
  • Router: Verify you still forward to the correct local IP address. The DHCP server on the router may have assigned your computer a new IP address after you set up the port forward. (In case this happened, you might want to look into the routers address revervation feature to avoid it in the future).
  • Router: Verify that you forward at least ports 7790-7792.
  • Router: Try increasing the upper limit of the forwarded port range, to say 7790-7800. The game will always pick the first three non consecutive increasing ports numbers starting with 7790, and another program may already be using some of the ports, shifting the port number for the HX server into the non forwarded range.
  • General: Make sure you didn't start the HX server multiple times and closed the first started instances, and your remaining running server listens on the ports which are now outside the forwarded range.
  • Windows: Verify you added HX.exe and/or HCC.exe to the Windows Firewall exception list.
  • Windows: Verify that the entries for HX.exe and/or HCC.exe in the Windows Firewall exception list have their boxes checked.
  • Windows: Verify that the entries for HX.exe and/or HCC.exe actually match the path you are using HX from. This may happen after you move HX, install it a second time, etc.
  • General: Make sure you don't have another 3rd party desktop firewall installed, which actually blocks it instead of the Windows Firewall.
  • General: In case you wanted to use HCC.exe, make sure you didn't accidently use UCC.exe.
  • Otherwise: Sometimes it's plain out of your hands. Your ISP may not give you a public IPv4 address you need for server hosting, which is in particular common for mobile connections. Your ISP may also plain be filtering out these ports. Maybe let your friend try if he has more luck hosting a server.
  • For the future: I have some ideas/plans for some more automated NAT traversal, which should eliminate the need for manual port forwarding for a majority of users.