WIN2K Server Startup Delays

[centauri]

Friends,

I have a big problem with our Windows 2k Server. It started when the server was not properly shutdown by my colleague.
Since then i have been experiencing these problems during startup:

a) It takes 15 minutes to complete "Preparing Network Connections...".
b) It takes 10 minutes to complete "Loading Personal Settings...".
c) One of the services called NET LOGON won't start automatically thus it has to be started manually.

This is my daily routine and it is very frustrating because a lot of time is being wasted and so I need help to solve these woes. Thanks in advance.

[Jeordiewhite]

Please no need for double posting.
Your other post is still there waiting for someone to reply, not many people are online at this hour anyway.

What does your event viewer have to show? That might be very useful checking it. Also have you tried a virus or trojan scan, maybe even run ad aware or spybot for any bad programs?

If you don't have much info in the event viewer then this will make it much harder to isolate the problem, also have you run windows update recently?

If nothing in the even viewer than you may have to consider a reinstall or maybe a repair, however the repair doesn't always catch everything, your best option would be to reinstall of nothing else is showing up as a problem.
Maybe back up your stuff and sit down with your colleague and make sure he doesn't do it again

Just back up all your important stuff and maybe do a reinstall.
However if incase your event viewer does hold some useful information go check http://support.microsoft.com/default.aspx
the knowledge database for any information to see if it comes up with any fix for your situation or if it shows what network services you could try reinstalling the networking services, that have corrupted.
be sure to back up any files that you may need like config files or other files like with the ftp or http.
good luck

[DVNT1]

The problems you mentioned are very vague so far. Like Jeordiewhite was saying, you really to look at Event Viewer closely and check for a virus.

As a side note, why even shut down the Server everyday? I run many W2K Servers that are never shutdown or rebooted unless they get updated (or one has a specific problem).

[centauri]

Mr. Jeordiewhite,
Thanks for your concern and reply. Allow me to answer some of your questions:

I have been updating my virus definitions everytime Symantec posts new ones. I have been doing manual virus scanning aside from the scheduled/automatic (2x a day) scanning and found no virus.

Regarding adwares, I never run such type of programs in my server because of annoying pop-ups.

In the event viewer the following services are having errors: DHCP Server, Net Logon, Service Control Manager and Remote Access. I have already tried Repair Install but still nothing has changed. I also updated Windows by installing Service Pack 2; I have not installed SP3 & SP4 because there is only 978 MB disk space left in the system drive C.

I cannot do fresh install because we have an accounting software called Sun System 4.2.6 running wherein only the vendor knows the installation steps. The vendor will charge us a huge amount in case of new installation.

Lastly i'll try to check the microsoft link you gave hoping i could find other solutions. Once again, muchos gracias.

***********************************************

Mr. DVNT1,
Thank you very much also for your reply.
Sir, it is the decision of the management to shut down all equipments including servers because of the following reasons:
- we only operate from 8.30a-5.30p and to conserve power, all equipments are turned off after office hours.
- to keep the server running overnight might be a fire hazard since aircons and other ventilations are turned off.

Although there was an incident that I forgot to turn off the server and it was running overnight, I was reprimanded for what I've done for fear that the machine will possibly go overheat.

[PresterJohn]

centauri,

i am reading these posts and find a couple of troubling remarks which poses some questions

1) do you backup the data on your server? if you do, more than likely, it would make restoring/supporting the accouting package much easier, not to mention that the data is of paramount importance, is it not?

2) c: is running low on space. is this where your data files are stored as well? how are you going to manage this as space decreases?

some short terms trouble-shooting tips:

- as the others already mentioned, you must look thru your event logs, particularly the system log.

- without knowing more info, we are reduced to guesses. the problem area might possibly be the nic or the nic driver...the other possiblity is corruption in the server service or one of its dependencies.

first thing you should do is make sure you have the data backed up. next look at your device manager to see if there are any problem areas. next you need to look into applying SP4 to the install...this might possibly clear up the problem.

incidentally, what type of hardware is this server running on and what type of disk subsystem are you using (scsi or ide, is there raid of any type, etc)? it sounds like your budget is limited...is this a desktop-type pc or a rack-mount 'server' hardware?

[centauri]

Presterjohn,

Sir, thanks for dropping by. I really appreciate your help in solving my problem. Just recently I visited the MS support site and all of you were right that I have to get some vital info from the event log first. Using the Event IDs, I was able to identify the root of the problem and at the same time got the corresponding solution. I will be applying the changes later including the installation of SP4 and I hope these things will work. Just have to keep my fingers crossed. Also I'll be doing your recommended tips too.

With regards to your questions, here are my answers:
- It is already an SOP on my part to back up data on a daily basis. But right now I am just storing my backups on a separate drive. Maybe later i'll be using tape backups.
- Actually the former systems and data officer used a separate drive (D) for the data. And if I'm installing other apps, i installed them there also.
- Our server actually is IBM e-Server, P3 800Mhz, 512 MB desktop-type PC.

Muchos Gracias once again!

[Siliconjunkie]

Check the DNS settings. Borked DNS servers will kill 2k at boot.