Avatar of bhobson_2000
Flag for United States of America asked on

Can't log onto Windows Exchange server running Server 2000 from Remote Desktops or console!!

I have an installation of Exchange Server 2000 running on Server 2000 box that has been running for a little over 3 years.  I rebooted it Tuesday as I normally do every week, no changes were made, and after the reboot, I first discovered that I could no longer get to the server via RDP.  After going to the console, I discovered I also can't get into it on the console, as a matter of fact, at the console monitor isn't getting a signal and is in "standby".  I have checked the cables to the KVM and everything seems to be connected properly.  To further complicate things, although I can get to all my remote management stuff for the server (logs, services, IIS, etc.), I can't shut it down or reboot it remotely, having tried the native Windows shutdown, the one in the Server 2K Resource Kit, and the one in PSTools from SysInternals.  I also can't stop/start the Terminal Services service because the Start and Stop buttons are greyed out.  My plan at the moment is to stop all the Exchange services, pull of a copy of the logs and dbs for extra insurance, then hard boot the server and hope it fixes the problem.  Has anyone else encountered this?
Windows 2000

Avatar of undefined
Last Comment
Rick Hobbs

8/22/2022 - Mon

No need to do a hard boot...


To perform a local or remote shutdown
1. Open Computer Management.
2. In the console tree, right-click Computer Management (Local) , and then click Properties.
3. On the Advanced tab, click Startup and Recovery.
4. Click Shut Down to open the Shut Down dialog box.
5. Under Action, select the actions you want to perform on the computer to which you are connected.
6. Under Force Apps Closed, select the circumstances under which you want to force applications to close when you shut down or restart the computer, and then click OK.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

The remote shutdown method you outline is the one I was using when I refer to "native Windows shutdown".  It just wouldn't restart remotely, no matter which method I tried.  I did end up going with my plan, and everything worked out fine.  Thanks for the ideas anyway!
Rick Hobbs

Glad I could be of assistance. Thanks!

BTW, I forgot to recommend trying to remotely start telnet on the unit, telneting in, and doing a restart from there.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck