Results 1 to 5 of 5
-
16-03-2012, 13:07 #1
-= TeamSpeak User =-
- Join Date
- Mar 2012
- Posts
- 3
Using a restricted network: need to inform the admins of the correct fix
I am using a computer on a restricted network regularly, but since I got here Teamspeak has not worked. I cannot connect to ANY server. My primary suspicion is ports, because another program suffered from a similar lack of connectivity that has now been fixed by opening ports. I am not entirely sure what is requred here and I would like to give the server admins the most minimal fix possible, as it is a very large network. Would anyone be willing to help my diagnose the exact fix that needs to be made to the system's settings?
Attempting to view the server list gives me the error "Failed to connect to weblist server". Here is the log for when I try to connect to my regular server:
I read something about 2010 (TCP) and 8767 (UDP) around here. Would the blocking of either of those lead to this problem?17/3/2012 1:52:17 AM ClientUI Info Connect to server: 203.97.27.203
17/3/2012 1:52:17 AM ClientUI Info Checking blacklist
17/3/2012 1:52:17 AM Info Trying to resolve blacklist server
17/3/2012 1:52:17 AM ClientUI Info Blacklist check ok
17/3/2012 1:52:17 AM ClientUI Info Initiating connection: 203.97.27.203:9987 203.97.27.203
17/3/2012 1:52:17 AM Info Blacklist server resolved
17/3/2012 1:52:17 AM Info Data sent to blacklist server
17/3/2012 1:52:17 AM ClientUI Info Connect status: Connecting
17/3/2012 1:52:23 AM Info Blacklist check timeout
17/3/2012 1:52:23 AM ClientUI Info Connect status: Disconnected
17/3/2012 1:52:23 AM ClientUI Info Failed to connect to server, want autoreconnect = 0
Thanks in advance for any help.
-
16-03-2012, 13:23 #2
-= TeamSpeak Guru =-
- Join Date
- May 2010
- Posts
- 6,372
Hello
Little port list for the client:
- 9987 (UDP) for the virtual server
- 30033 (TCP) for the file transfer
- 17385 (UDP) for the blacklist check server
- 2010 (TCP) for the weblist server
-
17-03-2012, 00:35 #3
-= TeamSpeak User =-
- Join Date
- Mar 2012
- Posts
- 3
Thanks for the reply. What about 8767 (UDP)? Should I include it to be safe? Do the errors there confirm that it is a port problem?
-
17-03-2012, 13:58 #4
-= TeamSpeak Fanatic =-
- Join Date
- Jan 2010
- Location
- Secret Base in Arctic Region
- Posts
- 1,187
AFAMK Port 8767 was the default of Teamspeak 2 ...
-
20-03-2012, 05:21 #5
-= TeamSpeak User =-
- Join Date
- Mar 2012
- Posts
- 3
So I contacted the network administrator with the ports I needed open, and I got this reply:
I don't understand what this means. Can anyone translate for me here, and is there any way past it?Unfortunately we cannot enable teamspeak as these ports are required inbound, and we only enable inbound access to our servers.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
Restricted With Poeple
By mrowl12 in forum Server SupportReplies: 3Last Post: 06-09-2011, 08:14 -
Join Power / Restricted Access Group.
By xcalibur in forum Permission SystemReplies: 1Last Post: 13-11-2010, 10:34 -
Restricted Server Access Explained
By Peter in forum Server SupportReplies: 0Last Post: 14-07-2010, 10:47 -
[RELEASE] Client revision check - inform and inform/kick the client
By burnersk in forum ToolsReplies: 14Last Post: 10-01-2010, 00:31


Reply With Quote