Active directory and domain controll

[jassingh]

Hi all,

I'm configuring a server for my first time and have run
into some difficulties, We have a new windows 2000 server
machine with service pack 3.

On first boot, I ran the "configure my server" with the
only server on the network option so it would set up
DNS , DCHP and active directory services, however this
threw some error and did not complete correctly. I
eventually got it up via dcpromo however, i could never
connect any clients to this domian. I noticed an error on
the server on reboots was "duplicate name on network"
error. I guess this was causing confusion.

In an attempt to sort it out I demoted the server, hoping
to run the active server wizard again and the intention
to then redo all the options and other wizards for DNS.
Now, however, active directoy setup fails with the
error "network location cannot be reached."
(what network location is it looking for - is it the
domain?)
Is there any way i can like "reset" all this so it
configures DNS, DHCP and active directory all over again,
as i am starting to get quite lost for options to proceed
with.

And why did the original setup not go as smoothly as the
step by step guides walk us through?

thanks
Jass

 

[IceBall]

One first question: Did your ipconfig for the server point to your own ip? Very important for the DNS to funktion with AD.


MCSE+I NT 4.0
MCSE w2k

 

[jassingh]

Yes, the settings from ipconfig match those set for teh ip address i set for teh server

 

[GiaBetiu]

what does it mean: " however this threw some error and did not complete correctly" ?

As about reset all... what you want,, there are two possibilities:
1. reinstall OS
2. think
Option 2
First check your IP configuration on that server. ipconfig /all will give you an idea.
Is the server having static IP?
When you are sure that your IP is ok (ping from another computer to it and viceversa) then you can go to next step: DNS.
Check your DNS zones. Go to properties of that server (in DNS mmc) and see to which IPs is bound). Should be the address of your server (all,. you can have "all&quot.
Back to your IP configuration, set as DNS server for your network interface the address of the server (itself).
Go to "command prompt". then try nslookup. your server should anser to your request.
Whatever,. try these steps.
And don't forget, installing more things in the same time (thinking that all is a wizard) is not the right way.



Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[Seaspray0]

The "duplicate name on network" bothers me. Do you have two nics on this server attached to the same subnet? If you are applying the service packs seperately, wait until it is a domain controller before applying them. The route I've done with success is: during OS installation, use a static ip address and point the server to itself for DNS. After the default installation is complete, dcpromo to a Domain Controller (DNS will install automatically during this process), then add services like DHCP, WINS, etc, then add service packs. The last step, add other servers to the network but have them point to your first server as the DNS.