No reply from server, maybee ofline...etc

[jonathan76]

Hi there,

I'm running a TS Linux server
it is up and running and people can come on it already : 213.193.253.194:8767
Youre welcome to check it out :)
but i cant get on it and im behind a router. i have done the TCP & UDP settings on my router.
But still i get timed out.
Should i be changing settings on the server..?? or on the pannel..??

Who can help me out that had the same problem..

with regards

jonathan

[Bastian]

Please read our FAQ (http://www.goteamspeak.com/index.php?page=faq&id=3&item=24#q24) and our forum rules (http://forum.goteamspeak.com/announcement.php?f=2).

[jonathan76]

i ha ve read the FAQ's but im sorry to say this hasnt helped me in any way.. :(
So i could use some personal help in this issue.

Possible reasons:
You entered an IP or port which is not correct or where no server is running on.
Check with the serveradmin if you have the correct IP and port and if the server is running. If the server doesn't run on the default port 8767, enter the destination address of the server like the following: IP:PORT or in numbers 192.168.1.1:8760 (this is just an example)


You have a firewall which is preventing a connection to the server.
Check your firewall manual to see how to allow TS a connection to any TS server. The ports required by TS are mentioned in the FAQ. If this doesn't help you, check a firewall forum for specific help for your kind of firewall

You can connect to some servers but not to the one specific.
Test several servers to make sure the problem lies not within your network configuration but on the server side.
The server hoster may miss a port forwarding or has a bad firewall config (this is often the case when new / network unexperienced user setup servers). Advice the hoster to configure the port forwarding.

You get a timeout.
A timeout issue can in certain cases be solved by switching the client into the debug mode. Some firewalls can cause timeout problems as well, so deactivate the firewall for testing. Wireless networks may as well be the cause of timeout problems. Try to connect without the WLAN and use an ethernet cable instead.


You get a socket error like 11004.
Check the sticky threads in the forum. Socket errors are described in several forum sections.

[WolfStar76]

www.portforward.com

[jonathan76]

Have been there and got the T-shirt..
As i said done all my TCP ^& UDP settings in my router as told in forwording.
I think there is a config file on the server that should be changed with a ip but im not sertain.
Is there any one with a simillar problem and a solution..?
It would help me greatly and be very greatful.

So please give my topic some time to think about..??
And help me find a sollution.. :)

[Bastian]

Could you please explain why you are ignoring the rather important note in this FAQ entry?

[jonathan76]

Could you please explain why you are ignoring the rather important note in this FAQ entry?


Whitch note is that , what youre talking about... if read the faq's as i said..

[Bastian]

This is part of the FAQ answer you quoted above: Note:

Do NOT use the WAN IP or serverlist to connect to your own LAN server. Your router will most surely not allow this. Within your own network, ONLY use the LAN IP. There is no difference even if you setup a port forwarding in your router, use the LAN IP when ever you or someone else is within the same LAN as the server is.

[jonathan76]

hmm, well thx anyway.. :rolleyes:

But im not running my server @ home so no LAN going on here...
The server is running on a linux server in A-dam (DC)
and i cant connect to it..:(
im almost giving up now, couse i cant seem to find the right awnser..

[Katana*GFR*]

It must be in your computer the fault, because other users can connect fine.
Do you have firewall or something? Theoraticly you shouldnt have to forward ports in your router when connecting to a outside TS server.

I cant connect to it either, is your connect port right? (8767)

[guldi]

according nmap:

Starting Nmap 4.01 ( http://www.insecure.org/nmap/ ) at 2006-08-08 13:22 CEST
Interesting ports on 213.193.253.194:
PORT STATE SERVICE
8767/udp closed unknown

I think I'll not be able to connect to a closed port.