Windows Forum

Ask something
Discussion Locked

Active Diretory

0 helpful
9 replies

by skper1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi all,

I 've just installed Active Directory om my win2k SRV /SP2. But every time I reboot the PC, it takes me 15 minutes to go to my desktop.

It stays at the preparing network connections when my PC loads and it stays there for 15-20 minutes. is that Normal??? it takes forever to go to my desktop every time i reboot my PC.

help pls.
Thank you, skper

9 replies

by beermonster

Hi,
This is usually caused by incorrect DNS setup. check that the server is pointing to the correct DNS address. If you installed dns onto the server during the dcpromo, and the server is pointing to itself for dns, then look in the forward lookup zone and confirm that the folders _msdcs, _sites,
_tcp and _udp are displayed. If not then look at the properties in dns for both the server and the zone, check the start of authority tab on each and confirm that the server and it's ip address are listed correctly. If not then edit as appropriate. Once thats done, stop and start dns and the dns client services (or just reboot the machine) and see if it's any quicker. Hope this helps...

by skper1

Hi BeeMonster,
I tried what you told me, I went to folders you said. But I'm a newbie on this AD. I just demoted my AD and it back to normal now. next time when i have more time I'll try to install AD again. Thank you so much for this reply. see you around Sir. Thanks Skper1

by akula

Domain controllers (the ones with the Active Directory store) take a very long time to boot up in Windows 2000. The idea is that a domain controller will only very rarely be shut down. That just goes with the territory.

by stngfan1

Some more information is needed.
How much memory do you have, and what is the speed of the cpu?
How many objects do you have in the AD?
You should at least have a min. of 128mb ram if not more. The CPU should be over 200 Mhz, more like 400 to have a decent response.

TM.

by joshg

Go with Answer 1, this usually happens while trying to resolve host names etc. When AD is first setup the first reboot will take this long but subsequent reboots should be quick unless problems contacting DNS.

This discussion is closed to new replies.