Able to connect to TS server on internal network, but not through the internet??

[gibbo]

Hey All, I have a TS3 server running on a Debian virtual machine.
It runs a static IP, on the internal network.

I can connect from another workstation to the server using the local IP address.
When I try to connect from the same machine, via my domain name, I can see the server and attempt a connection, but I never actually get onto it.

Client log:
<19:08:18> Trying to resolve hostname www.xxxxx.net
<19:08:22> Trying to connect to server on www.xxxxx.net
<19:08:28> Failed to connect to server

4/08/2012 7:18:41 PM ClientUI Info Connect to server: www.xxxxx.net
4/08/2012 7:18:41 PM ClientUI Info Trying to resolve www.xxxxx.net
4/08/2012 7:18:41 PM Info SRV DNS resolve unsuccessful for "_ts3._udp.www.xxxxx.net"
4/08/2012 7:18:41 PM Info No SRV TSDNS found at "_tsdns._tcp.xxxxx.net"
4/08/2012 7:18:42 PM Info DNS resolve successful, "www.xxxxx.net"=60.xx.xx.xx
4/08/2012 7:18:45 PM ClientUI Info Lookup finished: 60.xx.xx.xx 9987 www.xxxxx.net 0 0
4/08/2012 7:18:45 PM ClientUI Info Resolve successful: 60.xx.xx.xx:9987
4/08/2012 7:18:45 PM ClientUI Info Blacklist check ok
4/08/2012 7:18:45 PM ClientUI Info Initiating connection: 60.xx.xx.xx:9987 www.xxxx.net
4/08/2012 7:18:45 PM ClientUI Info Connect status: Connecting
4/08/2012 7:18:45 PM Info DNS resolve successful, "blacklist.teamspeak.com"=80.190.225.139
4/08/2012 7:18:51 PM ClientUI Info Connect status: Disconnected
4/08/2012 7:18:51 PM ClientUI Info Failed to connect to server, want autoreconnect = 0

Im getting all the way through to the target machine, I can see the traffic using tcpdump:

19:08:21.748078 IP 10.1.1.5.60172 > 60-xx-xx-xx.static.xx.com.au.9987: UDP, length 175
19:08:22.265348 IP 10.1.1.5.60172 > 60-xx-xx-xx.static.xx.com.au.9987: UDP, length 175
19:08:22.965191 IP 10.1.1.5.60172 > 60-xx-xx-xx.static.xx.com.au.9987: UDP, length 175
19:08:23.965265 IP 10.1.1.5.60172 > 60-xx-xx-xx.static.xx.com.au.9987: UDP, length 175

It just doesnt connect. Weird.
But like I say, go in the internal IP and it connects with no issues.

Can anyone help?
Thanks in advance.

[SilentStorm]

I don't know tcpdump or how it displays data but to me that looks more like outgoing traffic from your internal IP to some static IP from your ISP (which according to you is your own).
Many Routers don't like opening connections to the internet that will resolve back to themselves, which is why the connection fails if you use your public IP or a Domain that resolves to that IP.
In addition to that you need to forward Port 9987 UDP to the LAN IP of the TS3 Server.
As long as others not inside your LAN can connect using your WAN IP everything is fine, you yourself can always just connect to the LAN IP.

[Air SeaTac]

You will (usually) never be able to connect to your external IP (which I presume www.xxxxx.net resolves to) from your internal network, routers don't have that ability (as I said, usually). I'm not familiar with tcpdump but I'm guessing all that's showing is packets leaving your machine, I don't see any evidence that they're actually reaching the target machine

[gibbo]

Yep, sorry guys, but I can resolve and connect to internal stuff via the outside works with everything else I'm running.

Had someone external confirm this morning that it doesnt work for them either.

Any other ideas?
Thanks for the replies so far!

[SilentStorm]

In addition to that you need to forward Port 9987 UDP to the LAN IP of the TS3 Server.

You forgot that ^^

[hawk4base]

Yep, sorry guys, but I can resolve and connect to internal stuff via the outside works with everything else I'm running.

Had someone external confirm this morning that it doesnt work for them either.

Any other ideas?
Thanks for the replies so far!

Check your firewall settings first,allow port 9987 for in and outbound service .
2nd step check youre router/modem .you may have to modyif the settings in the router firewall and maybe you have
to asing your lan ip as target.

see link screenshot of my setup
https://dl.dropbox.com/u/74874771/ts...p%20router.jpg