Results 1 to 3 of 3
04-12-2006, 23:03 #1-= TeamSpeak User =-
- Join Date
- Dec 2006
Another I can connect but others can't post
I'm guessing I shouldn't be posting this because I've seen other similar posts get axed, but here goes...
I've read the FAQ about others not being able to connect to my server.
I have forwarded 3 different ports as per another post: 8767, 51234, and 14534 using portforward.com.
I have set up a static IP address using portforward.com.
I have disabled my Windows firewall.
I have given others my external IP to try to connect. They can't.
I have tried connecting using my external IP. I can't.
I can connect using my internal IP and so can my boyfriend (our computers are in the same room).
When I connect, everything seems to work fine. Others get the error that "No reply from server. Maybe the server is offline or maybe Teamspeak is not running on it."
I'm not sure what else I can do. Any help would be greatly appreciated.
09-12-2006, 15:14 #2-= TeamSpeak User =-
- Join Date
- Nov 2004
- Depends on the year. Right now Afghanistan.
Try a port scan. Somewhere you have goofed and the communication is being blocked.
If just 1 port fails then try forwarding that port again.
If they all fail look at your firewall again.
09-12-2006, 18:35 #3-= TeamSpeak Addict =-
- Join Date
- Jan 2005
- Cleveland, OH
Generic "my friends/users can't connect" checklist:
1) Are they connecting to your WAN address (www.whatismyip.com)
2) Are the ports forwarded from your rotuer to the TeamSpeak Server on your LAN? (www.portforward.com)
3) Have you made an exception for Inbound UDP traffic on port 8767 in your software firewall(s)? This includes the Windows Firewall which is ON by default in Windows XP SP2
4) Is the server running? (test by connecting to it yourself)
Pointers for you:
* With most home-quality routers you'll never be able to connect to your own external address. They don't like looping back their own traffic. Therefore, you'll (probably) never be able to connect to your own external IP - making this an invalid test/diagnostic.
* Make sure that the forwarding you've done is to the right internal PC. I've seen people mistakenly forward their traffic from the rotuer to. . . . the router again. The router, not having TeamSpeak installed, can't answer TeamSpeak queries.
* Make sure port 8767 is forwarded using UDP and not TCP (optionally you can enable BOTH or ALL - the key is to make sure UDP gets through). The opposite is true for the other two ports.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By Lakusfs in forum [TeamSpeak 2] Server SupportReplies: 3Last Post: 12-08-2006, 20:03
By jmunsters in forum [TeamSpeak 2] Server SupportReplies: 0Last Post: 15-03-2006, 12:49
By Sirius in forum [TeamSpeak 2] Server SupportReplies: 4Last Post: 19-06-2005, 22:49
By boj in forum [TeamSpeak 2] Client SupportReplies: 6Last Post: 19-05-2003, 21:27