Restart\Shutdown Server 2K3

[KilluminatiStyle]

I have a small domain setup in my home and things have been working just fine until recently. I usually just RDP into the server, rarely to I actually log in from the machine itself. Recently, when trying to reboot the server via RDP, it gets to the logging off screen then hangs. I have to go to the machine itself and hit CTRL+ALT+DEL to login (the shutdown option is greyed out) and then tell it to reboot.

I haven't added any new hardware or installed new software but I did uninstall several peices of software. I don't know if this has anything to do with my situation but I figured I let you know.

Really it's not a HUGE deal because I hardly ever reboot the server but it is annoying. Any help is greatly appreciated.

**NEW DEVELOPMENT AS I TYPED THIS**

Now it seems that it also hangs just trying to log off.

[Force Flow]

If you physically look at the server does it hang?

If you restart via remote desktop, you will experience a hang for 30 seconds to a minute, which is usually the timeout period after the computer goes through the shutdown procedure.

Although, that doesn't explain why you get a hang on a simple logoff.

[KilluminatiStyle]

If I RDP in, do stuff, Logoff/restart, it hangs at the "logging off" screen.

While its stuck there in the RDP if I take a look at the actual server screen it's just sitting at the "Press CTRL+ALT+DEL" screen, waiting for me to login.

[Force Flow]

After the logoff, if you disconnect from remote desktop and re-connect, what happens?

[KilluminatiStyle]

I can log back in normally but logging off or rebooting does the same thing again.

I'm wondering now if it may have something to do with Symantec Endpoint Management Console since for some reason non of my PC's are able to communicate with the Symantec Server anymore and the service won't start.

I'll check into that and post back.

[KilluminatiStyle]

Just thought I'd post back with some more information on this.

I got Symantec Endpoint functioning again and the problem persists. However, I think I found what is causing the issue. Crappy Lexmark software. It looks like there is a license agreement that is getting "confused" by the remote login. Unfortunately it's something I'm going to have to live with because Lexmark doesn't have a "bare driver" for this little beast which means I'm stuck with the software suite.