Timed Out

[woutervh]

When I connect to linux server with Win32 client I first get the Welcome..... message, then after 2 seconds it Timed out.

Via private IP (192.168.....) it al works perfectly, but public it doesn't.

It says this:
[19:27:45] Connecting to **.***.**.**
[19:27:45] Connected to server ********
[19:27:45] Welcome to ******** TS Server
[19:27:47] Connection timed out

Plz help me,
Regards

[pim]

Router problem on the server-side, or linux-firewall/security, you want to bet ???????

[woutervh]

Ok, the server manager wants to bet.
It really isn't the secrurity/firewall or something.
The port 8767 goes to server.
If not, I wouldn't get the Welcome message.....

[pim]

Can still be a routerproblem though, I've been struggling for over a month with one of the things, knowing for 1000% sure that the box was configured well. And it did exactly the same as your, connected or 2-3 seconds, including welcome message, and then fro no apparent reason disconnected. No entries in the logs either I assume?

Some of the routers simply do not work with TS, while other ports are forwarde correctly

Let me guess again, your router brand starts win an "S" ?????

[Vincentius]

Hehe i own the server. My response is a bit late but it took ages for the activation mail to arrive!

You're right, my routers brand name starts with an "S".

But in my router the server is set up as 'Master server', so outside the firewall. I don't have to foreward ports to it because it's not behind te firewall. I never had any problems with any other server application.

[pim]

Ok, if it's a Sitecom you are fcuked,

Mine wouldn't allow TS to operate on the forwarded port, any other application worked fine, like MSN, remote desktop, CoD, BF and MOHAA servers etc.

Even putting the TS server box on a fixed IP and putting it in the DMZ made no difference at all. I was so happy the damned thing just stopped working completely after 3 months. It was within the warranty and I could claim my money back and bought a LinkSys.

Everything is fine now

Just to be sure, do a forumsearch on Sitecom, if I remember correctly there was another frustrated Sitecom owner that was telling us about his dealings with the Shitcom helpdesk

[Vincentius]

Oke i'm fucked :mad:

I just trow that stupid device out of the window and build my own router.

[pim]

Try harassing Sitecom, and teel them if it ain't working you want to have your money back. And don't let them go int their usual routine of accusing TS software of being shitty and the Shitcom the best thing since sliced bread

[Dummer Sack]

What server and client version you use?
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).

[SuperDre]

Thanx, I have the Sitecom 202 (v2) with the latest firmware, and had the same problem.
When I used the 'workaround' it seems to work fine.

[MECHT4NK]

what does debug mode actually mean. i had the same problem.