Prev: Terminal Services Across Mulitple Domains
Next: Terminal Services
From: JamFish728 on 19 Apr 2010 12:41
I'm really new to Terminal Services, however, this problem has me stumped. We
have two servers clustered together and load balanced. Last Friday, one of
our servers started to give either giving errors ("Terminal Services is
busy") or taking an abnormally long time to login (around 20 mins at some
points). I tried restarting it over the weekend to see if it would help, but
as of today, the problem still persists.

I'm really trying to figure out what might've of caused it, and more so, how
to fix it. I'm not getting anything from searching on my own, so any help
would be appreciated.

This is Windows Server 2008 Standard.
From: Vera Noest on 19 Apr 2010 15:19
So it has worked before without problems, is that correct?
Has anything been changed on the servers immediately prior to this
problem?
Are you using Network Load Balancing or Session Broker Load
Balancing?
How big is the user load?
Check if this helps:

980568 - A terminal server that is running Windows Server 2008
stops responding when lots of clients make terminal sessions to the
server
http://support.microsoft.com/?kbid=980568

_______________________
Vera Noest
Remote Desktop Services troubleshooting
http://ts.veranoest.net

=?Utf-8?B?SmFtRmlzaDcyOA==?=
<JamFish728(a)discussions.microsoft.com> wrote on 19 apr 2010 in
microsoft.public.windows.terminal_services:

> I'm really new to Terminal Services, however, this problem has
> me stumped. We have two servers clustered together and load
> balanced. Last Friday, one of our servers started to give either
> giving errors ("Terminal Services is busy") or taking an
> abnormally long time to login (around 20 mins at some points). I
> tried restarting it over the weekend to see if it would help,
> but as of today, the problem still persists.
>
> I'm really trying to figure out what might've of caused it, and
> more so, how to fix it. I'm not getting anything from searching
> on my own, so any help would be appreciated.
>
> This is Windows Server 2008 Standard.
From: JamFish728 on 19 Apr 2010 18:09

Vera,

It was working before without any issues. Two Days before that, I installed
a new, legitimate program from one of our vendors, but I don't think that
would cause any issues.

I'm also not seeing anything in the event logs, aside from the error that
logins and logouts are taking a long time. No Errors from CredMan or LSASS
either.


"Vera Noest" wrote:

> So it has worked before without problems, is that correct?
> Has anything been changed on the servers immediately prior to this
> problem?
> Are you using Network Load Balancing or Session Broker Load
> Balancing?
> How big is the user load?
> Check if this helps:
>
> 980568 - A terminal server that is running Windows Server 2008
> stops responding when lots of clients make terminal sessions to the
> server
> http://support.microsoft.com/?kbid=980568
>
> _______________________
> Vera Noest
> Remote Desktop Services troubleshooting
> http://ts.veranoest.net
>
> =?Utf-8?B?SmFtRmlzaDcyOA==?=
> <JamFish728(a)discussions.microsoft.com> wrote on 19 apr 2010 in
> microsoft.public.windows.terminal_services:
>
> > I'm really new to Terminal Services, however, this problem has
> > me stumped. We have two servers clustered together and load
> > balanced. Last Friday, one of our servers started to give either
> > giving errors ("Terminal Services is busy") or taking an
> > abnormally long time to login (around 20 mins at some points). I
> > tried restarting it over the weekend to see if it would help,
> > but as of today, the problem still persists.
> >
> > I'm really trying to figure out what might've of caused it, and
> > more so, how to fix it. I'm not getting anything from searching
> > on my own, so any help would be appreciated.
> >
> > This is Windows Server 2008 Standard.
> .
>
 | 
Pages: 1
Prev: Terminal Services Across Mulitple Domains
Next: Terminal Services