I have used this to check and make certain that my Port-Forwarding HAS been done 100% correct, in line with the previous website's same External IP address.
I have tried to change the Port-Forward from 25565 to 25566 and neither work.
Details:
I am trying to "start up" a 1.9.4 CraftBukkit server
All of the server files are correctly intact, so the problem should not be originating from there
The server.properties portion that says "server-ip:" IS BLANK, as it should be
When I start up the server, it starts up, tells that it is "Starting Minecraft server on :25566" (and previously, ":25565"), loads the world, and says "Done (21.654s)!"
I am fully able to connect to the server using my Internal IP address- or by typing "localhost" into the Direct Connect box- but I, nor my friend, cannot connect to the server using the External IP
When connecting using the External IP address typed into the Direct Connect box, it says "Connecting to the server..." and then a second or less later, it says "java.net.ConnectException: Connection refused: no further information:"
If anyone has any possible solution, please comment back to me to help! I am sorry if I am missing any necessary information in order to help fix the problem; if I am missing any information, please ask me for it and I will deliver.
EDIT:
Now the Port-Forwarding website has changed to "port closed" and I do not understand why.
RE-EDIT:
NOW the Port is OPEN...??? Still can't connect through External IP
SUPER EDIT:
New adaption: it seems that my port is going back and forth between OPEN and CLOSED... Could it be a time-thing?? The port is considered OPEN when I have the server running, and is considered CLOSED when the server is not- I don't know what this means. Either way, OPEN or CLOSED, the server does not allow any External connections.
I made an edit to the original Reddit post that I forgot to make here, and this seems to be the main problem
"
MAYBE FINAL EDIT?: - It SEEMS that I can "join" the server through the External IP IF I change my router setting to DMZplus mode - This changes my IP address AWAY from a Static IP, and therefore screws with my internet, not allowing me to connect to certain websites as well as not allowing Minecraft Multiplayer to work!
Resolved! Not 100% certain what fixed the problem, but it is working now. Something with the firewall screwed up I presume. Maybe it was a port-forwarding fail? Who knows, but it is working now, thanks to the help of mr commentor down below.
https://www.reddit.com/r/Minecraft/comments/4mqtry/need_help_with_minecraft_server/
https://www.spigotmc.org/threads/minecraft-craftbukkit-1-9-4-server-help-needed.153594/
"
I cannot get my Minecraft server to run correctly. I am trying to run CraftBukkit 1.9.4
https://dinnerbone.com/minecraft/tools/status/
I have used this to check and make certain that my External IP address is the "correct" IP address to connect to, as this says the server is open.
http://ping.eu/port-chk/
I have used this to check and make certain that my Port-Forwarding HAS been done 100% correct, in line with the previous website's same External IP address.
I have tried to change the Port-Forward from 25565 to 25566 and neither work.
Details:
If anyone has any possible solution, please comment back to me to help! I am sorry if I am missing any necessary information in order to help fix the problem; if I am missing any information, please ask me for it and I will deliver.
EDIT:
RE-EDIT:
SUPER EDIT:
"
Can anyone help?
I made an edit to the original Reddit post that I forgot to make here, and this seems to be the main problem
"
MAYBE FINAL EDIT?: - It SEEMS that I can "join" the server through the External IP IF I change my router setting to DMZplus mode - This changes my IP address AWAY from a Static IP, and therefore screws with my internet, not allowing me to connect to certain websites as well as not allowing Minecraft Multiplayer to work!
"
So then how would I fix the problem?
I added you
EDIT:
Resolved! Not 100% certain what fixed the problem, but it is working now. Something with the firewall screwed up I presume. Maybe it was a port-forwarding fail? Who knows, but it is working now, thanks to the help of mr commentor down below.
Wouldn't let me edit up above... glitches galore