Author Topic: Minecraft Bukkit Server - Help  (Read 650 times)



It's my friend's server, and he can't figure out what's going on, so I offered to look into the matter for him in hopes someone on here would know.
He can't connect, however he knows the server is running in the background. His dad works on computers, and he says his ports are forwarded, and that he's got the right version. He can connect to other servers but not his own.
if there is any info you guys need, lemme know and I'll try and keep this updated.

Edit:
EXTRA ADDED INFO
He's using Bukkit, his versions ARE matching, and he's using v1.6.4
« Last Edit: November 06, 2013, 08:34:14 PM by AdinX »

Try redownloading the server .jar?

Try redownloading the server .jar?
That didn't appear to help

He's using Bukkit, his versions ARE matching, and he's using v1.6.4

looks like youre trying to connect with minecraft 1.7.2...

...

...

...

Since the error in the image is invalidated by "I'm too dumb to try using the same version" please provide more info than "he can't connect."

If it's the same then no he's not properly port forwarded or he's hosting a local server.

Version mismatching gives a different error than a timeout I think so you must have a different problem than just a version problem (but that is also going to be a problem if you try and connect to a 1.6.4 server with a 1.7.2 client like you might have in the screenshot). So follow these steps if you want to get to the bottom of it. In each of these steps the computer running the client (including the server) should be one that you test right before each step that it can connect to other minecraft servers so that you thereby know that the problem is with the server or the server's local network and not with the client computer.

I'm assuming that the server is a typical computer running behind a typical home network setup.

Step 1: Try and connect to the server by running a client on the computer the server is running on and connecting to 127.0.0.1. This is the localhost loopback address. It only works on the computer you're running the server on and doesn't use any external networking. If this doesn't work then the server is not running, or there must be a problem with how the server software or server computer is configured.

Step 2: Try and connect to the server by running a client on another computer on the same local network with the 192.168.1.122 address. Addresses starting with 192.168. are local addresses and can only be connected to by computers on the same local network. If Step 1 worked and this doesn't work, you probably have the wrong local IP address. Or something on the server, like a firewall, is blocking the connection. Or something in the local network switch/modem/router hardware is blocking local computers from connecting to each other (this is unlikely unless someone specifically configured the network that way).

Step 3: Try and connect to the server from a computer outside the local network (like at another house) with the public IP (which is not the 192.168. address) of the local network switch/modem/router than the computer is connected to. You should be able to get the public IP by Googling "what's my IP" on the server computer or looking it up in the network switch/modem/router configuration. If step 1 and 2 worked and this didn't, then you have the wrong public IP address or your ports are not forwarded correctly.