RE: Terminal Services stops responding on our Windows Server 2003



Your terminal server issue appears to have several potential causes. The
first thing to check are the applications running. If your programs are not
‘terminal server compatible’ they may run for a time but under a variable set
of conditions will lock up. In my experience, certain versions of
applications won’t work while others do.

Second, you didn’t mention any best practices. I strongly suggest you
initiate a best practices for deployment of terminal services. We have
established a set of consistent standards across all of our servers that
helps to eliminate inconsistent practices and ‘intermittent’ problems such as
the one you are having.

Here is a short list of problems that could be the culprit:

Bios, Raid or SCSI drivers that don’t like terminal server could be a problem.

My suggestion is to establish some best practices
Create locked down security profiles and limit users to only applications
and security they need.
Set printer permissions and limit printer drivers loaded on TS box
Certify all applications are TS compatible – VERY important
Make sure page file is about twice size of physical memory
Have a minimum of 1 gig ram, the more the better
Limit internet explorer use on TS box – spend some time on this one because
in my experience, nothing eats up bandwidth, loads more malware and slows you
down more than IE. If it isn’t needed, get rid of it and most of your
problems will go away
Restrict access to only areas and applications users need.
Don’t allow Media Player, Shockwave or any other graphics intensive plugin.

Without a better description of what you are running, security policies and
hardware specifics it is hard to be exact.

Good luck.



"MarkA" wrote:

> Hi
>
> I have the same problem. Did you find anyway to resolve this ??
>
> Cheers,
>
> Mark
>
> "Dan the man" wrote:
>
> > Hi Guys,
> >
> > We have a new windows 2003 installation running TS is application node about
> > every three-four days the TS service stops responding, you cant restart it
> > and TC clients cant login, the only way we have to fix this at the moment is
> > to restart the server.
> >
> > Any help much appreciated
> >
> > Dan
.



Relevant Pages

  • Re: RPC Server Is Unavailable on 2003 TS but not on 2000 TS
    ... Windows Server 2003 and you receive an "The RPC service is ... MCSE, CCEA, Microsoft MVP - Terminal Server ... There are 2 major SQL applications running all the time ... They have tested logging the entire office in to the 2003 TS ...
    (microsoft.public.windows.terminal_services)
  • Re: RPC Server Is Unavailable on 2003 TS but not on 2000 TS
    ... number of things based on previous posts on Technet as well as posts found ... Windows Server 2003 and you receive an "The RPC service is ... MCSE, CCEA, Microsoft MVP - Terminal Server ... There are 2 major SQL applications running all the time ...
    (microsoft.public.windows.terminal_services)
  • Re: RPC Server Is Unavailable on 2003 TS but not on 2000 TS
    ... Check the troubleshooting tips on EventID.net, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... applications loaded and they only put in the new 2003 TS ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows 2003 Server Terminal Services
    ... I tried the first .bat idea, and though it worked, it left the batch file ... accessing applications which they should run. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Terminal Server role and the Terminal Services Licensing ...
    (microsoft.public.windows.terminal_services)
  • Re: Access Control Best Practices for shared hosting seem at odds with Web Site Starters
    ... the full context of the bullet I quoted appears to be the HTTP POST ... Do not allow anonymous user to have write permission. ... content to the server, then they can write anything onto the server. ... More secure alternatives are applications that store ...
    (microsoft.public.inetserver.iis.security)