Interesting Port Problem

So I have all ports I use open for Minecraft
25565
25566
25575

I am running Bukkit on a netbook with Kubuntu installed, using SSH to handle all the work on my main computer.

When I set up the server with no 'server-ip=' set, I can login, but other people can't see the server online at all, they get "Connection Refused: Connect" yet when I assign the server with the IP 192.168.1.4 it will let all my friends on (from different countries etc) but not me, instead I get the "Connection Refused: Connect" I use the ip 192.168.1.4 to login, as "localhost" won't work for the local server, as it's not on this machine.

Yet without the 'server-ip=' set, I can get in and they can't.

Also, I have to use 25566 for my MC server, becasue 25565 will always show up as closed on port checkers (even though it is listed as open, and will work just fine if I run the server on windows)

 

I don't see why you are opening up 3 ports for a single Minecraft server than can only have a single port assigned to it at one time.

There really isn't a need to manually assign an IP to the game server either on a home network running a single server with a single network interface.

Are you actually forwarding the port you have set in your server.properties the the IP of your netbook?

 

Does it work with server-ip=0.0.0.0?
Also, what's the output of ifconfig on the server?

The fact that you can't use 25565 on Linux but on windows is also odd, sounds like something is wrong with your system there... (firewall, ip stack misconfigured/broken)

 

I use 25565 on Linux servers all the time for Minecraft. That isn't the issue.

 

Yeah, but you're not the one having the problem, right?

 

"The fact that you can't use 25565 on Linux", I was simply saying your fact is incorrect.

 

Lrn 2 read dude! Let me try to give you a little hint:

(protip: you does NOT refer to everyone)
Next time someone opens up a thread being like "port forwarding doesn't work" are you gonna be like "I'm using port forwarding all the time, so that's not an issue" or what?

 

Calm down, it was simply a misunderstanding in regards to your wording.