YuriVA775
26-08-2006, 00:59
Q: Some people can't connect to my server. How to fix?
A:
Symptoms:
* People who are using a home router (NAT) CAN'T connect to your server, but they CAN connect to other servers.
* People connected directly to internet, CAN connect to your server.
* The machine that is running the server has more than one ip number.
The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary ip). Nat routers don't know what to do with this foreign incoming data (unknown ip+port), and drop the packets.
Solution:
* Open the file server.ini that is created in the same directory where the server executable is located.
* Look for the following line in section [Main Config]:
BoundToIp1=
* Modify it like this:
BoundToIp1=213.202.254.117
This will make the server listen and send only on the specified address. Even easier is to let the clients connect to the primary IP of the machine.
Note: You can bind the server to multiple IP addresses by adding additional BoundToIp options (i.e. BoundToIp2, BoundToIp3, etc.) to your server.ini.
Does the IP have to be the one listed or is that an example?
A:
Symptoms:
* People who are using a home router (NAT) CAN'T connect to your server, but they CAN connect to other servers.
* People connected directly to internet, CAN connect to your server.
* The machine that is running the server has more than one ip number.
The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary ip). Nat routers don't know what to do with this foreign incoming data (unknown ip+port), and drop the packets.
Solution:
* Open the file server.ini that is created in the same directory where the server executable is located.
* Look for the following line in section [Main Config]:
BoundToIp1=
* Modify it like this:
BoundToIp1=213.202.254.117
This will make the server listen and send only on the specified address. Even easier is to let the clients connect to the primary IP of the machine.
Note: You can bind the server to multiple IP addresses by adding additional BoundToIp options (i.e. BoundToIp2, BoundToIp3, etc.) to your server.ini.
Does the IP have to be the one listed or is that an example?