Cannot run TS Server behind Routers

[Iceman]

Here's what I got:

-Server version: 2.0.20.1 Win32
-Windows HP Home Edition Service Pack 2
-Direct X 9.0
-Sound: VIA AC'97
-Tried on both a D-Link & a Linksys router, Neither works, from 2 different locations, can you believe it? =(

After reading the FAQ's and the Server hosting tutorials:

1) Re-installed both TS Server & client Apps.
2) Forwarded all applicable ports on the routers in question (8767 UDP, 14534 TCP, & 51234 TCP as per your FAQ, & directions from portforward.com).
3) went to whatismyip.com and got my WAN IP.
4) Made port exceptions on my windows firewall (then turned it off altogether). No other firewalls running.
4) Started TS Server & changed settings (name, etc.)
5) went to server.ini file ang put WAN IP on boundtoip1= (If I do this first, i cannot log on, or start the server).
6) Client can see server, but cannot connect, from ANY location! I even have some buddies helping me, they cannot connect either, but they can see the server.

here's what we see:
Error: No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

Am i missing something? I would REALLY appreciate any help you guys can give me!

[WolfStar76]

Check any software firewalls you're running (NOT the firewall on your router) and make an exception for port 8767 inbound.

Sounds like your firewall (Windows Firewall, Symantec, Zone Alarm, or any one of numerous others) is blocking inbound connections (as it should).

And THANK YOU. I think yours is the first 100% legible post asking for help in a reasonable way, in the proper forum I've ever seen. My faith in humanity is being restored.

[Butcher]

I also found this post nice and refreshing. As the post indicates iv'e followed all of the steps taken by the poster, icluding setting winxp's firewall ports!.

Any ideas, i can see the WAN IP teamspeak server but cannot access it!! For the curious its 86.128.108.247:8767 ']['eam>'A'. Cant understand really as all the help found here is perfect!

No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

^^ is all i get!?

[Iceman]

Thanks for the compliment, I know you guys try your best to help, and thats what counts .

You did give me an Idea, I did turn off windows firewall, but I also have spybot, AdAware, and a program called Anonimity 4, maybe they have something to do with it? I will mess with those and see what comes out of it...

[WolfStar76]

I also found this post nice and refreshing. As the post indicates iv'e followed all of the steps taken by the poster, icluding setting winxp's firewall ports!.

Any ideas, i can see the WAN IP teamspeak server but cannot access it!! For the curious its 86.128.108.247:8767 ']['eam>'A'. Cant understand really as all the help found here is perfect!

No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

^^ is all i get!?

Nothing comes to mind, other than to double-check your port forwarding and make sure you've got port 8767 pointing to the LAN IP of the computer running TeamSpeak Server (If it's the only computer on your network the IP is *probably* 192.168.0.100. Also - since you're INSIDE your network, you won't be able to connect to the WAN address (assuming you're hosting the server and running the client on the same box, or both are on computers on your network and not hosted by a 3rd party).

Thanks for the compliment, I know you guys try your best to help, and thats what counts .

You did give me an Idea, I did turn off windows firewall, but I also have spybot, AdAware, and a program called Anonimity 4, maybe they have something to do with it? I will mess with those and see what comes out of it...

Spybot S&D and AdAware don't, to the best of my knowledge, do anything more than scan your computer for programs they know to be bad. I can't speak for Anonimity 4 as I'm not familiar with it, however, if it does any kind of IP or port hiding/spoofing/changing it could ver easily be the cause of your issue.

Same as suggested for Butch, however, double-check your port forwarding.

Also - for both of you, assuming you're running the Server and Client on the same PC do you connect okay via either 127.0.0.1 or your internal LAN address? If so that at least tells us the server is working and accepting connections.

[Butcher]

I can only connect to 198.168.0.X if i dont add the WAN address to the server.ini file? If i add it it gives the same response as the WAN connection.

I'm running both teamspeak server and client on the same PC ? will this cause me problems? If so i could easily move either to another? Means having to get off my seat though!?

[Iceman]

You were right, I didnt see anything that either Spybot or adaware would do to mess up things.

I uninstalled a4, but didnt affect anything.

I got a little farther, I went on belarc.com, ran the advisor, and found that my LAN IP was a bit different than I anticipated??

My normal LAN IP is 192.168.1.177

The one belarc advisor said I had was 192.168.1.177 / 24 ?????????

I dont know whats up with the slash-24, but I put it in the server.ini file anyway. I was at least able to connect via the localhost:8767 method. I am currently waiting for one of my buds to see if they can connect now, but they wont get home until later on. I will let you know what happens!

[WolfStar76]

I can only connect to 198.168.0.X if i dont add the WAN address to the server.ini file? If i add it it gives the same response as the WAN connection.

I'm running both teamspeak server and client on the same PC ? will this cause me problems? If so i could easily move either to another? Means having to get off my seat though!?

I'd skip adding the WAN IP to the .ini - that really only needed in a configuration where you have two network cards in the same PC and want TeamSpeak to be bound to one specific interface and not the other (at least, that's how I understand it - don't use that option myself, so I can't guarantee I'm right on that one).

If you're able to connect to your LAN address, make sure you have your port forwarding on the router set to that same IP, and that you don't have a software firewall rejecting inbound connections on 8767. That *should* be all it takes to get the world connected to you.

And its fine to run both the server and client on the same box. I used to run that way myself.

[WolfStar76]

You were right, I didnt see anything that either Spybot or adaware would do to mess up things.

I uninstalled a4, but didnt affect anything.

I got a little farther, I went on belarc.com, ran the advisor, and found that my LAN IP was a bit different than I anticipated??

My normal LAN IP is 192.168.1.177

The one belarc advisor said I had was 192.168.1.177 / 24 ?????????

I dont know whats up with the slash-24, but I put it in the server.ini file anyway. I was at least able to connect via the localhost:8767 method. I am currently waiting for one of my buds to see if they can connect now, but they wont get home until later on. I will let you know what happens!

/24 is CIDR notation. Essentially it's another way of listing your subnet address.

Are you able to connect to yourself? Either by using the address 192.168.1.177 or "localhost" 127.0.0.1? If so, we just need to figure out what's stopping the world from connecting.

Make sure that any port forwarding rules you've created on your router are actually "Enabled" or otherwise "On".

I've seen some routers that allow you to create a rule that is then defaulted to "disabled" which is silly and self defeating, but, who'm I to critisize?

[Iceman]

Set Your Static IP

Set Your Ports On Router 8767(udp),51234(tcp),14534(tcp)

Set your firewall to allow these ports incoming.

Install Client and Server Software, run and set-up both.

Dont try and connect to your WAN address! as you cant!!

Do make sure you can connect to localhost:8767

lol what if I have done all this already?

I can connect with either the LAN IP or the localhost methods fine, but when others try to connect using the WAN address, they cannot. (not within the LAN, of course.)

Do you think the problem might lie with the DSL boxes? for example, at home I have a Westell DSL box, and at the office I have a Netopia box, wich then connect to the routers. Can they be the ones causing all the trouble?