• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 197
  • Last Modified:

Windows 2003 Server installed in NT Domain - Domain Controllers cannot be found.

We have installed a Windows 2003 Server/w AD in an NT Domain running Exchange 5.5.

Exchange Admin, along with many other resources are now unable to locate a Domain Controller on the Network. We THINK "DNS/WINS" are/were configured properly, but at this point, with so many changes (trying this or that) - we're not quite sure in which area(s) the problem(s) may lie. We can't connect any new users to the network as well - "Domain Controller could not be contacted".

Any suggestions as to which area we would need to focus on to try and solve this problem. Thanks.
0
terryadams
Asked:
terryadams
  • 2
  • 2
1 Solution
 
mikeleebrlaCommented:
exchange 2000 or 2003 must be installed on a 2000 or 2003 domain as they both use active directory.  They cannot be installed on an NT domain.  Do you have any 2000 or 2003 domain controllers?
0
 
Greg JacknowCommented:
What you said does not really make sense in that if you have 2003 server with AD running, as it is no longer an NT domain.  It is now a 2003 AD domain.  :)

Am I interpretting what you said correctly?  Did you upgrade you NT domain to 2003 AD?  Was this on purpose?  :)

To upgrade from NT you would have had to installed 2003 server on your NT4 PDC.  If you just installed 2003 server on a seperate box and then promoted it to a DC (and named the domain the same) then you now have two seperate domains with the same name.

Assuming you have done the upgrade on purpose and you now have a 2003 DC and some NT bdcs you should still be running in mixed mode.  You should (don't have to but it works best) have DNS running on your 2003 DCs (get at least 2) running in active directory integrated mode. (dynamic DNS takes over from WINS and browsing in 2000+.  Your DCs need to point to themselves (or each other) to correctly register their service record for AD.  You need to make sure you 2000 and up workstations and servers all have the windows DNS servers as their DNS server.

If you add a few details about the config of your domain controllers, (ie how many, what OS etc) and network (1 subnet or many) then we could help more.

This article http://support.microsoft.com/default.aspx?kbid=324753&product=winsvr2003
has a bunch of stuff about DNS on the bottom.  It is important that you can see that you AD DC are correctly registering themselves with DNS.

Greg J
0
 
mikeleebrlaCommented:
Greg, I'm glad i wasn't the only one that was confused.
0
 
Greg JacknowCommented:
Yes Mike I could see that.  As he clearly said exchange 5.5   :)

Sorry I could not resist. :)

Greg J
0
 
terryadamsAuthor Commented:
Thanks gjacknow1. My stated question (re-reading it) was a bit confusing - as we were in fact in a 2003 domain vice NT with the installation of A/D. Our DC's had not been registered as you had suggested. We made those corrections and the problem has been resolved. Thanks to all for the replies.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now