I have presently running 2 x 2008 servers in different locations server 1 - basic not currently running AD server 2 - Enterprise currently running AD Hardware for servers completely different including routers, modems etc session timeouts not set ISP's are different for each server location Clients access both servers via TS, with no TSgateway as yet All clients (approx 30) using Vista business with latest upgrades Server 1 has been installed for 9 months, server 2 only 2 months Problem - ever since the server 1 has been installed the clients have dropped out of TS (TS screen freezes) when idle with times varying from 3 minutes to 30 minutes (seems random), users have to close TS then re-logon, session does not close and reconnection is normal. I have put up with this but now since installing server 2 I am having the same problems and the users are complaining (with justification) as it is reducing productivity. I do get the occasional error 56 - The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. but this does not seem to directly relate to the times when the freeze happens. I would appreciate it if anyone could point me in the right direction, it seems strange that I should have the same problem on 2 entirely different systems. © 2009 Microsoft Corporation. All rights reserved.Sat, 04 Jul 2009 08:25:29 Zb00fd896-cd41-445d-8575-922bd6987fb6http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b00fd896-cd41-445d-8575-922bd6987fb6#b00fd896-cd41-445d-8575-922bd6987fb6http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b00fd896-cd41-445d-8575-922bd6987fb6#b00fd896-cd41-445d-8575-922bd6987fb6brownie1300http://social.technet.microsoft.com/Profile/en-US/?user=brownie1300I have presently running 2 x 2008 servers in different locations server 1 - basic not currently running AD server 2 - Enterprise currently running AD Hardware for servers completely different including routers, modems etc session timeouts not set ISP's are different for each server location Clients access both servers via TS, with no TSgateway as yet All clients (approx 30) using Vista business with latest upgrades Server 1 has been installed for 9 months, server 2 only 2 months Problem - ever since the server 1 has been installed the clients have dropped out of TS (TS screen freezes) when idle with times varying from 3 minutes to 30 minutes (seems random), users have to close TS then re-logon, session does not close and reconnection is normal. I have put up with this but now since installing server 2 I am having the same problems and the users are complaining (with justification) as it is reducing productivity. I do get the occasional error 56 - The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. but this does not seem to directly relate to the times when the freeze happens. I would appreciate it if anyone could point me in the right direction, it seems strange that I should have the same problem on 2 entirely different systems. Sat, 27 Jun 2009 16:49:35 Z2009-06-27T16:49:35Zhttp://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b00fd896-cd41-445d-8575-922bd6987fb6#7e30443d-02e2-496a-8406-db7c4c184438http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b00fd896-cd41-445d-8575-922bd6987fb6#7e30443d-02e2-496a-8406-db7c4c184438threesixty-360ICThttp://social.technet.microsoft.com/Profile/en-US/?user=threesixty-360ICTWe have the same experience, mostly when users are using other apps.. The Terminal Server keep alive gpo should fix this, but we have this enabled and it seems to have no effect..<br/><br/>my guess is the wan connection times out or there is a bug in the keepalive feature.. i'm researching this further..Sat, 04 Jul 2009 08:25:29 Z2009-07-04T08:25:29Z