Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Terminal Service Issues in Windows 2000 Server 1

Status
Not open for further replies.

cbrider

IS-IT--Management
Joined
Feb 3, 2003
Messages
94
Location
US
I am running a Windows 2000 Server with Active Directory. I can connect to the server via terminal services throught my Windows 2000 Pro workstation. But after several successful logons via terminal services, the server freezes, it stops everything, including my scheduled backup. The client computers can still logon, and there is no effect to network performance.

What to do?
 
I cannot see the event log because the desktop won't come up on the monitor. When i hit Ctrl+Alt+Del i can see the task manager but that's the only thing that works, log off button doesn't respond.
 
This sounds like a memory issue...

So reboot the server when you can, look at the event logs...

When you say "successful logons," how did you exit the Terminal Services session? You have to do a proper logoff. Clicking the "X" only disconnects the session, and leaves it active in memory. Also, what applications are you running on the terminal server? Is terminal services running in Application mode? Could be a program that leaks memory.

Matt
 
I may have clicked the "X". Yikes, i'll be more didligent in remebering to do that next time. No it is not running in app mode.

To conclude, i guess there isn't a way to fix the issue without a reboot.
I just hate the idea of using the power button.
 
Yeah, sounds that way. Thanks for the vote, by the way.

How much memory do you have? Its good that you're not running application mode Terminal Services, you really don't want it running on a box that is running Active Directory. Administrative mode should be fine.

Matt
 
I am running 1GB of RAM
 
That's plenty of RAM, so check your stuff when you reboot. Look at the event logs, check your memory counters, consider the apps your users are using. If its anything written in Foxpro or Access (especially Access), you could have a leaky application.

Matt
 
I do run an application w/ FoxPro, but it isn't accessed via terminal services. I only use terminal services right now and that's so i can do remote administration.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top