TS2 not working behind NAT TS1 Does work

[The-Priest]

Hi There,

Just like the thread say's.

Ive got a TS2 server running on my server but nobody can connect to it, but if i start a TS 1 Server it works fine so it cant be that the ports are worg because TS 1 usses the same ports !!!!

I've also opend the other ports but that doesn't help either

Can someone help me please ? because our clan would realy like to use TS2 instead of TS 1

I have also played with the BoundToIp setting but to no avail
Also what i noticed is that in TS 1 i can connect from the Lan and others from the Inet, but if i use the Boundtoip in TS 2 and fill in my outside ip adress i can't join from my lan, if i fill in my inside ip address i can but nobody can join from the Inet so i emptied the Boundtoip setting again as it is by default
I hope you can help.

Server Name = [GNL] Clan Server if you wish to try.


Specs of server :

Dual P3 450
256 MB ram
24 Gb Scsi Total
TNT2 32 Mb
100 Mb nic

[Broder]

From you post I am not 100% certain if you know what NAT is ? You should fill in your local IP in the TS2 ini file IF any and then set your Firewall to send all packets to post 8767 to this IP.

Technically that should work as I doubt TS2 cares where the packets comefrom. Also I guess you have to set the default gateway on the TS2 Server to the IP of the Firewall so TS2 shoots out all packets over that IP first.

Also if you are on 2K ( which I recon due to dual proc ) rightclick Network Neigbourhood -> Advanced -> Advanced Settings -> Adaptor Bindings. Make sure the LAN Connection to the TS2 Server is on Top so the packets go there first.

I am sure something similar can be doen on LInux as well but I have NO idea how :-)

Broder

[The-Priest]

Hi Broder,

I've done the NAT setup correctly because the TS 1 server Does work The boundtoip option in the Server.ini file of TS2 Server is empty again since that did'nt work

The NAT is setup is at follows:

TCP inside_addres:8767 Oudside_addres:8767
UDP inside_addres:8767 Oudside_addres:8767

So all trafic that want's to connect to my TS 2 server is linked to to the internal ip of the machine running TS2 Server.

This same setup works for TS1 server But not for TS2 Server

So that's my problem

Hope to hear from you

[N. Werensteijn]

ts2 only uses 8767 udp, not tcp

[The-Priest]

Sorry my mistake i meant the udp port tcp is udp +1 isn't it ?

So that does stand correct since TS 1 DOES WORK !!!!!

So NAT Aint the problem i think !!!!

I'ts somthing els

Please help

[Broder]

Hmm..I discovered though going trough a router that TS2 Server picks up the external IP as well. So have you tried to put the INTERNAL IP into the ini File of the TS2 Server to bind it to that ?

If that doesn't work either I'm out of ideas m8..sorry

Broder

Oh..btw don't forget to restart the Server after changing the .ini

[raru.kaycee]

theres no tcp port in ts2
the only thing you need ist to forward udp 8767 to your server
and again : DON'T fill in any adress in the boundtoip var
IT WON'T WORK!

and its sure no general NAT Problem cause it works just perfect behind my NAT-Router (i remember that was the intention of TS.. a voice chat prog that works just perfect behind routers )

[0[5BT]

Whilst I've not tried TS1 server behind my NAT'd router I aslo CANNOT get TS2 to accept connections externally. I notice that one of the guys in the TS1 forum has posted about TS2/NAT issues also. I've also tried altering the .ini file settings but to not avail.

I wonder if one of the peeps who can get this to work, would kindly do a quick 'HowTo' for TS2 via NAT. I'm sure its something reasonably obvious but it seems a number of us can't get it working properly....

Cheers

Barren

[BryL]

For a Cisco router with NAT the command for forwarding the port would be:
set nat entry add "inside IP" 8767 "outside IP" 8767 udp
write
reboot

This is working well for me

Bryan

[Sudd]

I've had this problem ever since I bought the NAT, and I managed to fix the problem once but I forgot how I did...And when I reseted the device because of some other problems I didn't manage to get it all to function as before... Now when I know exactly how I did I will share it to the rest of the world... First of all you'll have to forward the port needed (UDP 8767), then you'll have to allow remote users to ping the device... And last of all, if your computer in the network you're using have a specific IP Address Pool Range in the DHCP settings, try to disable the DHCP function... Then you should be all set and good to go.... Have fun...


EDITED by Guldi: Ups, that's an old (solved) thread. Port forwarding is done according the specific router manual. However, what you propose is a good idea to try (no DHCP, try to ping the WAN IP) but for the port forwrding is no general solution which work for all routers => that's why we don't cover each router here => check a router forum or betetr read the manual
=> CLOSED !