I'm having port problems again, and I need a solution.

[Conan]

just to clarify - the problems seemed to suddenly start again for no good reason. I am hosting as well on Dragonoid's server, and I looked for an already-open port to host blockland over. I chose 3386 (or whatever it is), the default remote access port, and it worked fine for a week and a half before having trouble with letting people join, even while I was accessing the server and modifying files.

The problem fixed itself, however, and now people can join my server again. The configuration is exactly the same as before. Seems like a weird bug to surface.

[Ad Bot]

[Zeblote]

I chose 3386 (or whatever it is), the default remote access port, and it worked fine for a week and a half before having trouble with letting people join, even while I was accessing the server and modifying files.

Having multiple things listen on the same port doesn't sound like a good idea to me.

[Conan]

Having multiple things listen on the same port doesn't sound like a good idea to me.

given i don't access this server more than once every few days, it seems fine to me. unless drag accesses the server often.

[Goth77]

Having multiple things listen on the same port doesn't sound like a good idea to me.

This isn't really an issue unless both IP's are the same. My brother and I use the same modem for hosting. We both have ports forwarded from 28000 to 28016 but on different local IP's.

1. I own the router

2. How do I do this?

According to Badspot the port forwarding process cannot be explained any further than already is (which is pretty true) but since the tutorial on http://www.blockland.us/portForward is a little outdated I provide you with this

Port Forwarding for Dummies

[Dragonoid.Slayer]

Having multiple things listen on the same port doesn't sound like a good idea to me.

Although the max people at a time is 2 on the server, there has never been a problem with this. When I lend the server the people, they login while I am logged in. Unless you mean running multiple instances of Blockland at the same time, which it still should not be a problem as we are all running on different ports.

given i don't access this server more than once every few days, it seems fine to me. unless drag accesses the server often.

I'm on quite often as a result of the problem.

[Dragonoid.Slayer]

Port Forwarding for Dummies

I just clicked link because I was on phone and stuff. I don't think you understand well enough, or have grazed over these details: I cannot port forward, because I am not local to the server.  It is in a data center, meaning I cannot access the control panel thing or the webpage to get into it.

Regardless, why the heck are my ports getting off? Why is my server regularly breaking?

[Goth77]

I cannot port forward, because I am not local to the server.  It is in a data center, meaning I cannot access the control panel thing or the webpage to get into it.

It doesn't matter what PC you use to log into the default gateway. If you own the router and are connected to it, you can easily log into the gateway even from your phone. Logging into your router is as simple as opening a web browser. Does your computer or phone not have a web browser? You say you own the router, are you physically able to reach it?

[Conan]

nono, its not he can't get on the gateway page. the page rejects all attempts to connect - i tried to figure out why, but i couldn't find anything. chrome returns with the "ERR_CONNECTION_REJECTED" rather than name not resolved or whatever.

[Conan]

noedit:

nono, its he can't get on the gateway page. the page rejects all attempts to connect - i tried to figure out why, but i couldn't find anything. chrome returns with the "ERR_CONNECTION_REJECTED" rather than name not resolved or whatever.

fixed

being local to the server doesn't matter, drag, since you're accessing it remotely. Its like trying to port forward on my computer while my computer is on - it doesn't matter that you aren't actually where I am; you can still find the default gateway, plug it into a web browser, and adjust the settings.

[Goth77]

Its like trying to port forward on my computer while my computer is on - it doesn't matter that you aren't actually where I am; you can still find the default gateway, plug it into a web browser, and adjust the settings.

Nothing you just said made any sense. First of all, when you port forward the computer usually IS on. Secondly, only the person with DIRECT PHYSICAL CONTACT with the router can log into the gateway and forward the ports. That means if the router is in your Drag's bedroom, then only he can forward the ports.

If you are for some reason blocked from the router's admin page, then you might need to actually reset the router. This involves holding the reset button in with a small pin/needle for about 15-30 seconds, then you will be able to log in with the routers factory settings

[Shift Kitty]

In past experiences, whenever a router experienced connection rejections, restarting it helped. In no way a guarantee though.

Nothing you just said made any sense. First of all, when you port forward the computer usually IS on. Secondly, only the person with DIRECT PHYSICAL CONTACT with the router can log into the gateway and forward the ports. That means if the router is in your Drag's bedroom, then only he can forward the ports.

Some routers do have an optional remote access.

[Conan]

Nothing you just said made any sense. First of all, when you port forward the computer usually IS on. Secondly, only the person with DIRECT PHYSICAL CONTACT with the router can log into the gateway and forward the ports. That means if the router is in your Drag's bedroom, then only he can forward the ports.

If you are for some reason blocked from the router's admin page, then you might need to actually reset the router. This involves holding the reset button in with a small pin/needle for about 15-30 seconds, then you will be able to log in with the routers factory settings

okay i think i've confused you

Drag's server is a remote access server running on Windows XP (or 7, but the style is classic). When remotely accessing it, you modify files and do changes through a "desktop" and can open chrome/whatnot.

His server is not (conveniently) physically accessible from where he lives, and the router is almost certainly controlled by the datacenter/server housing/colocation center the server is in.

[Goth77]

In past experiences, whenever a router experienced connection rejections, restarting it helped. In no way a guarantee though.
Some routers do have an optional remote access.

Right, but you can't physically hold in the reset pin from a remote connection. Although, most routers have the "restore factory defaults" option somewhere, but isn't always guaranteed to work properly

okay i think i've confused you

Drag's server is a remote access server running on Windows XP (or 7, but the style is classic). When remotely accessing it, you modify files and do changes through a "desktop" and can open chrome/whatnot.

His server is not (conveniently) physically accessible from where he lives, and the router is almost certainly controlled by the datacenter/server housing/colocation center the server is in.

Hmmm. Well If you can't access the router's log-in page through your web-browser then you're out of luck. You need to be in the default gateway to forward ports effectively

[Dragonoid.Slayer]

His server is not (conveniently) physically accessible from where he lives, and the router is almost certainly controlled by the datacenter/server housing/colocation center the server is in.

Well, the router is owned by me, but it is not like.. down the street from me(The datacenter). If worst comes to worst and I MUST port forward, I am capable of driving down there and logging on locally. But the problem is that I don't want to do this often, as the problem occurs "often". That's why I stated multiple times in OP that I would like to know the solution other than port forwarding. If port forwarding is the only solution, well then rip.

[Goth77]

Setting a static IP at your workstation and Port forwarding is the only permanent solution to your hosting issues. O  nce you do so, you shouldn't have to forget with it ever again unless your router somehow erases itself