PDA

View Full Version : Failing UDP Test


llowman
26-04-2008, 17:20
I have followed the sticky that was posted for setting up TS behind a router. I have set my system to a static IP and port forward all the ports in my Netgear WGR614 v1. TCP and HTTP test pass with flying colors. Have checked my firewall (Windows XP) and everything seems to be right. Like everyone else I can connect to my TS server but the outside world cannot. Any suggestions? Thanks in advance for the help.

BHKai
26-04-2008, 18:22
For the firewall you have the correct type of port selected? 8767 UDP and not 8767 TCP?

Does it work if you connect directly to the modem?

llowman
26-04-2008, 22:01
That is what I am wondering cause I have looked all over the router settings and when I ported it does not give me an option to choose. I have updated my router's firmware. Could it be that this router doesn't allow UDP? Thanks again for all the help.

BHKai
27-04-2008, 18:06
They should allow udp it is just they just have it set to allow all protocols of that number.

Try hooking directly to the modem to see what you get.

llowman
29-04-2008, 19:43
I did as you suggested and plugged straight into my modem and all test passed. With that out of the way I went back into my router and checked everything. All was well then I found this section called Default DMZ Server which was unchecked so I checked the box and set the IP address for the TS server. Everything passes now. But is this wise to leave this up and running this way?

Thanks again for all your help!

BHKai
30-04-2008, 04:58
If you have your firewall properly set then it is okay. If not, then you should really find away to just forward the ports you need.

llowman
30-04-2008, 23:41
THanks for all your help BHKai All good now and up and running.

Rorek_of_Null
01-05-2008, 04:10
Okay, so I'm having the same problem, except DMZ(-ing?) didn't help me.
Here is a list of the things that I've done;

Forward the ports TCP 51234 and UDP 8767 to the proper PC on my network
turned off windows Firewall (and after that didn't work i turned it on and made the ports mentioned above exceptions as well as TS-server itself.)
DMZ(-ed?) the Proper PC on my network to allow all connections through.

I'm out of ideas here, so I'm asking with the utmost respect and hope for someone to please, Please help me.

BHKai
02-05-2008, 12:52
What is the model or your modem? Does it work if you are directly connected to your modem?

ANR Daemon
02-05-2008, 14:52
See if this helps
http://forum.goteamspeak.com/showthread.php?p=172679
It's just a checklist for diagnostics.

I'd also advise to setup real firewall to replace built-in windows one to have better control and diagnostic.

Rorek_of_Null
07-05-2008, 11:41
let me be more specific, I have had TS working on this network before and nothing has really changed except the computer running TS. It use to run on a not-so-good PC, and now it runs on a better PC. I had this problem before but I don't know how I fixed it(I've done everything I did before, but to no avail.).

I have all the ports forward(ed?) to the right computer and the Server DOES show up on the server list(the public search one) but because the UDP fails no one except people on the LAN can connect.

Here are the results of the Test.

Performing UDP test...
» Establish a connection with the server ERROR 3
» Verify that it is a TeamSpeak 2 server ERROR 3
» Perform connection handshake ERROR 3
» Retreive a list of active channels ERROR 3

Performing TCP test...
» Establish a connection with the server OK
» Verify that it is a TeamSpeak 2 server OK
» Retreive the servers global information OK

Performing HTTP test...
» Establish a connection with the server OK
» Verify that it is a TeamSpeak 2 server OK
» Retreive the servers version information OK

PS.
I went to that guide ANR, but I didn't find it particularly helpful, sorry and thanks for trying.

ANR Daemon
10-05-2008, 13:27
It looks that Your "better PC" blocking incoming UDP connections (assuming You have adjusted all port forwardings properly after replacing server PC).
It is, sadly, typical for Win XP.