PDA

View Full Version : Single instance of 2.x server on Win2003 w/ multiple IPs

TeamElement
26-01-2005, 00:55
We have a single running install of TS 2.x running on Windows 2003 Standard Server. The server has about 8 IPs bound to the NIC.

Everyone can connect fine to TS via the first IP in the list of 8. However if they try to connect to any of the higher IPs they get the "server not running" message.

However .. IF they disable or "dumb down" their firewall or put their computer on the DMZ, they can connect fine to any of the IPs.

The server is running on the default 8767 port. And the BindToIP1 is not set to anything. There are also no logs on the server when someone fails to connect. Client logs show timeouts.

Ideas?
CheshireCat
26-01-2005, 01:04
I was talking rot. ignore me
guldi
26-01-2005, 11:11
- you sound as if you really need to have TS accessible on all 8 IP interfaces ? If not, simple only use one (=> bind it to this interface)

- A FAQ thread meantion that due to NAT problems it might happen that on such installation a server can not be contacted by all users => use the bindtoIP feature (what happens if you bind it to all IP's... never tested this ?)

- timeout probs might be avoided by setting the clients into debug mode, however your case (with 8 IP Interfaces) sounds quite unusuall => either the TS server gets problems with that many Interfaces or your network setup has some issues ???
TeamElement
26-01-2005, 23:24
TS is running on a web server -- thus the reason for the 8 IPs bound to the NIC (each website has a dedicated IP).

TS is setup on the 4th IP in the list on x.x.x.242 (of x.x.x.239 - x.x.x.247). Yet, people can only connect on .239 (the first IP on the NIC).

Should I send this to TS support?
guldi
27-01-2005, 09:48
Yet, people can only connect on .239 (the first IP on the NIC).
even if you bind it to this IP ?
Should I send this to TS support?
The DEV's should see this thread here. Let's see if we get a feedback here.
TeamElement
08-02-2005, 00:22
Yes, if I use the BindToIP1 to the .242 I assume it binds fine but then noone can connect whatsoever. Any suggestions on this?

Why would binding it to the 4th IP using this method make any difference?
Broder
09-02-2005, 10:29
Hmmm maybe there is a Firewall somewhere between the Users and the Server that only allows the UDP packets to the First IP rather than the 4th ?