Server still functions, but cannot log in locally or remotely

[Guest Chris Benton]

Running Windows Server 2003 SP1 on an HP DL380. A couple of weeks ago, we

developed a problem where we are unable to log in to the server either

locally or remotely. It will work okay for a few days, then we get a gray

screen with no login prompt, and we simply get disconnected after a few

minutes; however, clients are able to log in, authenticate, and use server

resources as if nothing's wrong. Only a hard shutdown/restart clears up the

problem. The event logs show nothing amiss. Eventually, a login prompt will

show up at the console, but the login process takes over an hour and when I'm

finally logged in, I notice that no services are running at all. If I try to

do anything in Active Directory via MMC, I'm told that a DC cannot be found.

I'm mystified as to what could be causing this. Any ideas? Virus/malware

scans always come up negative. (We're running Trend Micro OfficeScan with the

latest engine/virus definitions.)

[Guest Meinolf Weber]

Re: Server still functions, but cannot log in locally or remotely

 

Hello Chris,

 

Do you use SBS 2003? Have a look on this articles:

http://blogs.technet.com/sbs/archive/2006/09/01/453504.aspx

 

http://forums.techarena.in/small-business-server/844637.htm

 

 

Also see here:

http://support.microsoft.com/kb/924995/en-us

 

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

 

> Running Windows Server 2003 SP1 on an HP DL380. A couple of weeks ago,

> we developed a problem where we are unable to log in to the server

> either locally or remotely. It will work okay for a few days, then we

> get a gray screen with no login prompt, and we simply get disconnected

> after a few minutes; however, clients are able to log in,

> authenticate, and use server resources as if nothing's wrong. Only a

> hard shutdown/restart clears up the problem. The event logs show

> nothing amiss. Eventually, a login prompt will show up at the console,

> but the login process takes over an hour and when I'm finally logged

> in, I notice that no services are running at all. If I try to do

> anything in Active Directory via MMC, I'm told that a DC cannot be

> found. I'm mystified as to what could be causing this. Any ideas?

> Virus/malware scans always come up negative. (We're running Trend

> Micro OfficeScan with the latest engine/virus definitions.)

>

[Guest Chris Benton]

Re: Server still functions, but cannot log in locally or remotely

 

Thanks. We're not running SBS, but 2k3 Standard Edition. I will give this

solution a try, however, and let you know what happens.

 

"Meinolf Weber" wrote:

> Hello Chris,

>

> Do you use SBS 2003? Have a look on this articles:

> http://blogs.technet.com/sbs/archive/2006/09/01/453504.aspx

>

> http://forums.techarena.in/small-business-server/844637.htm

>

>

> Also see here:

> http://support.microsoft.com/kb/924995/en-us

>

> 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

>

>

> > Running Windows Server 2003 SP1 on an HP DL380. A couple of weeks ago,

> > we developed a problem where we are unable to log in to the server

> > either locally or remotely. It will work okay for a few days, then we

> > get a gray screen with no login prompt, and we simply get disconnected

> > after a few minutes; however, clients are able to log in,

> > authenticate, and use server resources as if nothing's wrong. Only a

> > hard shutdown/restart clears up the problem. The event logs show

> > nothing amiss. Eventually, a login prompt will show up at the console,

> > but the login process takes over an hour and when I'm finally logged

> > in, I notice that no services are running at all. If I try to do

> > anything in Active Directory via MMC, I'm told that a DC cannot be

> > found. I'm mystified as to what could be causing this. Any ideas?

> > Virus/malware scans always come up negative. (We're running Trend

> > Micro OfficeScan with the latest engine/virus definitions.)

> >

>

>

>