I am currently running a Minecraft server for a few friends on a laptop connected to a TELUS Wi-Fi Hub. I have successfully configured it so that both local and global users can connect and everything works fine EXCEPT that when my roommate disconnects from the server or the server is restarted on a local connection. Important details:
If anyone has ever dealt with something like this or knows what's going on I would be super grateful for any input you can provide (the port issue, not the maleficent network spirits) .
- The user's PC is hardwired in to an ethernet switch which runs straight to the router. They are on port 4 of 5, this does not seem overly important to me.
- This is exclusive to the user's PC. My PC is hardwired via the same pathway to the router and does not cause this issue
- all local users are connecting via the server's local IPv4
- It does not matter whether they are the last user on the server or there are multiple people still in the server on both local and global connections
- all users currently in the server remain connected until they end the session. This issue only affects the port itself.
- This only happens when the user is connect via a local connection. When connected via global IP address using my phone as a hotspot, disconnecting does not close the port
- This still happens when the user is connected via wi-fi to an auxiliary router that is hardwired to the ethernet switch that runs to the main router.
- setting a static IP for the PC did not fix the issue
- Setting the PC's local IPv4 as a DMZ did not fix the issue
- disabling intrusion detection on the router did not fix the issue
- updating/installing java (JRE and JDK) did not fix the issue
- I have double checked that all java related executables are allowed through the firewall, namely whatever was in the firewall already (2 instances of javaw.exe) and the freshly installed java.exe and javaw.exe from the freshly installed jdk and jre (possibly redundant idk)
- Logging into the router, editing the port, and saving the settings without changing them seems to refresh the port and open it back up. The current fix is to just refresh the port whenever the user leaves the server or the server is restarted.
If anyone has ever dealt with something like this or knows what's going on I would be super grateful for any input you can provide (the port issue, not the maleficent network spirits) .