People can connect to my server but then immediately timeout

[Shadow421]

OK this is my problem when people connect to my teamspeak server ip they connect and then timeout immediately. I have forwarded the correct IPs on my Linksys router. I have Windows XP Professional. I have looked around on here and tried some of the things it said to do and none of that worked. So please any help anyone can give would be great. Oh and I can connect to my LAN ip and to my ISP ip but no-one can connect to me.

Thanks for your time and I hope this gets me the answer.

[pim]

This very much sounds like a router or firewall problem

You say:

I have forwarded the correct IPs on my Linksys router

But it is more important to see of the right ports are forwarded to the right (internal) IP address.
Use www.myip.com and see if you external (ISP/WAN) IP is static or dynamic.

The box running the server should have a fixed IP not one from dhcp

Finally check if there are any firewalls running, like the winXP one, pr zone-alarms/norton

A server log would also be most helpful for faultfinding

[Shadow421]

Ok I have both IPs right. The 1 running server is my ISP assigned IP. The IP that I have it forwarded to is also correct. I have no software firewalls at all and I didn't use the XP firewall because I don't like it. About the server log how do I use that to find the problem? lol see I told you I tried a lot of things. I am pretty decent with computers I have a certificate in IT. Anyways I appreciate the reply but keep them coming. Maybe a reply on how to use the server log to find problem.

Thanks

[guldi]

can you switch the clients which get a timeout into debugg mode and then try again ?


PS: I moved this thread in the appropriate forum and deleted the second one as this contained the same problem.

[Shadow421]

I am new to this what will putting it in debugg mode do?

[SatanClaus]

that should cause a very detailed log-file (your TSClient.log in the TS-directory). Also there seems to be some strange influence where putting the client into debug-mode fixes the problem

cu
SatanClaus