Win2kServer & service failure

banesong

Distinguished
Dec 31, 2007
43
0
18,530
I am having a very vexing problem lately. When I boot my server, it is taking a very long time (10 min) to complete the boot, and the "some services have failed" message comes up. When i check the event viewer, I notice that the NetLogon service hung while starting. I have no clue why this is happening? any suggestions? I have full network access, and it doesn't seem to be affecting anything but the time it takes to boot, but it is an annoyance to me. Thanks

Thomas
 
G

Guest

Guest
10 minutes to boot up Win2kSVR? Thats certainly not unusual :) It is a server after all and has a shitload of stuff to load and check on startup. As for the erros in your event viewer, don't worry about it. I am not sure but I think that its just telling you that your Domain name isnt actually registered. Sounds to me like you don't really have a problem. Servers arent meant to be rebooted often so the long bootup times are just something you'll have to deal with.
 

ws6

Distinguished
Dec 31, 2007
71
0
18,630
10 minutes to boot. that isn't bad at all for server. i run 2 win2k servers. 1 is a athlon 1 gig with 1 gig of memory and the other is a single 800 mhz p3 chip with a gig of memory. they both take a while to boot (usually around 12 min for the 800 and about 15 to 20 for the 1 gig). they are both thier own domain controlers but the i gig machine is also running exchange 2k, isa server, iss 5 web site, a very large active directory, sequal server, and chaperon 2k. the 800 is running onlyu the basic things. the net login thing is common if you are your own domain controler but you shouldn't get the error message. did you look in both app and system in the event logs?

chris t.

-----------
Chris
ws6@kc.rr.com
 
G

Guest

Guest
I ran into the same problem a while ago.
I am running 2 network cards in the server.
One NIC has Microsoft file & print sharing running, The other NIC does not.

Went into networking properties and clicked on the advanced tab.

I changes the boot order of the NIC's so that the one with file and print sharing loaded first.

this helped the problem for me.

if you are in the same boat just reply and I can give you a more technical explination.