Well except for the exception that I can't run the file with the command "java -Xms1024M -Xmx2048M -d64 -jar minecraft_server.1.12.2.jar nogui" and even "java -Xms1024M -Xmx1024M -jar minecraft_server.jar nogui" through cmd.
But anyone who tries to get in the server from outside, or generally using the external ip, they cant connect and it tells them "io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information:". I checked my port through https://www.yougetsignal.com/tools/open-ports/ and it says its closed when its supposed to be up.
I did turn off my firewalls, and checked configuration options (they are on default and correct) and tried to re instal them several times but the port remained closed. what do i do...?
When you say you can’t run the server with the commands you’re using... why not? What’s the error message you’re getting?
Btw, the “-d64” flag is only to be used on the Solaris operating system. Java for Solaris has both the 64bit and 32bit JVM in a single binary installation and needs that flag to specify which one to use. For windows, Linux, mac... that flag isn’t needed. If you want to use the 64bit version of java, you’ll need to download and install it. After that, from the command line execute the following:
and it will tell you if you’re running the 64bit version.
Are you able to connect to the server from another machine on your local network? On the server itself? What do the logs say? Any error messages of any kind?
whenever i try, it just says "Error: Unable to access jarfile minecraft_server.1.12.2.jar"
yes, any computer from local network can get in and work fine and play normally (no error messages), but when someone from out of the local network tries to get in it tells them "io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information:" so yeah the probnlem is only for people out of the local connecting
Btw, the “-d64” flag is only to be used on the Solaris operating system.
I updated the Minecraft Gamepedia site to specify the d64 flag is used only for Solaris. I wasn't exactly sure how to reference you and this thread so I just linked it (instead of doing some sort of superscript thing lol). Nice to know some people still read it before coming here.
So PeteSK... run through the steps one more time. Something has to be missing or a typo or something. Take a look at the following:
This is the ipconfig command. Open a command prompt on the server machine (and I'm assuming you're on windows, if not I can guide you through all common operating systems) and type:
when you press enter you should get something similar. Look for the IPv4 Address line and take note of what you see. It should start with one of the following types of local private network addresses:
If it starts with a 169 you have a problem. That's a whole different issue. Anyway, once you have the output of ipconfig go back into your router settings and make absolutely sure that you have entered the rule correctly and that the internal IP address is the same there and from ipconfig. Make sure you're firewall is configured correctly... there are endless tutorials online for any version of windows. Lastly, on the server machine, start your server via the command line:
With everything being default, you should see something like this as your output...
Once the server is started, open another command prompt and type the command:
netstat -n -a -b -o -q | FindStr ":25565 java"
after pressing enter you should see something like whats in the bottom half of the last picture. What this does is verify that your server is actually listening on all interfaces and ip addresses on your machine. If it is, you'll see it. 0.0.0.0:25565 for IPv4 and [::]:25565 for IPv6
If you are absolutely positive you have done everything correctly and it still doesn't work, Google how to use traceroute and other network troubleshooting programs. If those tools verify that your connection to the other players is route-able, then you may need to contact your ISP to see if they can explain why packets are being dropped out of thin air.
Oh, and speaking of route-able, all of this assumes standard internet household network configuration. If you have your Cable/DSL modem that comes from your ISP (like, they gave you a box for your internet that's hooked into the wall somewhere that you didn't buy at BestBuy/Amazon/etc.. yourself) AND that's all you would have needed to get internet but you have this Netgear R7000 hooked up to it because you wanted it, then you will have to access the router/device/modem that your ISP gave you via ITS web interface and either put your Netgear R7000 into the DMZ or forward the ports from that device to your Netgear R7000.
You should not have the following:
Internet -> Router/Modem combo connected at wall -> Netgear R7000 -> Your server
If that's the case, all you have done is forwarded the ports from the R7000 to your server but not from the Router/Modem combo device to your R7000. You have to open the port for every device in the line...
Anyway, I'm sorry if this just increases the confusion. If this doesn't resolve your issue, then we will need a whole lot more information on the type of devices in your network, starting at the wall and going all the way to your server. (name, type of device, model number, etc.) We'll also need to know what OS you're running. Pretty much, just paint us a picture of what you got and we'll make it work.