Ports - Revision history

Nah at 06:49, 5 June 2021

2021-06-05T06:49:24Z

2020-11-15T05:43:49Z

2020-09-29T16:32:53Z

2020-09-29T16:29:50Z

2020-09-29T16:29:32Z

2020-09-29T16:28:45Z

2020-09-29T10:59:40Z

2020-09-29T10:59:07Z

2020-09-29T10:52:42Z

2020-09-29T10:50:55Z

@@ Line 98: / Line 98: @@
 * General: In case you wanted to use HCC.exe, make sure you didn't accidently use UCC.exe.
 * General: In case you are using a VPN (NordVPN, etc.), consider that your VPN provider may not give you a public IPv4 addresse and/or might filter ports.
 * 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.

@@ Line 20: / Line 20: @@
 ==== Third party guides about port forwarding in general ====
-https://www.wikihow.com/Set-Up-Port-Forwarding-on-a-Router
+[https://www.wikihow.com/Set-Up-Port-Forwarding-on-a-Router Wikihow]
 ==== Support sites from router manufacturers ====
-ASUS: https://www.asus.com/en/support/
+ASUS: [https://www.asus.com/en/support/ Support]
-D-Link: https://eu.dlink.com/uk/en/support
+D-Link: [https://eu.dlink.com/uk/en/support Support]
-Linksys: https://www.linksys.com/us/support/
+Linksys: [https://www.linksys.com/us/support/ Support]
-Netgear: https://www.netgear.com/support/
+Netgear: [https://www.netgear.com/support/ Support]
-TP-Link: https://www.tp-link.com/en/support/
+TP-Link: [https://www.tp-link.com/en/support/ Support] [https://www.youtube.com/watch?v=2tIUts0fyFk How to set up Port Forwarding on a TP-Link router]
 ==== tl;dr;====

@@ 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 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 have another 3rd party desktop firewall (ZoneAlarm, GlassWire, etc.) installed, add exceptions there as well/instead.
 * 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.

@@ 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 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.
 * 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.

@@ 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 actually match the path you are using HX from. This may happen after you move HX, install it a second time, etc.
 * 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.

← Older revision		Revision as of 10:59, 29 September 2020
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.
	* 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.
		+	* For the future: I have some ideas/plans for some more automated NAT travelsal, which should eliminate the need for manual port forwards for a majority of users.

@@ Line 83: / Line 83: @@
 === Troubleshooting ===
-* General: In case the server doesn't immediatly show up in the list, give it at least the one or another minute.
+* 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.*.*).
 * 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).

@@ Line 93: / Line 93: @@
 * 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.
-* HX: 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.