Windows2003 blank screen after login

[Guest Rolard99@gmail.com]

I have a Windows2003/Exchange 2003 server (32bit sp2 on both) in my

environment that just recently stopped allowing logins. Local, remote

it doesn't matter. Mail continues to flow correctly and mail clients

can connect fine but if you login to the server remotely you get a

blank screen. Logging in locally does the same except that the

realtime scan module from Trend will startup. Locally I can bring up

Task Manager and can fire off commands. Explorer shows as running but

stopping and starting it still does not bring up a desktop. Nothing

has been installed recently and the event logs have been no help.

This weekend I am slated to wrestle with it and currently I am running

low on ideas to try. Anything other then running a setup repair or

reloading come to mind?

 

Thanks!

Paul

[Guest Meinolf Weber]

Re: Windows2003 blank screen after login

 

Hello Rolard99@gmail.com,

 

Have a look here:

http://support.microsoft.com/?kbid=906510

 

http://support.microsoft.com/kb/249321

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a Windows2003/Exchange 2003 server (32bit sp2 on both) in my

> environment that just recently stopped allowing logins. Local, remote

> it doesn't matter. Mail continues to flow correctly and mail clients

> can connect fine but if you login to the server remotely you get a

> blank screen. Logging in locally does the same except that the

> realtime scan module from Trend will startup. Locally I can bring up

> Task Manager and can fire off commands. Explorer shows as running but

> stopping and starting it still does not bring up a desktop. Nothing

> has been installed recently and the event logs have been no help.

> This weekend I am slated to wrestle with it and currently I am running

> low on ideas to try. Anything other then running a setup repair or

> reloading come to mind?

> Thanks!

> Paul