View Full Version : TS server, ports, and problems
Naustradamus
20-12-2006, 07:35
hello .. I've been having a frew problems trying to set up my TS server.
I have placed my modem/router to DMZ mode, but have still gone ahead and forwarded the UPD and TCP ports .. as for HTTP, didn't know how to, but the device lets me forward HTTP ports in general .. not sure if its doing the job .. pic bellow
http://img.photobucket.com/albums/v490/Naustradamus/1.jpg
... also, I've turned off my winfirewall, but for some reason, it stays on .. I've forwarded the ports to it incase, both TCP and UPD .. like I said .. don't know about HTTP forwarding .. pic bellow
http://img.photobucket.com/albums/v490/Naustradamus/2.jpg
and lastly, when I set up my server, it shows on list of servers if you filter it (just use "ank" and look at bottom of list) ... but when my friend tried .. he couldn't get in
and last but not least ... when I tested my server out on a web page (TS connection Test) ... only my TCP ports were forwarded (last time I set everything up .. they didn't work either .. hopes its not a temperary fix)
http://img.photobucket.com/albums/v490/Naustradamus/3.jpg
Anything you can suggest for me to do?
P.S. forgive the links ... I trued to post the pivs themselves .. but this forrum doesn't work with [img ] it seems
WolfStar76
20-12-2006, 14:01
In the first pic, I can see that you've forwarded too many port (8000 - 9000) which is a bit insecure. However, the reason it's not working is because you've forwarded those ports to 192.168.1.1 (which is probably your router) instead of 192.168.1.12 where the other ports are going (which is probably your laptop).
You also mention putting the modem/router in the DMZ, I'd forego the DMZ, especially if you're turning off your Firewall as well - that leaves your computer with NO protection from acctacks. A very bad idea.
Similarly, instead of generically forwarding 51000 - 52000, try simply forwarding TCP 51234. The more specific you are on your forwarding, the more secure you leave your system. Each port left open is another point of attack for people to exploit.
You also have port 80 (HTTP) forwarded, which is fine - if you're running a web server of your own, however it has nothing to do with TeamSpeak. If you want to allow access to the TeamSpeak administration page, change your port forwarding from Port 80 to Port 14534.
The fact that your server is being listed in the "Web Address Book" is irrelevant - that just means TeamSpeak was able to speak "out" to the central TeamSpeak directory. It has no bearing on your ability to receive a connection.
Lastly, while disabling your Windows Firewall is fine for *testing* TeamSpeak, you don't want to leave that off permanently - just like the DMZ, this leaves your computer with no protection. Instead, make exceptions within the firewall for inbound traffic on UDP port 8767, and TCP ports 51234 and 14534 (the same ports you should be forwarding).
In Summary:
1) Remove your DMZ settings (won't make TS work, but is FAR more secure)
2) Change your UDP forwarding from 8000 - 9000 to 8767
3) Change your UDP forwarding from 192.168.1.1 to 192.168.1.12 (this is all that's needed to make TeamSpeak work)
4) Once you're confident people can connect - enable the Windows Firewall, and make exceptions for inbound traffic on UDP port 8767.
You can make the changes to port 51234 and 14534 I mentioned above, but they're only for remote administration of the server - and unless you need to admin it from outside your network, I wouldn't bother. It opens up some security issues in and of itself.
Naustradamus
20-12-2006, 17:41
so, all I haft to do is be more spesific with my ports and it should work?
I'm just making sure cause the only thing you've mentioned up to date was my security ... not my issue.
And aslo, as for DMZ, it was on first and foremost ... I play games, use torrents and such, so placing DMZ on at my router makes it that my PC can do torrents well as well as let my PS3 online withought issues ... my WinXP firewall WAS suppost to be off, but it never does .. so its not off .. and I also have Norton that, even if its not the best, seems to protect me better then WinXP firewall.
Also .. just asking ... did you try to connect to my server? It just appeared to me .. my friend was trying it at a hotspot .. he didn't try any other servers >.>
thanks for the help though! I'll go change the ports right away.
Naustradamus
20-12-2006, 17:48
oohh ... sorry, I just realized that you said specifying the UDP port would help out. I just changed the setting and now the test does show that both UPD and TCP does work.
So thanks!!
lastly though, the HTTP test ... is that just in regards to someone that is using TS with SQL?
I know you can make both work together, but at this point in time, I don't really need that. >.>
again though .. thanks!! ... I'll get someone to test it as soon as I can
WolfStar76
20-12-2006, 17:50
so, all I haft to do is be more spesific with my ports and it should work?
No, if you read what I wrote - being more specific increases your SECURITY.
Pointing your inbound UDP to the PC (192.168.1.12) instead of the router (192.168.1.1) should allow TeamSpeak to get your friends to connect.
I'm just making sure cause the only thing you've mentioned up to date was my security ... not my issue.
You obvisouly didn't read ANY of my post if you think the *only* thing I mentioned was your security.
And aslo, as for DMZ, it was on first and foremost ... I play games, use torrents and such, so placing DMZ on at my router makes it that my PC can do torrents well as well as let my PS3 online withought issues[/quote[
That's a matter of choice I guess. Don't be surprised if you get viruses, spyware, and other problems from running a machine in the DMZ.
[quote] ... my WinXP firewall WAS suppost to be off, but it never does .. so its not off .. and I also have Norton that, even if its not the best, seems to protect me better then WinXP firewall.
Odds are Norton Firewall has already turned off your Windows Firewall and is taking its place. You'll need to make the exceptions I mentioned in the NORTON Firewall instead. (Norton will stop inbound traffic unless/until it's told otherwise).
Also .. just asking ... did you try to connect to my server? It just appeared to me .. my friend was trying it at a hotspot .. he didn't try any other servers >.>
I didn't try connecting to you, and couldn't have even if I'd wanted to, since you didn't list your address, and your routing is wrong. (As I mentioned in my original post - twice).
thanks for the help though! I'll go change the ports right away.
Good luck.
WolfStar76
20-12-2006, 17:52
lastly though, the HTTP test ... is that just in regards to someone that is using TS with SQL?
The "HTTP" test is used to test the Administration page for TeamSpeak - the one that runs on port 14534.
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.