*Please Help* Connection Timed Out

[Treize]

1. I have tried port fowarding.
2. I have tried DMZ
3. I have turned off ZoneAlarm
4. I have turned off DHCP
5. I connect to my server via the LAN IP.

Still I get the same issues. Friend of mine tried all night to get in as well, and strangely enough sometimes she could, sometimes she couldn't. If she'd login from the search page, she could get in, if she'd log in from the local address book she couldn't. Regardless she was the only one, everyone else I tried to get in couldn't at all. Including myself at times (when I was attempting to join my regular IP).

I have read the forums on this extensively and it seems a lot of people are having this problem and are being told that it's something they are doing wrong. I've followed all the advice that was suggested on here. And still nothing. I can host Roger Wilco fine (granted it sucks), so why not this? Perhaps there is some obscure bug that only occurs in certain configurations?

Regardless, if anyone has any advice, or have solved this problem on their own, please lemme know. Teamspeak is too badass a program for me to give up on it before I really even get started.

System Info:

Windows XP Pro
Sound Card: SB Audigy
Router: Linksys NR041 (in DMZ)
Speakeasy DSL 1.5/256
Versions of TS:
- Client: 2.0.32.60
- Server: 2.0.19.40

[pim]

porttriggering?
Latest stinksys firmware?
UPnP?

Just some thoughts, besides this ZA might be the culprit. If you check the forums you will find ZA users where switching it off nor de-installing helped. Manual deletion and a registry cleaner finally removed ZA really after which TS worked.

Not being a ZA expert, and having a perfectly working stinksys myself I would start there

[Treize]

Network Everywhere Cable/DSL 4-Port Router

Product Release Date : September 6, 2002
Current Firmware : Version 1.2 Release 03
Firmware Date : May 5, 2003
Product PartNo : NR041

Under the UPnP menu of my router:

teamspeak: 8767 UDP 192.168.1.100 (enabled)
teamspeak2: 14534 TCP 192.168.1.100 (enabled)
teamspeak3: 51234 TCP 192.168.1.100 (enabled)

No dice.

Am I forwarding wrong?

I know the basics of networking, I am not going to pretend to be any more knowledgable than I am, but I was able to set up an FTP site ok with this router, I dont see what could possibly be my problem now.

Just to make sure ZA wasn't the problem (i've since uninstalled anyway) I attempted to host a server on my G/f's computer (other one on network) and got the exact same problem. Which leads me to believe:

1. Router
or
2. Forwarding issues

More detailed description of the problem:

When user tries to connect through the address book: Connection timed out.

When user tries to connect through the search feature, they can get in as GuestX but the second they leave, they can't get back in.

Some users can't even get in through the search feature.

Thanks for the response btw :)

[pim]

This is all strange, have you tried to put all and everything in the debugging mode, an please post the logs

[Bastian]

This is a very strange bug in server version 2.0.19.40. All clients must have their client log level at "debug" and most likely it will work fine then.

To avoid this, use the current developer release. You can grab it at ftp://ftp.teamspeak.org or here:

http://www.teamspeak-einstieg.de/modules.php?op=modload&name=Downloads&file=index&newlang=eng

Please report back!

[Timon010]

I'm expieriencing the same problem

Have the right ports forwarded, and the client in Debug mode.

I can connect to Teamspeak, but anyone from outside can't connect...

Router = Sitecom DC202
firewall = on (although if I put it off, the problem stay's)

Anyone has any suggestions?


Timon

[Treize]

Well, shortly after posting this, I got fed up and got another NIC and cut the router out of my network here.

So now I have DSL -> my computer -> other computer by way of internet connection sharing.

ZoneAlarm reinstalled, and ... strangely enough. Everything's fine now. Teamspeak works flawlessly.

So:

1. Perhaps it's a problem with my particular brand/model of router.
2. it's definitely not zone alarm.

This weekend if there is really a desire for me to do so, I will hook the router back up and try to duplicate and log the problem for you guys.

[pim]

Timon,

Dump the sitecom in the north-sea. They, and especially the model you mention, will NEVER work, They are also known as shitecom. SO if you dump it around Delft, you will find mine on the bottom too

Go for a linksys , 51 euros and you.re the man, if you want to spend more go for the Vigor Draytek range

[SuperDre]

Just dump the linksys...


There is a known problem with some routers and client 2.0.32.60 (in fact the exact problem is not known yet, but the following workaround works in most cases).
As a workaround you will have to set the client to debug mode to make the problem dissappear.
Debug mode is under Settings -> Options -> Other -> Log Options (Do not forget to restart the client. Otherwise the setting will not be active).

[Brain]

... and don't think D-Link DI 604, at least not in hardware revision D