I've recently upgraded to the Talk talk WiFi hub after and no longer can see the Minecraft server over the internet.
The internal IP for the server is fixed, checked the port on the server and it's set to 25565. Server is up to date and firewall is off.
I've set the port to be forward for the server IP within the router both internally/externally across TCP.
I can log into the server locally with numerous computers but when checking if the port is open across the internet, it's showing as closed. I've checked whilst not connected to the same internet so that I don't get loop back. Still closed though.
No server can be found with "my external IP:25565".
Any help would be much appreciated.
Solved! Jump to the Best Answer.
@OCE_Michelle has asked me to help you. Please can you send me a screenshot of the port forwarding configuration you have used in the router, so as I can check it?
I am also helping another customer with Minecraft & the hub. This is what I replied with as it might apply to you as well:-
I have just tested this on my hub & TCP port 25565 opened the first time. This is what I used:-
You do not say if 25565 is UDP or TCP in your post. UDP will always report closed when using a port testing website, as these ports are not compatible with them.
Does this software run on Windows & if so, have you allowed an inbound rule through your PC's personal firewall?
Another possibility can simply be the method you are using to test this. If you could let me know, then I'll expand on this further.
Cheers for the reply and thanks Michelle for forwarding on.
I did mention above that it was over TCP but I have also selected UDP.
The server is running on a windows 8.1 pro. The firewall I had switched off to to insure there was nothing blocking it. No other antivirus software etc is installed.
Nothing has been changed on the server or other computers since the server was last working other than the new router being purchased.
This is the website that I have been trying to see if the port is open with. :-
Well I deleted the above rule, made a new one with what you had shown... and its worked!
If you could explain what the issue is for future reference it would be much appreciated so that I dont make the same mistake again!
Thanks again Keith,
Very much appreciated. Big thumbs up!
That is correct, using an external host entry is pointless unless you want to restrict access only from that address. In nearly all occasions you have no idea what the source address will be. When you create the rule, leave this field blank & it will show up with the wildcard type of "*" meaning any address.
Glad it is all sorted.