Teamspeak on a Windows router

[barrettr]

I'm running teamspeak 2.1.20.0 on a windows 2003 SP1 server which is functioning as a router. This machine is directly connected to the internet and to a LAN with two separate NICs. This server/router also runs a web server and a Counter Strike: Source server. The web server and the Counter Strike: Source server are both always accessible to clients on the internet and the LAN. This server is configured to allow all incoming connections from the internet and the LAN (ie no packet filtering). The fact that the web server and the Counter Strike:Source are always accessible from clients on the LAN and the internet suggests that both NICs in the router are functioning normally.

I was able to install Teamspeak on this server (router), but it behaves erratically. Sometimes it allows connections from the LAN, but refuses connections from the internet. Other times it allows connections from the internet, but refuses connections from the LAN. At still other times it allows connections from both the internet and the LAN. All of these different levels of teamspeak functionality arise with no changes being made anywhere. The only signal that I get that correlates to the different levels of funtionaliity is that teamspeak's list of IP addresses will sometimes display three entries (one for each IP address and one for the external IP address) and at other times it will only display one IP address and the external IP address in it's list of IPs. This implies that it's having trouble figuring out which NICs to answer when requests come in. My goal is to have teamspeak running reliably on both NICs that I have in the router (the NIC for the internet and the NIC for the LAN). Is there some way to force Teamspeak to allow connections on both NICs all of time? Are there setting that I can put in server.ini to do this? If so, what is the syntax that is needed?

Thanks,
Ron
Ron.Barrett@AHHCBiz.com

[guldi]

the default behaviour should be to listen on all "detected" interfaces however you can bind it in the server.ini to listen to only one specific interface. You migt try this. Syntax should be selfexplanable when you open that config file. Else feel free to post again.

[barrettr]

Thank you, yes, I have seen the BoundToIP=(IP Address) which is good, but I'm trying to get Teamspeak to always listen on two NICs. I have tried specifying BoundToIp1=(IP address 1) and BoundToIP2=(IP address 2), but that doesn't have the desired effect of forcing Teamspeak to listen on two NICs. The problem appears to be that the automatic detection of NICs isn't working reliably on my router. It seems that only Teamspeak's development team would know if there is a way to force it to listen on more than one NIC. Is that possible? If it is, what do I need to do in order to make it do that?

Thanks,
Ron