w2k pro shutsdown on startup

[mastermagik1]

One of our clients has a Dell Optiplex pc, when it boots into 2k the login screen appears and then shuts itself down. if your quick enough you can log in but the system still shuts itself down. Tried disabling virus s/w, updating nic drivers, display drivers but still exactly the same. I can boot into safe mode but nothing is logged in the event viewer. Also Automatically reboot is unticked.

 

[Palagast]

Mastermagik1,

I've encountered this problem once. It was because of faulty memory then. You can boot with a bootdisk and scan it with something like memtest.

Worth a try i'd say.

 

[mastermagik1]

cheers for that, just found out if i unplug the nic cable and boot up, it comes up ok. think it might be blaster virus, gonna scan and find out

 

[Palagast]

Doh, of course that could be it..
Should have thought of that myself

Good luck with it.

 

[mastermagik1]

ran msblast, stinger and spybot but found nothing

 

[Palagast]

Back to the drawing board then...
You say when you unplug your nic it works fine?
Reinstall nic drivers?
Replace nic?
Far-fetched, but is an administrator pulling a prank on you by remotely shutting it down?

 

[mastermagik1]

the pc booted up fine once, but now its not, only back into safe mode

 

[rislejay]

Is Group Policy enabling either "Shut down the computer when the security audit log is full" or "Shut down system immediately if unable to log security audits"? I had an issue similar to this happen after the user loaded up some sort of privacy cleaner. I uninstalled the app and everything was fine.

 

[MiggyD]

can you ping the network server (in either mode [safe/norm])?

I had a similar problem. I did exactly as you did: unplugged the cat-cable, logged on locally, users were able to access files on network--but they couldn't save there when using server-side apps/db (but otherwise they could save pics/texts locally).

If I plugged-in the cable and did "scanreg /restoredns" (see [red]*[/red] below) after a few minutes it would shutdown without warning. I later concluded it was due to the ASP updating that happens every few minutes.

I spent approx. 4 hours trying to figuer out what happened when the higher-ups finally told me they called in the company that caused this problem.

Came to find out that they [the company] "changed the server's domain name from 'A' to 'T'."

It figuers! The few days I take out for vaca and someone else is called in to destroy the system. [sarcasm] Heck, I could have done; and truely have my eyes closed.[/sarcasm]

The higher-ups said they wanted the changed on our server so that there would be no confusion with the other building's 'A' server.

Hope there's a bit of help in this disastrous story for you.

--MiggyD

[red](*)[/red] I'm uncertain if it was "scanreg.exe" or "net.exe" that was used. My 'IS log' is at work; so I'll have to check it out tomorrow and let you know.

 

[MiggyD]

Correction to: "...the ASP updating that happens..."

Should read : "...the Active Directory updating..."

What can I say? It's late for me.

 

[mastermagik1]

Thanks for all the help. in the end as the 2000 pro machine is used to host a sql app i needed to get the machine up asap, so decided to try a inplace/repair that made the machine not even go into safe mode, last resort done a parellel install of 2k pro and reinstalled the sql side without losing any data as the data was on the e: partition. Totally confused as why the original problem occured but needed to get the site running asap. Thanks for all the suggestions.