Teamspeak connections, no direct connect?

[Stalks]

I could of just missed something in options, but I've spent a while trying to find it to no avail.

My teamspeak and another persons isnt actually directly connecting to our TeamSpeak server. Instead upon issuing a commandline "netstat" it is connecting via the http port 80 to 2 teamspeak.org IPs.

After a clean reboot, with 0 idle processes other than those of common Win2000 services, and Teamspeak connected to our Linux TeamSpeak server hosted at Telehouse. This is the result of a netstat.

http://theqscript.com/stalks/netstat.gif

Is this how TeamSpeak is designed?

[Stalks]

bump

Routing connections thru a "bouncer" adds nearly 1/2 a second to the response due to a 500ms route to bouncer1.teamspeak.org and bouncer2.teamspeak.org ... yet the box running the teamspeak server that I use is only 16ms away.

Please, how can we all directly connect to the server instead of being routed through teamspeak.org first?

[Stalks]

bump

This is ridiculous.

If I block connections to bouncer1 and bouncer2.teamspeak.org, I cant connect to teamspeak.

I want to directly connect to the TeamSpeak server I am using.

Surely this is possible, such a design flaw isnt integrated and permenant?

[Judas]

Thats strange as i block the bouncers and dont encounter any problems. As far as i am aware at least on of the bouncers is just used to determin your WAN IP (as the server attempts to connect to the same bouncers).
According to my believe () the second "bouncer" is the webpost (for servers that is). The client might try to get a serverlist from the second host.

Yet I only allow TS to access UDP 8767 and it works fine for me.

Also the connection to the "bouncer" are just made at startup. TS client never again attempts to connect to them hosts as long as you dont restart it (at least that is my experience, could be wrong with that one though).

Are you absolutely sure that UDP 8767 is open at all times?

[shagghie]

I think it might have to do with you server config. Is it set up for 'public server' or for 'clan server'? i think those are the two options. Perhaps you have it set for public server and that's why it's making those calls to the bouncers. I have mine set to clan server and haven't noticed anything unusual in netstat.exe...

g'luck!