selvikin
27-03-2007, 07:10
On the following FAQ:
Q: Some people can't connect to my server, some can. How to fix?
<http://www.goteamspeak.com/printview.php?id=41>
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 the internet, *CAN* connect to your
server.
* The machine that is running the server has *more* than one
*external* 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.
I'm about to make the changes, now...
1. Do I use the External (WAN) IP address of the server?
2. Do I have to restart the server after the changes???
Q: Some people can't connect to my server, some can. How to fix?
<http://www.goteamspeak.com/printview.php?id=41>
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 the internet, *CAN* connect to your
server.
* The machine that is running the server has *more* than one
*external* 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.
I'm about to make the changes, now...
1. Do I use the External (WAN) IP address of the server?
2. Do I have to restart the server after the changes???