Exhausted almost all options, still can't host

[Raeyok]

Okay, so here's my situation in a nutshell.

I used to host all the time. Then I decided to take a break from hosting for a while. I'm now attempting to put a server back up, but for some odd reason, it just won't work. I've tried power cycling/resetting my router and modem and re-forwarding my ports countless times. I don't know what the forget happened between me taking a break from hosting and now, but I cannot host. I have depleted every solution I can think of, and even several from Google searches.

Needless to say, I really need some help here.

The router I'm using is a NETGEAR RangeMax Wireless-N Gigabit Router, model WNR3500v2.

Photos of stuff (sorry about large pieces of whitespace, forgot to crop them):

This is my router's port forwarding page for Blockland:




This is my router's Internet Port information from its status page:




These are all my network adapters (I don't use the LAN because I don't have an ethernet plug in my room):




And finally, my TCP/IP settings:




Any and all assistance that could possibly be given here would be extremely appreciated, I would so love to be able to host again.

If you need me to get any other screenshots/information, please don't hesitate to ask, I would be more than glad to get it/them.

[Ad Bot]

[Bauklotz]

Do you use a firewall? Are you sure that 192.168.1.45 isn't taken by another computer?

[Raeyok]

Do you use a firewall?

Yes, Kaspersky's firewall, but I know for certain that it doesn't restrict Blockland's access to the Internet.

Are you sure that 192.168.1.45 isn't taken by another computer?

Y--... wait. I used to host on my desktop, but we recently upgraded its OS to Windows 7, wouldn't that revert any network adapter settings to default (get IP/DNS automatically from ISP)?

[Bauklotz]

It would revert the settings on the desktop computer, not on the router. If your router supports forwarding the port to a computer name instead of IP address, use that, and turn off the "use this IP address" in TCP/IP settings, and make it select one automatically.

[Raeyok]

It would revert the settings on the desktop computer, not on the router. If your router supports forwarding the port to a computer name instead of IP address, use that, and turn off the "use this IP address" in TCP/IP settings, and make it select one automatically.

Yeah, I just checked the settings on the desktop, it doesn't have settings for port forwarding.

Also, I'm pretty sure my router doesn't have this support feature of which you speak, I most likely would already know about it if the router did have it... yeah it definitely doesn't, I just checked.

I have a question, actually. If I can't get my normal hosting to work, would it be possible to host on my Hamachi network? Again, this is only if I can't get my normal hosting to work again.

[BobSevenSevens]

Set your ending port from 28000 to 28032.

That might work.

[BobSevenSevens]

Sorry about the double post, but here's what my ports are set to:

[Butler]

Set your ending port from 28000 to 28032.

That might work.

It's not that this might work. This will work. He's just an idiot.

[otto-san]

On your Firewall, unblock TCP and UDP ports 28000.

It's not that this might work. This will work. He's just an idiot.

No, that isn't how ports work. It's only really necessary to have one port forwarded on the port you are using. Unless you're trying to host thirty-two servers at once.

[Raeyok]

It's not that this might work. This will work. He's just an idiot.

Then please enlighten me as to why Badspot did it that way in the port forwarding tutorial on the Blockland homepage:

Change one of them to look like this:

Set your ending port from 28000 to 28032.

That might work.

All right, I'll try that.

[Chrono]

You only need port 28000.

Your computer's network settings might have reverted. It's very likely that your LAN IP is not 192.168.1.45

[Raeyok]

You only need port 28000.

Your computer's network settings might have reverted. It's very likely that your LAN IP is not 192.168.1.45

Well, it seems to have been fixed by changing it to 28032, because I have two people on my server right now.

Thanks for the help guys. I'll keep this topic unlocked in case it decides to stop working again.