Haven't played in over two years... Bear with me, here, I just found out Bukkit is the kill.
I'll run down the check-list. Correct me if I miss something.
Port forwarded.
Server configured, IP left blank.
Ensured static IP.
Running server via .jar with .bat to launch to fix blank server UI.
Created firewall exception for correct port, in both, what, TCP and UDP? they're called?
I can successfully connect to my own server just fine, but a friend of mine cannot. He is NOT computer savvy. He knows how to work the power button. Maybe. I've tried everything I could short of an external service like Hamachi (because, again, friend is no good with computers). Am I missing something? Did I skip a step? Is the vanilla host just as crap as I remember, after all this time? Anyone?
Update: tried a few troubleshooting guides here, but none of the problems they listed were occurring. I've not no "failed to bind to port" issues or anything like that. It just keeps timing out when someone external tries to connect. The only issue I can think of would be my firewall, but I've created the exceptions already...
If it makes a difference, I'm on Win10 and Minecraft 1.8.9.
Rollback Post to RevisionRollBack
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
Simply being on the list is not enough, make sure all the check boxes next to the entries for Java and Minecraft are checked. Also make sure that your port forwarding is correct, make sure your server machines internal IP is the one being forwarded and make sure you give anyone trying to enter you external IP
Simply being on the list is not enough, make sure all the check boxes next to the entries for Java and Minecraft are checked. Also make sure that your port forwarding is correct, make sure your server machines internal IP is the one being forwarded and make sure you give anyone trying to enter you external IP
The boxes are checked, yes. But perhaps the port forwarding is the issue, then, because I've been using my external... I'm about to switch it back (because I changed it once last night from AN internal, just can't remember what I used), but I want to clarify:
When I port forward, am I using the internal IP I use to connect to my own server, or to my router?
*edit, scratch that. My router scolded me for trying to use the IP I use to connect to my server. IPv4 it is.
When you log into your router to set up the port forwarding, you need to forward the port you want on both TCP/UDP for the Internal IP of the computer that is running the server. That means go onto the computer that is going to act as the server and find its internal IPv4 address. That should be the one you have set up. Once all that is done, make sure you restart the Minecraft server software and then see if someone can connect to it using your networks External IP.
So, what I've learned from this, basically, is that the vanilla software hasn't gotten any better after all this time and the only way to host a server is to pay for a Realm. Peachy.
Rollback Post to RevisionRollBack
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
You have either done something wrong, your internet cant handle it, or your computer cant handle it. The majority of people have no issues once they have set it up properly. The majority of people have no issues with it once its set up, which means the vanilla server software is fine, its something on your end that is causing your issue.
I have 10mbps down, 6 up, 8GB of RAM on a $1000 laptop. The net and PC are fine. I've obviously done something wrong, and I have no clue what it could be... I've gone over it and over it and I can't find a single thing wrong. I've been on the forums, besides in this thread, looking at other common problems and solutions, even checking to make sure that if I HAD the problem I'm reading that I could fix it.
1.8.9 isn't the issue, right? It's listed to work with servers running 1.8 through 1.8.8.
I've got the port forwarded (correctly now).
I'm running on the server .jar so I can see the display, using a .bat to start it.
I'm connecting with an internal IP just fine, and I've visited a few sites that all confirm my external.
It's not failing to bind to port (it did ONCE, but because a previous launch had crashed. Killed that instance and it worked fine).
Firewall's set up to allow the traffic on the port AND from the programs.
What else... I feel like I'm missing something in that list and I can't think of it...
Rollback Post to RevisionRollBack
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
I finally got it... Let my router auto-fill a field in the port forwarding (another PC on the network had the same internal IP except for an additional zero on the end), deleted the extra digit, and tried again. I had a SINGLE error in the internal IP that was screwing up the WHOLE thing...
Rollback Post to RevisionRollBack
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
Haven't played in over two years... Bear with me, here, I just found out Bukkit is the kill.
I'll run down the check-list. Correct me if I miss something.
Port forwarded.
Server configured, IP left blank.
Ensured static IP.
Running server via .jar with .bat to launch to fix blank server UI.
Created firewall exception for correct port, in both, what, TCP and UDP? they're called?
I can successfully connect to my own server just fine, but a friend of mine cannot. He is NOT computer savvy. He knows how to work the power button. Maybe. I've tried everything I could short of an external service like Hamachi (because, again, friend is no good with computers). Am I missing something? Did I skip a step? Is the vanilla host just as crap as I remember, after all this time? Anyone?
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
Update: tried a few troubleshooting guides here, but none of the problems they listed were occurring. I've not no "failed to bind to port" issues or anything like that. It just keeps timing out when someone external tries to connect. The only issue I can think of would be my firewall, but I've created the exceptions already...
If it makes a difference, I'm on Win10 and Minecraft 1.8.9.
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
Where you have this "Created firewall exception for correct port, in both, what, TPC and UPC? they're called?"
Did you also make exceptions for the any entries of the Java or Minecraft programs themselves listed in the firewall?
Just checked. Yes, they all have exceptions as well, though I didn't make them...
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
Simply being on the list is not enough, make sure all the check boxes next to the entries for Java and Minecraft are checked. Also make sure that your port forwarding is correct, make sure your server machines internal IP is the one being forwarded and make sure you give anyone trying to enter you external IP
The boxes are checked, yes. But perhaps the port forwarding is the issue, then, because I've been using my external... I'm about to switch it back (because I changed it once last night from AN internal, just can't remember what I used), but I want to clarify:
When I port forward, am I using the internal IP I use to connect to my own server, or to my router?
*edit, scratch that. My router scolded me for trying to use the IP I use to connect to my server. IPv4 it is.
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
So now I'm using the static IPv4 I set aside, and Dinnerbone's server check still can't connect to me..
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
When you log into your router to set up the port forwarding, you need to forward the port you want on both TCP/UDP for the Internal IP of the computer that is running the server. That means go onto the computer that is going to act as the server and find its internal IPv4 address. That should be the one you have set up. Once all that is done, make sure you restart the Minecraft server software and then see if someone can connect to it using your networks External IP.
*edit, removed image of proof, it's been up there long enough...
Did that, though...
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
So, what I've learned from this, basically, is that the vanilla software hasn't gotten any better after all this time and the only way to host a server is to pay for a Realm. Peachy.
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
You have either done something wrong, your internet cant handle it, or your computer cant handle it. The majority of people have no issues once they have set it up properly. The majority of people have no issues with it once its set up, which means the vanilla server software is fine, its something on your end that is causing your issue.
I have 10mbps down, 6 up, 8GB of RAM on a $1000 laptop. The net and PC are fine. I've obviously done something wrong, and I have no clue what it could be... I've gone over it and over it and I can't find a single thing wrong. I've been on the forums, besides in this thread, looking at other common problems and solutions, even checking to make sure that if I HAD the problem I'm reading that I could fix it.
1.8.9 isn't the issue, right? It's listed to work with servers running 1.8 through 1.8.8.
I've got the port forwarded (correctly now).
I'm running on the server .jar so I can see the display, using a .bat to start it.
I'm connecting with an internal IP just fine, and I've visited a few sites that all confirm my external.
It's not failing to bind to port (it did ONCE, but because a previous launch had crashed. Killed that instance and it worked fine).
Firewall's set up to allow the traffic on the port AND from the programs.
What else... I feel like I'm missing something in that list and I can't think of it...
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red
I finally got it... Let my router auto-fill a field in the port forwarding (another PC on the network had the same internal IP except for an additional zero on the end), deleted the extra digit, and tried again. I had a SINGLE error in the internal IP that was screwing up the WHOLE thing...
"Tell me your stories, I'll lend you my ear. Tell me your horror, I'll make it disappear." ~ Fault Line by August Burns Red