Terminal Service Idel timeout problem

[cc929]

Hi,

I have problem for Terminal services server (Windows 2003 std R2)idel timeout.
I have opened port 3389 in my fortinet firewall.
After remote desktop logon and the idel time reach to 10 min, they will kick me out or logoff automatically but my firewall connection still alive. I did change screen saver timeout to 60 min but still not working.
If I remote desktop from internal network, I don't have problem.
Does anyone know how can I change terminal server setting and I can get 60 min idel timeout pass thought firewall?

Please help!

Thanks!

cc929

 

[gmail2]

OK, I'm slightly confused. I presume you've got two different subnets in your domain split by a firewall and you want to RDP from one subnet to a host in the other. However, I don't quiet understand what you mean by "the firewall connection is still alive" - you mean that there's still some data going through your firewall between the RDP client and the TS Server? How have you confirmed this, from traffic logs or ? Have you checked Terminal Services Manager to see if the session is still showing as Active, Disconnected or Idle?

Irish Poetry - Karen O'Connor
Get your Irish Poetry Published
Garten und Landschaftsbau

 

[Zelandakh]

This is quite common. You have an RDP idle timeout and you also have a firewall idle timeout which can kick in and disconnect the session. This is irksome for Outlook Anywhere sessions too.

On the firewall change the connection idle timeout to 60 minutes.