Active Directory Issue

[dodger6]

Ok I have currently 1 Win2kAS running Active Directory Services.

I'm in the process of building a second machine Win2k Server to run SQL 2000. However I recieve a message when trying to join the second server to the Active Directory stating
"The domain "

http://www.XYZ.com"

cannot be contacted. Ensure that the DNS domain name is typed correctly. This condition may be caused by a DNS lookup problem. If this domain was recently created, its name may not yet be registered with the Domain Naiming Service. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Web site:

http://go.microsoft.com/fwlink.?LinkId-5171"

I entered my local domain rather than

http://www.xyz.com.

It was my understanding that Active Directory replaced the old PDC/BDC scheme and yet I was not aware that it required being registered with a naming service in order to run. How are you supposed to take advantage of AD if you are on a closed network? I know I'm missing something terribly obvious here. The entire network (client/server) is Windows 2000 by the way.


End objective:
Attach a secondary server to the existing Win2k network, this server will host a SQL2000 database and act as a backup to the primary fileserver.

Any assistance you can provide would be appreciated.

 

[vgrice]

Make sure the internal NIC on the DC is registering itself in DNS - TCP/IP Properties/Advanced/DNS. Also make sure that the DNS server is listing itself as the only DNS server ont the TCP/IP properties page. Vince Grice
vgrice@hotmail.com
MCSE Win2K, NT; MCSA; MCP+I

I not only use all the brains I have, but all I can borrow.
- Woodrow Wilson

 

[GlenJohnson]

Active Directory replaced the old PDC/BDC is correct. Are you running DCPROMO on the new machine to make it another dc or are you just trying to join the domain. Must be a dc to run ad. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"Take nothing on its looks: take everything on evidence. There's no better rule."
Charles Dickens (1812-1870); English novelist, dr

 

[zoeythecat]

On the second machine make sure your NIC is installed. Simply check device manager and make sure there are no yellow flags. If there are than reinstall the driver and then try the DCPROMO again.

 

[dodger6]

(vgrice) Not entirely sure what you mean by making sure the NIC is registering itself on the TCP/IP properties page. Register this connection's addresses in DNS and use this connection's DNS suffix in DNS registration are both checked. If I missed something on that lemme know.

(Glen Johnson) On machine #2 I joined the domain then ran DCPromo. Should machine #2 have been its own domain with a trust to the primary?

(zoeythecat) Yes the NIC is installed and running perfectly.

 

[zoeythecat]

I know this is probably basic stuff and you already checked this, but on the 2nd DC are your DNS settings from your TCP/IP properties pointing to the primary DNS server that would be the first DC? Recheck your TCP/IP (DNS Settings)

 

[dodger6]

Yes the primary server is the first ip listed under the DNS servers on the secondary machine.

 

[Guest_imported]

Did computer #2 successfully join #1's domain? Can you login to that domain?

 

[GlenJohnson]

It's been a while, but I believe we ran dcpromo without acutally joining the domain first. I'd have to do some research because of how long it's been. Strictly stand alone server, logging on locally, ran dcpromo, became the second dc. Something in the back of my mind thinks this is how we did it, but the grey matter isn't sure.

Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"Take nothing on its looks: take everything on evidence. There's no better rule."
Charles Dickens (1812-1870); English novelist, dr

 

[dodger6]

Machine 2 has sucessfully joined the domain, Yes.
Machine 2 logs into the domain and authenticates, Yes.