View Full Version : Again a connect problem
I have run a teamspeak server for a while. I doesn't have problems with it.
But since a week i have problems with my server. The port 8786 is forwarding.
At this moment some people can connect to my server, esspecially new ones cannot connect. Very strange. Sometimes the people who used my server a long time, cannot connect and other times they can. :confused:
I read in other post that you should open the port 51234 also? why? :eek:
I read in other post that you should open the port 51234 also? why? :eek:
DEFINITELY NOT !
1) there is a FAQ thread which deals with such kind of problems.
2) you should give some more infos: did you changed firewall,....
i didnt change my firewall and i haven't installed SP2 (lucky me!) :D
but how can it be that sometimes people CAN connect to my server and other times NOT. Example:
A friend and i were on ts-server (for a hour) and then he shut his teamspeak and after he shut down, he couldnt connect to the same server again :confused:
why didnt they make it easy for users (NOT TS), i think 99% of the people that runs a servers has connect problems :(
The reason some people can and some can't is simply put, a router.
See Below:
Symptoms:
People who are using a home router (NAT) can't connect to your server, but they can connect to other servers.
People connected directly to internet, can connect to your server.
The machine that is running the server has more than one ip number.
Problem:
The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary ip). Nat routers don't know what to do with this foreign incoming data (unknown ip+port), and drop the packets.
Solution:
There are two easy solutions. (There are more, but those are too complicated to explain here)
1:
In server.ini in the section [Main Config] there is an option BoundToIp=
Set that to your server ip. For example: BoundToIp=213.202.254.115
You don't need to specify a port.
This will make the server listen and send only on the specified ip.
2:
Even easier is to let the clients connect to the primary ip of the machine. But this is usualy not wanted, because of dns issues etc.
Copied from FAQ, hope it helps.
Toro :p
spyhunteruk
25-10-2004, 11:40
Right I have setting up of Server problems, can anyone help.
I have checked the forums and FAQ and can't find the answers:
Heres what my Server log file states upon running the server:
25-10-04 11:35:02,ERROR,All,WEBINTERFACE, WebInterface startup failed with port 14534, Exception:Socket Error # 10049
Cannot assign requested address.
25-10-04 11:35:02,ERROR,All,TCPQUERY, TCPQuery startup failed with port 51234, Exception: Socket Error # 10049
Cannot assign requested address.
25-10-04 11:35:02,ALL,Info,server, Server init finished
Can anyone help.
I have two IP addreses running when right clicking on server taskbar icon, lan ip and outside world ip.
Please help ASAP!!!
The reason some people can and some can't is simply put, a router.
See Below:
Symptoms:
People who are using a home router (NAT) can't connect to your server, but they can connect to other servers.
People connected directly to internet, can connect to your server.
The machine that is running the server has more than one ip number.
Problem:
The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary ip). Nat routers don't know what to do with this foreign incoming data (unknown ip+port), and drop the packets.
Solution:
There are two easy solutions. (There are more, but those are too complicated to explain here)
1:
In server.ini in the section [Main Config] there is an option BoundToIp=
Set that to your server ip. For example: BoundToIp=213.202.254.115
You don't need to specify a port.
This will make the server listen and send only on the specified ip.
2:
Even easier is to let the clients connect to the primary ip of the machine. But this is usualy not wanted, because of dns issues etc.
Copied from FAQ, hope it helps.
Toro :p
i try to do this, but i doesnt work! The server wasnt running then anymore.
The client log look like this:
ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
:confused: :confused: :confused:
ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait:
I'm sure you'll find more then one post on "Time out", no need to post the whole story again.
I'm sure you'll find more then one post on "Time out", no need to post the whole story again.
guldi the client has set it on DEBUG MODE, but he cant connect to the server yet. How can that be? :confused:
I have run a teamspeak server for a while. I doesn't have problems with it.
But since a week i have problems with my server. The port 8786 is forwarding.
At this moment some people can connect to my server, esspecially new ones cannot connect. Very strange. Sometimes the people who used my server a long time, cannot connect and other times they can. :confused:
as you state your useing port 8786 the default port is 8767 so when your using a diferant port your clients NEED to place the port # after the ip with a colin : between the two so it reads like this xx.xxx.xx.xx:8786 or they cant find server
guldi the client has set it on DEBUG MODE, but he cant connect to the server yet. How can that be? :confused:
- what m&m stated
- firewall
- have you tested on the server side what Torojon proposed (or what he copied fro mthe FAQ) ?
- what m&m stated
- firewall
- have you tested on the server side what Torojon proposed (or what he copied fro mthe FAQ) ?
i tried but, the server dont run then, because the server says also to me then: cannot connect to server. And the administration doenst work also at that moment.
But by me there stand in the server.ini not BoundToIp= but BoundToIp1=. And if i change is, it change is self to BoundToIp1=. But after the = i have to put my outside ipaddress?
If I remember correct, the 1 is just there as you can bind the server now to more then one IP => boundtoIP1=..., boundtoIP2=....
But, I'm not totaly sure about this one.
Bind to external IP:
no, bind it to the IP the server is running on. This will be most surely the LAN IP of the server.
i tried but, the server dont run then, because the server says also to me then: cannot connect to server. And the administration doenst work also at that moment.
But by me there stand in the server.ini not BoundToIp= but BoundToIp1=. And if i change is, it change is self to BoundToIp1=. But after the = i have to put my outside ipaddress?
sounds to be a firewall app if the webadmin is also not working ! Xp firewall , zonealarm , zap , blackice ,any and all can bloct not only the webadmin but the clients from being able to get to your server ..
also built in cookie blockers and popup blockers can block the webadmin there in yahoo tool bar , mozilla explorer , the new microsoft IE tool bar allso has them built in now
sounds to be a firewall app if the webadmin is also not working ! Xp firewall , zonealarm , zap , blackice ,any and all can bloct not only the webadmin but the clients from being able to get to your server ..
also built in cookie blockers and popup blockers can block the webadmin there in yahoo tool bar , mozilla explorer , the new microsoft IE tool bar allso has them built in now
the webadmin works always, except when i change BoundToIp1= in BoundToIp1=202.4343.4343 (by example)!
And the only person who cant come on teamspeak is just one/two persons. This persons have a network at home. So the solution that you are saying, isnt right. :(
the webadmin works always, except when i change BoundToIp1= in BoundToIp1=202.4343.4343 (by example)!
And the only person who cant come on teamspeak is just one/two persons. This persons have a network at home. So the solution that you are saying, isnt right. :(
try to BoundToIp1=your lan ip 192.168.1.101 see if that works
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.