My server's problem.

[zhenpeng14]

My server doesn't let anyone connect, until I connect using "localhost" on the same computer where I'm hosting the server, when doing that anyone can connect mean while I'm connected with "localhost". If I disconnect and a time pass, the server will kick everbody connected and then will stop emitin the server until I connect again.

 

[Flakeyhooves]

First off, did you forward a port for people to connect to your server? No one can join unless you have a port opened for people to connect to.

 

[zhenpeng14]

First off, did you forward a port for people to connect to your server? No one can join unless you have a port opened for people to connect to.

Yes, I did. If I'm not connected with "localhost" on the same computer running nobody can join. But If I'm on the server, anyone could enter while I'm connected. Also I can't connect from another computer on the same network to my server. Did you read what I said?

My server doesn't let anyone connect, until I connect using "localhost" on the same computer where I'm hosting the server, when doing that anyone can connect mean while I'm connected with "localhost". If I disconnect and a time pass, the server will kick everbody connected and then will stop emitin the server until I connect again.

 

[jianmingyong]

Yes, I did. If I'm not connected with "localhost" on the same computer running nobody can join. But If I'm on the server, anyone could enter while I'm connected. Also I can't connect from another computer on the same network to my server. Did you read what I said?

Well you are same as me. My server stop accepting new player after 15 minutes of inactivity but won't kick anyone out.

But of course my server is done through a more easier method call port triggering. It will do port forward when it is in used while it will close the port automatically if it is unused.

More safe but come with a price

 

[nilllzz]

Well you are same as me. My server stop accepting new player after 15 minutes of inactivity but won't kick anyone out.

But of course my server is done through a more easier method call port triggering. It will do port forward when it is in used while it will close the port automatically if it is unused.

More safe but come with a price

Port triggering only makes sense if you have a small amount of ports and a lot of hosts behind your NAT device, as it automatically opens ports for those hosts that need them.

If you have one static host, then you can just open the port via port forwarding to the host, when the host does not accept the data sent on a port, then nothing happens, there's no security problems involved.
Port triggering might take longer to configure once the service got taken down, because your NAT device might need to readjust itself to the host.