Re: ts2003, users hung at black screen

I understand that the VPN connection never goes down, but AFAIK,
the router can still think that the session can be disconnected.
Most routers allow configuration of the idle timeout, have you
checked yours?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?YW50aG9ueQ==?= <anthony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 13 aug 2008 in microsoft.public.windows.terminal_services:

rdp time outs had already been configured for much longer time
out instances so that should not be it.

ok (group policy)
console root\local computer policy\computer configuration? is
this the place to change the group policy for the screen saver?

we have a constant ping going as a test and the server ip
address getting ping never quits even though the remote session
screen goes black.

"Vera Noest [MVP]" wrote:

There are three possible causes for inactivity time-outs:

* a time-out limit configured on the rdp-tcp connection, in
Terminal Services Configuration, or in a Group Policy.
* a screen saver on the Terminal Server; can be disabled in a
Group Policy.
* a router between your clients and your server, which sees no
traffic and decides that the session must have ended and throws
it out. If that is the case, the solution is to enable TS
Keepalives on the server, in a Group Policy.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?YW50aG9ueQ==?= <anthony@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 13 aug 2008 in
microsoft.public.windows.terminal_services:

i have a clean build 2003 standard server, with TS installed
in application mode.
Users have been complaining of getting logged or bumped off
after 15 min or so. Some of them just have their screen go
black and lose the entire desktop. If they close their remote
window and re login the get back to the desktop their session
is still alive with the applications running. It's like a
screen saver kicks in and locks the TS session and the ony
resoluton is to close the session window and reconnect every
few minutes. They are very frustrated. They are all running
windows xp pro through our sonicwall VPN tunnels. Ping
statistics through the tunnel to the TS server are great and
when the screen goes black they are still pining fine.
.

Relevant Pages

  • Re: ts2003, users hung at black screen
    ... the router can still think that the session can be disconnected. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... this the place to change the group policy for the screen saver? ...
    (microsoft.public.windows.terminal_services)
  • RE: Default application not launching
    ... Terminal Services Configuration - rdp-tcp connection - Environment ... the session should logoff automatically when a user ... Services Configuration, a GPO or in the RDP client, the session ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: How to unlock the console?
    ... It didn't ask to unlock the screen saver anymore. ... >>> After i connected to the console session of the WIN2K3(DC,TS Server) ...
    (microsoft.public.windows.terminal_services)
  • Re: ts2003, users hung at black screen
    ... or in a Group Policy. ... * a screen saver on the Terminal Server; can be disabled in a Group ... traffic and decides that the session must have ended and throws it ...
    (microsoft.public.windows.terminal_services)
  • Re: How to unlock the console?
    ... It didn't ask to unlock the screen saver anymore. ... \console)in the RDC software on the WINXP. ... >> After i connected to the console session of the WIN2K3(DC,TS Server) from ...
    (microsoft.public.windows.terminal_services)
Loading