Cant connect as TS2 Client behind NAT

[Lempo]

Hi,

I'm trying to connect to TeamSpeak2 server as a client, but it doesn't work.

The server is on (there were 3 other dudes in while i tried to connect) and if I ping the IP (62.241.204.20) from ms-dos I got the response in 49 ms.

My PC's operating System is Windows XP personal.

My ADSL-modem is Telewell TW-EA715, that has inbuild hardware firewall. It NATs internal IPs. So when my computer's dynamic IP is for example 62.142.15.137 its internal IP is always 192.168.7.2.

I do NOT have any software firewalls like ZoneAlarm or XP's own firewall activated.

What's wrong?


Here is the message shown on TeamSpeak 2 GUI:

[22:25:34] Connecting to 62.241.204.20:8767
[22:25:37] No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

*** And the server really is ONLINE, and TS is running on it!

And these lines were written in log file:
---------------------------------------------------------------
-------------- log started at 27-08-03 22:25 -------------
---------------------------------------------------------------
27-08-03 22:25:27,2988,DEBUG,All,Startup,Client version 2.0.31.55
27-08-03 22:25:27,2988,DEBUG,ProcedureInfo,Client Open,Creating and starting threads
27-08-03 22:25:34,2988,DEBUG,ProcedureInfo,Client Open,host 62.241.204.20 resolved to 62.241.204.20
27-08-03 22:25:34,2988,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
27-08-03 22:25:34,2988,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
27-08-03 22:25:37,2988,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait

[Toverli]

I have the same probs. And when i browse the forum many others. BUT NO ANSWERS :(

[Lempo]

Yep...no solution yet found for this problem. The closest match was this:

If you are running client, you must allow
Outboud UDP on port 8767
Inbound UDP on port >=1024

On the client side, most firewalls (NAT routers) will not require special mapping for the client to work as the outbound connection to the server will allow the subsequent inbound connections.

BUT HOW TO DO THIS. I contacted Telewell router deliver, and he said, I should upgrade ADSL-modem's BIOS and open/forward those ports. Now there's a new BIOS in my router and I have forwarded ports 8767/UDP and 1024/UDP. Without any results. I still can't connect any TS server!

:confused:

[Merk]

Welp, some bad news. You basically have to open up all udp ports to get this thing to work behind a NAT. Yes, it uses port 8767 server side, but the clients dynamically asign their local ports to whatever 0-65535. Thus, if you just have port 8767 open and have 8767 forward to your server you will never be able to get access outside of the NAT. Download tdimon from the url below and run it on your server and client and you will see what I mean.
http://www.sysinternals.com/ntw2k/freeware/tdimon.shtml

Even putting your server in the DMZ does not work, although linksys says it should. Sucks, but what you can do is have all udp ports forward to fake ip addesses and then have udp 8767 go to your server. I would also think about getting some type of firewall software on all clients. Gotta run wide open on udp or you will have problems. Oh yeah, if you are running XP Prof like me you have to add an entry to open 8767 in it's firewall also

[guldi]

@Merk
ARGS !!! What are spreading here ???

CORRECTION:

NAT is kind of a filter which is not letting in ANY connection (unless it is forwarded by a port forwarding rule). But it's letting out any connection (unless no packet filters are set).

Clinet:
The client try's to connect to a server on port 8767 (default) so this is a outgoing connection => not blocked !
The NAT "filter" is now awaiting an answer from the requested IP of the server. If the answer comes, it is AUTOMATICALLY forwarded to the requester IP on one of the ports between 1024 - 65535 (Port is choosen by server) => you do NOT need any rules in your router for this cause NAT is handling this connection now as established and related !


Server:

As the server is not doing a connection request (the client is doing this) it can not be reached behind a NAT => you need a port forwarding for the TS server port (8767 default). But you do NOT need a rule for the outgoing traffic of the server (unless you use no other firewall, packet filter).


There are different NAT (S / D- NAT / MASQ) but if you buy a standart DSL / cable router you can be 99 % sure you have a NAT working as describe above.


@Lempo
You can ping the IP of the server, but can you reach the server IP on it's destination port ? you can test this with a port scanner. You're not running any packet filter in your router ?

[Lleb_Kcir]

lem i was having a simular issue, but it was random at my end. turned out the be my POS linksys router. got rid of that POS and picked up a SMC7004FW no more issues.

the NAT on the linksys router is pathetic. you have to jump though all sorts of hoops to get things working properly.

basicaly if the server is behind a NAT router and the default port is configued to be mapped by the NAT router you are set.

one thing you may be missing on your connection is the :8767 at the end of your IP.

example

123.123.123.123:8767

without the :8767 at the end it may give you just that error. try putting the port at the end of the IP of the server. that should help i hope.

[Lempo]

Heh,

Thx for all of You... and sorry. The real problem wasn't NAT, it was me. My ADSL-operator (Saunalahti) had shutted down all UDP-ports. I changed this on the operators admin page and now everything works like a dream!

Lempo