[Tutorial]Port Forwarding (a.k.a. clients cannot connect)

[Tomas]

Okay so i'm bored those answers like
.....
I've done everything [open in Firewall, accept connection in Firewall, set server as trusted in Antivirus, and shut down windowws firewall] I've hosted many game, http, ftp and mysql servers so i know how to open ports and "let someone in". But i dont know how to repair this.

I can confirm that its not working ;-/
Oukey, umm could you test from some machine in your LAN(192.168.1.x) to connect to your teamspeak3?
Could you look into the router/modem log file/page/entries if it has any?

"You have hosted many ... game"... umm, was any of those services provided over UDP protocol? (mostly they are over TCP imho)
And perhaps your provider is blocking UDP in some way to you(firewalling? to prevent p2p).

What is left is remote fixing... if you can't pinpoint&fix it on your own.

[peesde]

I was hosting Counter-strike 1.6 servers and they're using UDP ports [27015 - 27030 < that was my range], Open Tibia Servers [8000 - 9000 < UDP port range] and some more but with Teamspeak3 server i was able to open those ports nad make my server accesable to people from "outside". Problem is that suddenly all "clients" have been disconnected from the server and now noone can connect.
Virtual server:

Cports:

CMD ipconfig /all :

TS requested ip:

All computers from my local network can connect by 192.168.1.102:9988 and i can connect with this address too.
I've readed about my router [Pentagram P 6381 - 3] and all i could find is that nobody knows how to set "port range" so i'm entering just one port per line. Windows firewall is turned off, comodo firewall is turned off and i've just turned off my antivirus.
Don't have any clue what's wrong.
If i gave not enough information please post here what i should post.

EDIT:
My server has been repaired. I dont know how. I was writing edit for this post and my friend told me that it's working.

Regards,

[weebel]

I might try reinstalling my protocols with the server running and see what happens, but I doubt that is going to work. Plus im not sure if the "drivers" are kept on the HD with windows 7.

I've made sure my wan IP is correct also, I was talking to the people trying to connect live. Not to mention they can see me on the server list and still have the failed to connect issue.

I'm using a brand new Cisco router and neither my DSL modem, nor my IP provider are blocking ports. Everything is correctly forwarded. I even temporarily rand my PC as a DMZ with no luck. Every IP addy is reserved on the router so everything that connects always has the same ip so thats not the problem.

Im not new to this, I'm a certified network tech / administrator and have gone over this for hours. I've just decided to give up and assume its a compatibility issue somewhere down the line thats out of my control.

[foley123]

hi
i am running comcast for my internet and have a router connected it is a netgear model wndr3700.
my firewall is pctools and running windows 7 home 64 bit.
i installed the sever no problem but people cannnot connect.
i understand that comcast has one ip starts 69.245.*.*and then netgear assigns ip to both of my computers starting at 192.178.*.*
i have no idea how to get people to connect to my server.
i have a loptop that i connected to my phone to test it and i tried ever single ip that i have available and nothing
thank you for any help you can give

Thread got merged

[maxi1990]

you basically need to forward the virtualserver's udp port(s) to the local ip (192.178.?.?) where the ts3 server is running.
sometimes your local firewall also needs some rules to allow ts3 servers through
Keywords: port forwarding $ROUTERNAME (if you choose to consider google for further information)

[Air SeaTac]

Hoping you've both made typo's, the internal IP's should be 192.168.*.*

[francy222]

Hallo,
I have downloaded and installed team speak server and the client. I can connect to the server typing "localhost" in the server addres textbox.
But no other person can do it, if they type my ip addresse the client say that the connection faliled. I dodn't post any password to the server.
Can someone help me please to find where is the mistake?

Thread was moved

[pillbox1234567]

Hoping you've both made typo's, the internal IP's should be 192.168.*.*

That is incorrect. Though the 192.168.*.* setup is very common for home networks, it is all but universal. In fact, most corporate networks do not use it. I, for one, have set up my network to use 10.156.*.* Some ISPs have default configurations that are not 192.168.*.*

[ARCHI]

Okey so you have one public IP. I don't know how your network works but I'll try to explain it as much as I can.

It's called routing. You need to tell first router (which is directly connected to the internet) to forward ports 9987 udp, 10011 tcp and 30033 tcp to "second" router or direct machine. If it's router then you need to type internal IP of such router. For example if your first router has 1.1.1.1, second 2.2.2.2 and machine with ts 3.3.3.3 then on first router you forward ports 9987/udp 10011/tcp and 30033/tcp to 2.2.2.2 and on second router you do same with IP 3.3.3.3. So It'll be Network=>1Router=>2Router=>TS3 Server

[Air SeaTac]

That is incorrect. Though the 192.168.*.* setup is very common for home networks, it is all but universal. In fact, most corporate networks do not use it. I, for one, have set up my network to use 10.156.*.* Some ISPs have default configurations that are not 192.168.*.*

10.156.*.* is fine since it's part of the private IP range as set out by IANA, 192.178.*.* is part of the public IP range & should not be used on private networks (unless the organisation using it has been assigned IP addresses in this range).

From the IANA website -

"Private Use" IP addresses:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

These address blocks are reserved for use on private networks, and should never appear in the public Internet. There are millions of private networks (for example home firewalls often use them). People can use these address blocks without informing us, so we have no record of who uses which of these addresses.

[jeroentje402]

hello,

i have a problem with my teamspeak server. i did everything what this guy does in this video: http://www.youtube.com/watch?v=jJBnxvttL04&feature=plcp
i portforwarded, added TSS3 to my firewall. but still my friends can't connect.

i have windows vista 32 bit.

this is the log:

2012-07-17 16:35:38.242000|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987 

Thread was moved

[SilentStorm]

Helpful Log really - worth exactly nothing...
DO NOT just strip parts from the log you deem unimportant or unnecessary if you have no clue where or what might cause the error, you can however strip 19 of 20 lines if they are all the same and are logged right after each other...

Anyway whatever Vid you watched (nope won't watch it) either you didn't follow the instructions properly or the video was crap, or there is still some firewall / antivirus blocking the connection.

Read this Thread

[kamild1996]

That TS3 server just pisses me off!
My router is Sagem F@st 3202.
I've forwarded ports 9980-10000 - no results.
I've changed Voice IP to 0.0.0.0, 127.0.0.1, 192.168.1.12 and my current IP - no results.
I've turned off Kaspersky Internet Security - no results.
And a curio - query port, when set to any value, just works.
All other services like Terraria server, Minecraft server etc. works even with antivirus on. Forwarding ports for these just made these things working but with TS3 server... It's strange...
On the logs, I only see this:

2012-07-22 17:04:38.062500|INFO |VirtualServer | 1| listening on 192.168.1.12:9987

Please, help me!

[ANR Daemon]

Did you forwarded UDP or TCP ports?

[ENEMYINSID3]

my friend recently made a server and it works fine when at his house, however, when i go to my house i loose connection. why is that? i cant connect to the server at my house and my house is beside his. he has the server running and hes connected to it but i cant connect to the server. plz help

Thread got merged.
Please use the search function first.