Slightly different server/router problem

[W3bMa$t3r]

Ok, I read the posts about server and router problems and couldn't find anything related to my problem. I have an SMC router. The UDP 8767 is forward to the TS servers IP on the lan. My issue is that the TS Client connects to the server (It connects, shows welcome message from TS Server), but within 3-5 seconds it says the connection to the server has been terminated.

I checked my Firewall for SPI features and I was able to bypass (I only did it temp) the UDP protection, but it didn't affect the lose of connnection.

In the routers fire wall status, it shows the connection attempts to the TS Server, but is also showing that it's receiving a LAND ATTACK (a DoS attack). Would this have anything to do with the lose of connection if I've turned off the UDP protection?

TIA for any help you give.

[Dummer Sack]

Originally posted by W3bMa$t3r
In the routers fire wall status, it shows the connection attempts to the TS Server, but is also showing that it's receiving a LAND ATTACK (a DoS attack). Would this have anything to do with the lose of connection if I've turned of the UDP protection?
It can be the problem. Have you tried to turn of the Firewall completely for testing? If the problem goes away it is a Firewall problem.
This (http://www.teamspeak.org/forums/showthread.php?s=&threadid=8793) user here seems to have the same problem though he is not running his own server I think.

[W3bMa$t3r]

Well my router has a dmz function where supposedly if you enter the local lan computer's ip address, you can give it full, open internet access (i.e. not behind firewall or any of it's features). I did this for the ts server but it didn't change the lose of connection with the client. Hmm, is it possible that there is something other than the router causing this problem or is the dmz possibly not giving full, open internet access?

I'm going to try turning the firewall function of completely, not just open a "clean" path and see what that does for me. I'll post back... Thanks.

[W3bMa$t3r]

Ok, I turned off the firewall function completely, but the client is still connecting for 2 seconds and then losing connection.

One thing I did notice though is that the router status log wasn't showing a LAND ATTACK with every connection attempt like it was before when the firewall was active so I'm assuming that the firewall was definetly out of the picture on this one...

[Dummer Sack]

Has the person that tries to connect to your server problems with other servers or is he running a firewall?
Does the server run ok if you connect to it via the LAN IP?

[W3bMa$t3r]

Originally posted by Dummer Sack
Has the person that tries to connect to your server problems with other servers or is he running a firewall?
Does the server run ok if you connect to it via the LAN IP?

He can connect to the other TS servers we have running at different locations, but not to the one I'm trying to get setup. No, he's not behind a firewall. Yes, TS (server/client) works fine via LAN.

[Dummer Sack]

Then the only other thing I can think of is that the router firmware may be buggy.
I know that some firmware revisions of LinkSys routers are making trouble with TeamSpeak.
Check if other firmwares for your router are available and upgrade or downgrade to find a working one.
Maybe search for a router forum where they know your SMC router. I think there you will get help selecting the correct firmware.

[W3bMa$t3r]

Ok, I'll look around. I upgraded the firmware when I bought the router, probably less than a month ago, but I'll check the forums and see what they say. I appreciate all the help. Thanks.

[Dummer Sack]

If the firmware is the problem maybe post the not working and a working revision here.
There is still a chance that the problem is on the client side. So test with more than one client. That the server is working in the LAN indicates a client or router problem.

[W3bMa$t3r]

Well, I'm now inclined to think it is a router problem. Possibly the firmware.

We just completely killed the firewall (for like the 3rd or 4th time) and it works fine now... Damn router... I'm gonna try a DMZ again and see if it works...

If it ends up being a firmware problem, I will post the good and bad. Thanks.