Results 1 to 7 of 7
-
06-11-2006, 22:07 #1
-= TeamSpeak User =-
- Join Date
- Nov 2006
- Location
- Australia
- Posts
- 4
Using say port 8081 for the server, Client won't connect
Sorry if this has already been asked before but I am having trouble with the connection when I change the server port from 8767 to anything else. I have seen other threads with similar problems but they are not realy changing the running port from the defaults. I have even tried it by running the server and client on the same PC and connecting using 127.0.0.1 and it does not connect. I have had a look at the server.ini but there are only entries for the UDP server port. This is what my server.ini looks like:
[debug]
MessageTypes=LMTALL
MessageDepths=LMDALL
[Main Config]
ExternalIPDectection=1
HTTPServer Port=14534
HTTPServer Enabled=1
DateTimeFormat=dd-mm-yyyy hh:nn:ss
TCPQueryPort=51234
AllowedClientNameChars=
DisAllowedClientNameChars=()[]{}
BoundToIp1=
[WebPost]
AdminEmail=na
ISPLinkURL=na
ISPName=Private
ISPCountryNumber=5112
Enabled=0
PostURL=
ListPublic=0
UserAgent=teamspeak
[log]
access_r=0
access_u=0
channel_registerred=0
channel_unregisterred=0
sa=0
chat=0
kick_server=0
kick_channel=0
[Spam]
max_commands=10
in_seconds=2
I understand that the client uses a huge range to try to connect but the client still won't connect even when running on the same PC. Also I tried to disable all firewalls, antivirus on the PC and still no go. When I change the port back to 8767 via the webadmin it connects fine.
The reason I want to change the server port is that I cannot connect to it from work as it is a big government agency and only have a very limited number of ports open and I would be knocked back if I requested to open the port.
I am running the teamspeak server at home on a 1.5Mb adsl connection so if I was to run it, would I just need to port forward 8081 or whatever port I want to use so long as it is the same as the port the server is running on or are there other ports I need to trigger or forward.
Also is the client configurable to connect on a certain port or does it just use the huge range as a search to see what port the server is running on.
If anyone could explain it better to me that would be appreciated.
PS: I have read the manual about the router configurations which says it is configurable but as yet haven't been able to do it.
Cheers
Justin
-
06-11-2006, 23:02 #2
If you change the port number away from the default port, you'll have to tell the client what new port you're using.
Example: Since you're running the client and the server on the same box, you'll need to change from connecting to "127.0.0.1" to "127.0.0.1:8081".
Likewise, users connecting to your server via the WAN will need to connect to xxx.xxx.xxx.xxx:8081.
Additionally, since traffic will be coming in on port 8081 instead of 8767 you'll need to change all your port forwarding and firewall exceptions to use port 8081 in place of 8767.
Give that a shot, and let us know how it goes.
-
07-11-2006, 01:20 #3
-= TeamSpeak User =-
- Join Date
- Nov 2006
- Location
- Australia
- Posts
- 4
Exactly correct. It works on my DEV system so I will see how it goes on my live system tonight.
Thankyou WolfStar76
-
07-11-2006, 16:37 #4
Glad to help.
-
07-11-2006, 22:01 #5
-= TeamSpeak User =-
- Join Date
- Nov 2006
- Location
- Australia
- Posts
- 4
Actually it is still working from home and from a friends place but the corporate network that I work for must not have any UDP ports open as I have just come to work and it doesn't seem to connect even when I am running it on port 81 which I know works for TCPIP as I was running another service on that port before and could get to it.
So maybe this product unfortunately won't work for me.
If there was maybe a web based client that used TCPIP and not UDP then it would definitely work.
I'll keep looking around.
Thanks
PS: Great software though
Cheers
Justin
-
07-11-2006, 22:35 #6
I don't know that you'll find *any* voice application that doesn't use UDP.
Voice has an acceptable loss paramater, you don't need every packet to come through.
What's more, TCP/IP has to assemble the packets in order, which would mean adding delays when waiting for packets to come in that haven't ben received yet.
In general it wouldn't be pretty for voice, but good luck all the same.
-
07-11-2006, 22:48 #7
-= TeamSpeak User =-
- Join Date
- Nov 2006
- Location
- Australia
- Posts
- 4
I have found another bit of software that I will see how it goes called BigSpeed Voice Chat SDK. Not sure how it will go but I will test it out. There is also a video chat.
I'm not trying to plug their software but it is another option. If this post breaches any rules I will understand if it is removed.
http://www.bigspeed.net/index.php?page=bsvoichatsdk
Cheers
Justin]
Update: I just found out it uses TCP/IP 2222 and is also configurable to whatever port you wantLast edited by jckruger; 08-11-2006 at 03:58.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
Jdawgg's Guid to Starting a TeamSpeak 2 SERVER
By JD in forum [TeamSpeak 2] Server SupportReplies: 21Last Post: 14-08-2008, 14:54 -
The novel lol
By Plebby in forum [TeamSpeak 2] Client SupportReplies: 0Last Post: 02-01-2006, 12:24 -
Server
By lars-andre-petersen in forum [TeamSpeak 2] Server SupportReplies: 70Last Post: 26-09-2005, 11:54 -
Stopped server wont restart
By Black_ice8472 in forum [TeamSpeak 2] Server SupportReplies: 1Last Post: 24-06-2004, 15:27 -
I cant clik administration after TS restart
By Schirmer in forum [TeamSpeak 2] Server SupportReplies: 9Last Post: 13-06-2003, 04:20


Reply With Quote




