Active Directory

CatCheeto · February 4th, 2003, 01:15 PM

Hey, we have an active directory set up and I was trying to add a second domain controller to it. So I go into setup active directory and select add, put in the user and pass and such and it keeps telling me the direcoty doesn't exist. It is really odd since it gives me the option to search for the directory and it is right there. Any ideas? Need more info?

cadetstimp · February 4th, 2003, 01:42 PM

First make sure the "to be domain controller" is running and on the network. Make sure the existing domain controller can ping the new server and vice versa.

Then, on the new DC, click start, run and in the open feild type dcpromo and press enter. This will get the wizard started that will promote the server to a domain controller.

One thing to remember, if you ever decide to retire the new domain controller in the future - make sure to demote it before it is removed from the network and wiped clean. This will make sure it unregisters itself with the other domain controllers. Otherwise you may be left with a orphaned DC that really doesn't exist.

CatCheeto · February 4th, 2003, 02:27 PM

Ok, I type DCpromo, select Additional. Type in my user, pass, and full DNS (domain.biz lets say) It says that it cannot gain access to the list of domains in the forest anf that the specified domain either doesn't exist or could not be contacted. 2 things that are weird to me, I am logged onto the domain and the 2nd it filled in the domain name for me. So, I try just typing in "domain" without the .biz and it works. So, it then asks for the domain I wish to join and it has Domain.biz and it pop's up with "Domain cannot be contacted. Ensure DNS domain name is type properly. So I try server.domain.biz thinking it needs a computer on the domain. That doesn't work. Then I go with just "domain" and it tells me that the domain name "domain" refers to "Domain.biz, and is that what I intended. I hit yes. It ask where I wan't everything stored and I do the defaults, enter the defualt password for restore mode. It starts to try to transfer files and says "op failed. Failed finding a suitable DC for the domain domain.biz. It either doesn't exist or couldn't be contacted"

So, sorry for the long drawn out, but I wanted to give as much info as I could. I could ping the server, and the server could ping the new DC. I have domain admin rights with the user I am typing in and the user I am logged on to. Would any other info be helpful?

DVNT1 · February 4th, 2003, 03:18 PM

Sounds like it could be a problem with this computer's DNS server setting. Like it is not using the AD integrated DNS server but just some other DNS server.

CatCheeto · February 4th, 2003, 05:05 PM

Well, I know we set up the DNS on the first DC. I even see the all the computers and what IP's they have thru the DNS manager area.

cadetstimp · February 4th, 2003, 09:32 PM

As a standalone server - was its host name added to the existing domain successfully? Also, you're using a static IP on the new server right? Don't try to dcpromo until both machines can ping each other successfully via their host name.

CatCheeto · February 5th, 2003, 10:42 AM

Both names are in the DNS listing. I don't have the new server as static but its IP is shown on the DNS listing. Does it need to be static for sure? And to make it static I have to make a reservation for it correct? And how do I find out a mac address?

CatCheeto · February 5th, 2003, 11:35 AM

I don't know if this has anything to do with it, but I noticed I can't access other computers using for example server.domain.biz from the server. I can access every other computer from any other computer though.

cadetstimp · February 5th, 2003, 02:15 PM

It's good they're in the DNS listing, but can they ping each other?

Go to the command prompt on your existing domain controller and type ping and then the host name of the new server - does it a) return the correct IP address and b) does it respond or time out? Now do the same on the new server and try to ping the host name of the existing domain controller. This is square one....until both servers can ping each other’s host names and get a steady response nothing else will work.

To help trouble shoot and help with connectivity issues check the following on the new server:

1) Network card driver loaded and working
a) Does it look good in the device manager?
b) Can the new server ping its own local IP address and get a response?
i) This is a good indication the driver is working
2) Network card settings on the new server
a) Is it using the same subnet mask as the domain controller?
b) Is it using the same gateway as the domain controller?
c) Is it using the same DNS server addresses as the domain controller?
d) Is the IP address static?
i) Server IP addresses should be static and specified manually
3) Physical connectivity
a) Does the new server’s NIC show a solid LINK light?
b) Is the ether cable clicked in all the way?
c) Does the switch the server is connecting to show a good LINK light?

CatCheeto · February 6th, 2003, 01:54 PM

1)
a) y on both
b) y
2)
a) y
b) y
c) y and I added the servers ip since it acts as a DNS server
d) y
3)
a) y
b) y
c) y

Both computers can see each other just fine any way I try except for inside the dcpromo