Cannot locate domain controller for active directory

[Jason Beveridge]

We have a Network with
1 x nt4 (service pack 6a) server
1 x win2k server
1 x 2003 server
All clients either win2k or XP Pro
NT 4 Server was PDC
I removed all clients from domain and renamed domain on PDC
(I still wanted access to PDC until phased out)
I created new domain on win2k server (same netbeui name as
old one)
I installed DNS at same time. DNS has fixed IP
Setup new accounts for users etc.
Attached clients to new Domain
Now when you log onto clients as domain, login is very slow
(10 minutes) and even if you login with domain admin logon
you cannot see domain users when setting priviliges.

I attempted to set 2003 server as another DC of same domain
but it reported:

"The computer could not locate a domain controller for
active directory"

I checked the order of DNS - OK
I ran DCDiag and it reported:

"Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\CCSERVER01
Starting test: Connectivity
CCSERVER01's server GUID DNS name could not be
resolved to an IP address. Check the DNS server,
DHCP, server name, etc
Although the Guid DNS name
(e3c9ab30-2b3a-4dfe-9ccb-093f001453e6._msdcs.controlcorp.local)
couldn't be resolved, the server name (ccserver01.controlcorp.local)
resolved to the IP address (192.168.0.254) and was pingable. Check
that the IP address is registered correctly with the DNS server.

......................... CCSERVER01 failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\CCSERVER01
Skipping all tests, because server CCSERVER01 is
not responding to directory service requests

Running enterprise tests on : controlcorp.local
Starting test: Intersite
......................... controlcorp.local
passed test Intersite
Starting test: FsmoCheck
......................... controlcorp.local
passed test FsmoCheck"


I then stopped NETLogon service and restarted and
rechecked. Same problem.

I ran netdiag /fix - all reported ok:

"Computer Name: CCSERVER01
DNS Host Name: ccserver01.controlcorp.local
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 10 Stepping 0,
AuthenticAMD
List of installed hotfixes :
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : ccserver01
IP Address . . . . . . . . : 192.168.0.254
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.99
Dns Servers. . . . . . . . : 192.168.0.254
192.231.203.132
192.231.203.3


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this
interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{E504A6A2-8EF0-41F1-9675-4942005F8806}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on
DNS server '192.168.0.254'.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E504A6A2-8EF0-41F1-9675-4942005F8806}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{E504A6A2-8EF0-41F1-9675-4942005F8806}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is
assigned.


The command completed successfully"

Any suggestions??

Cheers
Jason Beveridge

 

[Matjaz Ladava [MVP]]

Have you rejoined your clients to the new Windows 2000 domain ? You have
created a new domain and therefore you have to re-join your clients to your
new domain, because the new domain does not have their computer accounts.
Next thing to check is, that you are pointing your clients DNS settings to
the DNS server of the new domain.
To add a Windows Server 2003 as a domain controller to Windows 2000 domain,
you first have to extend the schema of Windows 2000 domain
http://support.microsoft.com/default.aspx?scid=KB;EN-US;325379
The error that you are getting is pointing to DNS problem. I would check,
that your Windows Server 2003 is pointing to the right DNS server, and that
you have all proper records present in your DNS server. Check that with
%systemroot%\system32\config\netlogon.dns file on your new domain DC.

--
Regards

Matjaz Ladava, MCSE, MCSA, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com

 

[Dave Shaw [MVP]]

From what I can gather, I think you have 2 domains: one Windows NT and one
Windows 2000 AD. You evidently didn't upgrade the NT PDC, meaning that when
you created a DC out of your Windows 2000 Server, you then had 2 domains.

If you want to have one domain and all computers in the same domain, demote
the Windows 2000 Server, move all the clients back into the NT domain, then
upgrade your PDC to Windows 2000 Server or Windows Server 2003. Once the
upgrade is complete, it will run DCPROMO and create the Active directory for
you. During that time, you can also configure DNS. Once done, point *all*
clients and servers to that DNS server.

If your current PDC won't handle the upgrade, take another computer that can
and install it as a BDC in the NT domain - then promote it to a PDC. Once
done, perform the upgrade as mentioned above.

-ds