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.
https://minecraft.gamepedia.com/Tutorials/Setting_up_a_server#Configuring_from_the_command_line
Cheers
1
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
binaryinstallation 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:java -version
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?
Edit- Poor word choice.
2
Thanks @briceorbryce here's the link to the source of that information for anyone who is interested. http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#64bit_layering
------
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:
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
And last but certainly not least, click this link (https://api.ipify.org/) , and give your other players THAT ip address to connect to. That is your external/global IP address.
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.
1
No worries, networking can be a little complicated... each network is a little different. Take a look at the simple diagram. There are at least 4 points of failure that you can control. The way I handle these issues is to work through them from start to finish eliminating each one until I find the issue. Its a simple process once you do it a few times.
Starting with A, your server application, do a quick run-through and make sure that your configuration options are correct. Since we're primarily focused on networking, leaving everything at its default value would be recommended. Start the server and check for errors. None? Then move to B...
You said you checked your windows firewall and made sure the port was open. Did you add a rule for the port number itself? ... or the application (Java)? In my personal experience I don't use firewalls on internal network computers. It adds an unnecessary layer of complication to things. But this is security risk I'm willing to take. I guard access to my network, as a whole, like a momma bear protects her cubs. So I know every device on my network and actively look for intruders... Anyway, for the purposes of this exercise, turn off the windows firewall completely. That will resolve B. (We'll enable it later to see if it causes any problems after we've made a successful connection)
Before we get to failure point C, try using a different computer, Computer B, to connect to your server. Use the server's LOCAL ip address. Usually the one that starts with 192.168... or 10.0... If that works, we can go on to failure point C.
Assuming it works, this is where your port forwarding rule comes into play. Make sure that the ip address you're forwarding to is the correct one. On the server, from the command line (Start -> Run -> cmd) type: "ipconfig" without the quotes and press enter. Get the IPv4 Address. That's where you're forwarding the port to. It would look something like this:
Once you're positive you have your forwarding rule pointed to the correct computer inside the network, failure point D would have you use an external service to test it's connectivity to your computer from the outside. MxToolBox <- I use that a lot. Use that tool to check your EXTERNAL ip and port combo. ###.###.###.###:25565 ex. If that works, then you're all set. If it doesn't, then we can go onto other things, like putting your server in the DMZ (TEMPORARILY!) and trying again. You do that on the router, btw. It basically lets ALL traffic through to the server. Its definitely not recommended to keep it this way though. But if putting your computer in the DMZ works, then you have a problem with your port forwarding rule. So you would know where to start.
Also, something I just thought of, make sure that your server has either a static IP address in the correct range or a permanent DHCP reservation. This can be configured on the server itself or on the router, depending.
The whole point is to try and narrow down the point of failure and correct it.
Work through that and let me know if you have any questions.