The Meaning of Life, the Universe, and Everything.
Join Date:
2/23/2014
Posts:
275
Location:
The Void
Minecraft:
Upsilon
Member Details
Edit your port forwarding. Now, do ipconfig. Get the IPv4 address it says in ipconfig, then change the ip in your port forwarding to that Ipv4 address you just got. Whenever it does not work, re-do that. If you do not want that to happen, try to configure a static private/local ip.
First time he tried, it said "failed to resolve host", then it said java.runtime exceptions error again. I don't understand why he can;t connect to it now or what changed.. if I can't figure this out soon, I think I'll just call it quits. 7-8 hours of this just isn't worth it man.
I gave him the right IP, and to make sure I gave him multiple different ones for him to try out incase they didn't work.. I think maybe I should call it quits. We can just find another game to play I guess, it's just shameful that we have to deal with this when we both just spent money on the game.
The Meaning of Life, the Universe, and Everything.
Join Date:
2/23/2014
Posts:
275
Location:
The Void
Minecraft:
Upsilon
Member Details
You could try running a LAN world with Hamachi. To do that, you need to have hamachi. Make a network and have your friend join it. Next, have him right click your computer's name in hamachi then click copy IPv4 address. You then host a LAN world. After, it should say a port in your chat. Have him connect to (IPTHATHECANGETBYPASTING):(PORTTHATISINCHAT).
Ok. Let's straighten some things out here. 192.168.1.2 is YOUR computers personal Network IP address. When you first turn on your router and connect to it, it automatically assigns an ip to your computer so that it can differentiate between devices. The one you port forward is the one that it assigns. With your computer, you have a Public IP address which is the 100.40.12.44, when you port forward, you give the router your personal IP (192.168.1.2) and it then allows people to access your Public IP and join your network without being in your network. Meaning, YOU join the server with either 192.168.1.2 or localhost because you are connected within your network and that doesn't require port forwarding. For other people to join they MUST use 100.40.12.44 to join, they are different IP's and it can be a little illogical that you don't port forward 100.40.12.44.
Explanation over, Basically, You connect to the server with localhost or 192.168.1.2 and your friend(s) connect with 100.40.12.44 or 100.40.12.44:25565
He tried that and it can't connect or it isn't found..
Is doing it in custom ports correct? I noticed there's other options but I've been doing it in custom ports this whole time on the verizon page..
I'm not sure what that is. I would do it on the port forwarding page you had earlier. You had it right earlier, you just gave your friend the wrong IP I think.
I'm going to catch some sleep, but I decided I'm going to make a new server from scratch by following your tutorial, and if I can't get it to work tomorrow, I'm calling it quits.. I'll update this forum tomorrow, I've been going at this for about 10 hours now at least possibly more..
I'm going to catch some sleep, but I decided I'm going to make a new server from scratch by following your tutorial, and if I can't get it to work tomorrow, I'm calling it quits.. I'll update this forum tomorrow, I've been going at this for about 10 hours now at least possibly more..
ok, thanks for looking, and starting from scratch would be best, hope you succeed, and if u have any issues, just message me
One thing I don't like about your video is you haven't shown how to add Java to the operating system path. A person following your video to the letter will wonder why they'll get an error about the Java virtual machine launcher throwing an error because the JVM couldn't start.
You also don't mention how to whitelist Java.exe (or Javaw.exe) so that incoming connections aren't dropped by the firewall.
Be (very) careful about telling users to add their IP address to the server.properties file. Depending on what IP address you put in there will mean whether or not the server will throw a port-binding error or whether they'll be able to connect using localhost or not. The norm is to leave it blank (Nimbleguy mentioned this) so that the server will bind to all available IP addresses on the system. This way, you can also connect to it using localhost (Poiihy and Nimbleguy mentioned this as well).
As a small nitpick, when you're port forwarding, you talk about, "having the ability to port forward using both TCP and UDP". A question to consider is why wouldn't a user not have the ability to use TCP and UDP.
One thing I don't like about your video is you haven't shown how to add Java to the operating system path. A person following your video to the letter will wonder why they'll get an error about the Java virtual machine launcher throwing an error because the JVM couldn't start.
You also don't mention how to whitelist Java.exe (or Javaw.exe) so that incoming connections aren't dropped by the firewall.
Be (very) careful about telling users to add their IP address to the server.properties file. Depending on what IP address you put in there will mean whether or not the server will throw a port-binding error or whether they'll be able to connect using localhost or not. The norm is to leave it blank (Nimbleguy mentioned this) so that the server will bind to all available IP addresses on the system. This way, you can also connect to it using localhost (Poiihy and Nimbleguy mentioned this as well).
As a small nitpick, when you're port forwarding, you talk about, "having the ability to port forward using both TCP and UDP". A question to consider is why wouldn't a user not have the ability to use TCP and UDP.
If you follow my tutorial step by step, it will work, and some people don't have the ability to select both TCP and UDP, so they have to select one of them, but most people have have the ability to, but I felt like I should say it.
Yep, I followed absolutely everything and I did everything right and no one can connect still. I'm done, this game can blow me honestly. 18 hours of work for nothing, good fight.
Explanation over, Basically, You connect to the server with localhost or 192.168.1.2 and your friend(s) connect with 100.40.12.44 or 100.40.12.44:25565
But you still port forward 192.168.1.2
Also remember, always port forward the 192.168.something.something IP and let people join on the http://whatismyip.com/ IP.
Is doing it in custom ports correct? I noticed there's other options but I've been doing it in custom ports this whole time on the verizon page..
ok, thanks for looking, and starting from scratch would be best, hope you succeed, and if u have any issues, just message me
You also don't mention how to whitelist Java.exe (or Javaw.exe) so that incoming connections aren't dropped by the firewall.
Be (very) careful about telling users to add their IP address to the server.properties file. Depending on what IP address you put in there will mean whether or not the server will throw a port-binding error or whether they'll be able to connect using localhost or not. The norm is to leave it blank (Nimbleguy mentioned this) so that the server will bind to all available IP addresses on the system. This way, you can also connect to it using localhost (Poiihy and Nimbleguy mentioned this as well).
As a small nitpick, when you're port forwarding, you talk about, "having the ability to port forward using both TCP and UDP". A question to consider is why wouldn't a user not have the ability to use TCP and UDP.
If you follow my tutorial step by step, it will work, and some people don't have the ability to select both TCP and UDP, so they have to select one of them, but most people have have the ability to, but I felt like I should say it.