Can't connect to Server using Hamachi

1. Mac OSX Lion 10.7.3
2. 64 Bit-Core i5
3. 64 Bit Java, Version: 1.6.0_29
4. Hamachi
5. Bukkit 1.1-R6-b1988
6. The "start_server.command" from the Wiki, I did it exactly right.
7. None yet, just trying to get the server working!
8. The server starts just fine, if I have it in my server list, I can see that you can connect to it, but when I (or anyone else for that matter) try to, they cannot. It either displays "Internal exception:java.net.SocketTimeoutException: Read timed out" or it says "Logging in" until it disconnects itself because it takes to long to log in.
9. I've tried reinstalling CraftBukkit, re-forwarding port 25565, deleting, and recreating my Hamachi server, restarting my computer, and restarting my modem.
10. I tried all the stuff you guys said to, and on vanilla I can connect, but like I said before while the server is bukkit, I can't...I'm still using Hamachi.

 

First, why use Hamachi? Port Forwarding is SO much easier, unless you haven't bought Minecraft. Second, people have to connect to your Hamachi server to connect to your Minecraft server. Also, you have to give out your Hamachi IP to people, not your original external IP.

Hope this helped ^^

 

ditch hamachi. google port map. download it. run it. click the + button. type 25565. check both things. name it minecraft. you are done. Connect to it by finding your static ip. Google whats my ip address. type in yourip:25565

 

I'm using hamachi because when I tried to port forward, it worked even less, I couldn't connect using my external IP or localhost/internal IP and it didn't even display that anything was online in my server list. Also I know I have to give out my hamachi IP, if you had read my post in its entirety you would know that I was connecting to my hamachi IP, as it displayed that it was online.

As I said before, port forwarding wasn't working. Also hamachi isn't that hard to use, and I had a server using hamachi back in the late fall of 2011, but then joined another server in the meantime, I wanted to return to my server, so I had to update it. Hamachi has worked fine for me in the past, just not right now, as I said its not hamachis fault, because the server runs on vanilla with hamachi just fine, I'm not asking for you to tell me to Not do something that's working better (and has worked better in the past) for me, that bukkit is clearly capable of doing.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

There's your problem. If you can't even connect using localhost that probably means your server isn't up to date, it isn't actually on, or you're doing something beyond retarded. I only say this because to connect to your own server alone, you don't ever need to port forward and don't ever need Hamachi. All you need are the server, Minecraft and an internet connection to connect to Minecraft.net

Unfortunately, I can't really help you unless you give me a step-by-step set up of what you did when you made your server. But for convenience, here's a step-by-step tutorial on how to do it properly. I assume you're using CraftBukkit.

1. Update Minecraft
2. Download the latest CraftBukkit, here's an auto-installer with a few crap plugins, but it's automatically configured so you don't have to do much. Click me
3. Have a test try. Meaning don't do any internet related configurating, don't use Hamachi, just connect to your IP with localhost or your internal IP, which you can find by going to: run/start search -> cmd then type in ipconfig, your IPv4 IP should be your internal IP which only you can use to connect to your server with. Also, if you're using your internal IP, don't forget to use :25565 at the end of the IP!
4. Configure the Server.properties to anything you desire
5. Port forward/use Hamachi. I don't acutally believe for a second you can't port forward on your router, unless you have a Tesco router, they suck really bad. Anyway, here's a link on how to port forward. Click me
6. Have another test try, but this time with your mates. If it doesn't work, come back to this to check if you've done something wrong, if it works, YAY!

By the way, using localhost sometimes might not work if you have two or more computers in your household connecting to your router. With some routers, localhost only works with one computer at a time, or it might just stick to one internal IP in the house that can use localhost.

But to get to the point, your main issue is the fact you can't even connect to your damn server to begin with. I advise using your internal IP, which should look like 192.168.*.*** Obviously you replace the asterisks with numbers. Also, the amount of numbers after 192.168 can differ. So mine is 192.168.0.103 but before I got a new router is was 192.168.1.4

Hope this helped! ^^

PM me if you're STILL having issues.

P.S. I'm dumbing this down as much as possible and adding information that you have probably already mentioned doing, but it's best to do it this for safety measures. Besides, someone might stumble across this post somehow and might make convenience with it. :3