Hello, I've port forwarded several servers before, but this time I'm stumped. I seriously have no idea what I'm doing wrong.
I'm using a WNDRW4500v2 (Netgear 900) router, my ISP is Brightouse Networks (Time Warner), and my OS is Windows 7.
Ever since I got my new router, I haven't been able to port forward anything. Even though I've done this several times before, I've had to go watch tutorials on YouTube and still nothing works. I'm using Norton Anti-Virus 360, and I've made sure that my firewall (or Windows Firewall) is not effecting this in any way.
OK, so first of all, make sure your internal IP in your server.config (or whatever the name of the config file is) is correct. Then, make sure 'port' is set to 25565 - I presume you set up port forwarding such that port 25565 is forwarded to your computer. When you start up your server, watch the log that it outputs - for example, for me, this is a successful server launch:
[16:35:58 INFO]: Starting minecraft server version 1.7.9
[16:35:58 INFO]: Loading properties
[16:35:58 INFO]: Default game type: SURVIVAL
[16:35:58 INFO]: Generating keypair
[16:35:59 INFO]: Starting Minecraft server on 192.168.1.101:25565
[16:36:00 INFO]: Preparing level "mkworld"
[16:36:01 INFO]: Preparing start region for level 0
[16:36:02 INFO]: Preparing spawn area: 25%
[16:36:03 INFO]: Preparing spawn area: 82%
[16:36:03 INFO]: Done (2.727s)! For help, type "help" or "?"
For me, this is a successful server launch, and this will be virtually identical to most servers. Since you're running Hexxit, yours will look much different, as Hexxit loads a ton of mods, but if your server says something like this at any point:
[16:38:59 WARN]: **** FAILED TO BIND TO PORT!
[16:38:59 WARN]: The exception was: java.net.BindException: Cannot assign requested address: bind
[16:38:59 WARN]: Perhaps a server is already running on that port?
...there's a problem there. In this case, I screwed with the setting for my internal IP. If your server starts up normally and does not give any "FAILED TO BIND TO PORT!" error, then check canyouseeme.org (or a similar port checker) to see if the port is open.
...wait a minute, when you do the port check to test port forwarding, you DO have your server up and running, right? If it's not up and running when you test it, in my experiences, port checkers will say the port is closed if the server is down when you check the port.
I haven't edited anything in my config files, and I've made sure that my port is 25565. Yes, I've also made sure my server was running while checking to see if the port works. And no, there were no error messages involving a failed port or failed binding of the port.
I even got this in result:
2014-07-19 15:08:23 [INFO] [Minecraft-Server] Starting Minecraft server on *:25565