Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cannot setup second dc in 2000

Status
Not open for further replies.

extendedping

Technical User
Nov 15, 2001
7
US
hi all, working on home lan, have 1 2000 domain controller and am trying to set up second dc, when i run active directory setup or dcpromo message says cannot locate domain or domain controller (says "domain x cannot be contacted")both computers are on same subnet and have second computer on domain just not as domain controller. when setting up first dc i choose to have dns set up automatically and now don't see any zones in dns could this be a problem? also i tried putting first domain controller ip address in dns properties for second server which was suggested but didn't help. any suggestions would be greatly appreciated.
 
I guess the two systems can ping each other and stuff ?
check the event logs and check if there are any errors with the LAN connection and the logon process.
Try a different NIC in the second server....
can the workstations see (ping) both servers ? can they connect to shares on both ?

just a few thoughts.....

Jon. ----------------------------------------
To be is to do (Sartre)
To do is to be (Casmus)
Do be do be do (Sinatra)
----------------------------------------
 
thanks for response, i can ping both, and can log into the domain from the second computer, no errors in event log and nic working fine in both.
 
if you're using the "configure my server" wizard, and try to install active directory, do you see any errors ?
[ it's a while since I last did a DC install ]

Jon. ----------------------------------------
To be is to do (Sartre)
To do is to be (Casmus)
Do be do be do (Sinatra)
----------------------------------------
 
yes the message is "domain x cannot be contacted" where x is the domain name fakedomain.com
 
This is definitely a DNS problem. First, try pinging the DC from the new computer using its FQDN (fully qualified domain name). Make sure the new DC has the DNS IP configured for the NIC. Verify by accessing nslookup at the command prompt on the new and existing DCs. Also, can go to DNS MMC in Administrative Tools, right-click on server, choose properties, and go to the Monitoring tab. From here you can perform iterative and recursive queries on the DNS database.
 
assuming that your first DC is running DNS :
configure the second server TCP/IP settings so that its primary DNS is pointing to the first DC
Do not install DNS server on the second DC yet, let dcpromo handle that... ---------------------------------------------------------------------
I have not failed, I've just found 10,000 ways that don't work
---------------------------------------------------------------------
Peter Van Eeckhoutte
peter.ve@pandora.be
*:->* Did this post help? Click below to let me know !
 
when i look at dns i dont see any zones defined, when setting up active directory ileft default option which was to have dns set up automatically, does this mean it's not set up and if i need to set it up manually, what is a srv record i've heard you need that but have never worked with it before, thanks.
 
that would mean it is set up automatically... If not, then you will have to set it up manually on your first DC.
An SRV records is a DNS record which points to a resource... eg. a domain controller.
Win2K uses DNS to locate DC's... ---------------------------------------------------------------------
I have not failed, I've just found 10,000 ways that don't work
---------------------------------------------------------------------
Peter Van Eeckhoutte
peter.ve@pandora.be
*:->* Did this post help? Click below to let me know !
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top