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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server joing DC??? 1

Status
Not open for further replies.
Jan 13, 2008
167
US
I have a Server that is a Domain Controller. called "Server" then I have another server "Server2" both running Windows Server 2003 R2 Standard.

Everything is good on "Server" however when I try to add the "Server2" as a domain controller by installing Active Directory and selecting child domain it goes to where it is trying to configure the machine and then says "The specified domain either does not exist or could not be contacted"

if I try to do it through my computer > properts> computer name> domain.... it doesn't prompt for a user name just says "Domain Could not be contacted"

I have another computer that connected just fine.

I have messed with DNS and WINS and nothing seems to help.

domain is tqi.data.com and full server name is server.tqi.data.com and server2.tqi.data.com I already added "Server2" to the "Server" in AD as a domain controller. Is it case sensitive?

Any help guys?!

Thanks in advance
 
Are you trying to create a new domain with Server2? If not, then you don't add it as a child domain.

Double check that the DNS setting on Server2 is pointing to your DNS server on your domain.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
I had to add it as a domain controller for DFS. I finally got it, it was a combo of DNS and Firewall stuff..

However now it's saying my DFS root isn't a vlid location
 
Your firewall was causing a problem between DC's within your network? That's even more curious...are you using your firewall as a router? What problems could it be causing?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
it's AVG Network Edition that pretty much blocks everything unless you give it the OK. So it blocks ports and programs and everything. So it blocked the communication from the server ip to the server2 ip. Once I disabled it I did it then you restart and it automatically adds it to AVG.

Weird I know, I didn't install that app the old network guy did... I have to admit though it does work well, graphic reports / remote admin etc
 
Oh...software firewall...

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top