I too have had similar issues with MSW2KS (2000 Server). For me, it began after, I added the latest MS Service Pack (4 I believe.) Additionally, I got the same problem with my MSW2KP (2000 Pro desktop).
Similar to you, I reinstalled from scratch my MSW2KS and on my MSW2KP. It was happy days again until- I ADDED Microsoft Service Pack Updates! Then, it took 5 to 15 minutes to complete a boot-up prior to my login screen on either the Server or Pro.
I am 'guess-timating' the security part of these service packs are performing intensive TCP/IP Port checks. My personal firewall (I use Outpost v2.5 by Agnitum) is going 'buck wild' with port scan activity when I boot up now. The history data is in my Outpost logs. A tremendous amount of various Window System application accessing 'out' to the localhost (my server 'loopback' as a remote PC) and 'in' from the localhost as well as IP address duplication of the same activity as localhost. (Instead of 127.0.0.1 as Remote or Local Host, it uses Internet Protocol e.g. 188.8.131.52, etc.). It is VERY REASSURING that no external IP addressing or Hostnames are showing up in my Outpost Firewall logs during this boot-up. If so, then, I DO HAVE A MAJOR PROBLEM! The fact that only my PC's are having application activity to itself, gives a high % of probability these are legitimate Microsoft System activity.
Because malicious Worms from Advertising Hackers, Computer Crackers, Mischievous Programmers, Industrial Espionage Hackers, and Terrorists, are so powerful, this problem may become a necessary evil for the near future. Consider, the more programs on your server that make use of IP ports (especially if initialize at boot-up), the more work an anti-virus/security pack software must work to protect. There are 65, 535 possible IP ports for TCP alone. Add, UDP, ICMP, IGMP, etc.- each with up to 65, 535 possible access ports to be protected! I think you may see the idea.
I have read many messages over the 'net' that others are complaining about MS service packs giving similar problems. Since, I am trying to host my own 'membership' server, I don't mind the slow boot-up, if it means better security. I awake, start my MSW2KP (my server is usually on), fix coffee, have a pastry, brush my teeth, contribute to the 'Ivory Princess' and return. It's been 15 to 20 minutes, and now I can 'login'. <s>
From what you have shown in your message, I believe your issues may be similar and are not a sign of a critical problem. I'm not certain, but, that's my take on it. Good luck!
So over the past couple of weeks, my computer has been a bit slowed at starting up. Usually it takes a few minutes to finish loading the operating system. Well, I had figured it was because I had installed a couple of things... didn't bother me too much at the time.
(For the record, since my computer had become slow... I had installed World of Warcraft and a Win2K/XP driver for a Compaq IJ300 InkJet printer.)
Well, yesterday I get home from a friend's house. I had stayed overnight and was planning on going over to another friend's house to chill for the evening when I decided to login to my computer for an hour or so. I startup my computer and after it runs through the Win2K loading screen (you know, the pretty screen; not the DOS screen with the DOS-designed loading bar)... it begins a physical memory dump.
"Okay, BSoD... not the first time someone's had that, I'll just let it run through then restart my machine."
So when it finishes, the computer restarts and I go through the startup process. I reach the same point (just after the loading screen, but before the Login screen would appear)... and to my amazement, I see another BSoD. This time, impatient, I restarted my computer manually. Again, same instance. Finally becoming really annoyed, I turned my computer off and gave it a couple of minutes. I restarted once more to no avail.
So finally, I decided to reformat my machine and reinstall Win2K. I didn't have anything priority that I might lose, so it didn't bother me too terribly bad. Anyway, the overall reinstall went okay. I had one BSoD appear, which made me iffy ("If this happens again, I'm screwed"). Didn't happen again, so that was fine.
So I start my system fresh for the first time, but for some reason I still have the slowed user startup. I login with no problem, but after the login screen, it can take as much as five minutes to load the system (keep in mind, with exception to drivers which I have had *no issue with* -- I've been using these since I built the machine, it is a fresh Win2K Server install).
Can anyone give me any ideas about what I should be doing?