DC problem

  • Thread starter Thread starter Patrick
  • Start date Start date
P

Patrick

We have an network with two DC's. Primairy W2K server and secondairy W3K
server. Everything works fine, only when the primairy server goes down or
off the network clients are not able to logon to the domain. When i start AD
Users and Computers on the secondairy server at that moment i'am not able to
connect to the domain also. Someone?

Patrick
 
make the DNS zone AD integrated and install DNS service on the other server.
If you have only one domain you can make the other server a Global Catalog.
 
The DNS service is installed and AD integrated. The two servers are both in
the same domain end both have a Global Catalog. And every time the primary
server is down clients are not able to logon and get authenticated.
 
how is the DNS configured on the client side? are both DNS servers setup on
clients?
 
make the DNS zone AD integrated and install DNS service on the other server.
If you have only one domain you can make the other server a Global Catalog.
Click to expand...

If he has AD he must have at least a partially working DNS service,
I'd say. However as you imply, it may not be set up properly.

You do not have to have the DNS on the DCs. In my first AD setup I had
the DNS running on member servers (for a number of good reasons).

Cheers,

Cliff
 
Cheers,

Cliff
--

These twin-CPU hyperthreading computers are really
great! We can wait ten to a hundred times faster
these days.
Click to expand...

DNS service is running on both DC's. And the clients are pointing to both.
When i do a nslookup on a client when the primary DC is down adressen are
shown correctly for the primary as the secondary. Only clients are not
authenticated for network resorces on the second DC. When the primary DC is
up and runnen again network resorces on the secondary DC are available again
for the clients.


Patrick
 
Okay I found this in the eventlog.

The File Replication Service is having trouble enabling replication from
DCPRIMARY to DCSECONDARY for c:\winnt\sysvol\domain using the DNS name
DCPRIMARY. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DCPRIMARY from this
computer.
[2] FRS is not running on DCPRIMARY.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

[1] When i do a nslookup from de SECONDAIRY server the name is resolved.
[2] FRS is running on the primary server
[3] Yeah right, over four days replication should have taken place between 2
DC's

So what else can cause the problem?

Patrick
 
Ow sorry about that, in the future i will pay more attention to signatures
:) btw the problem is solved. Reloaded the sysvol directory on the dc from a
backup and started the netlogon and ntfrs service with the
NTFRS_CMD_FILE_MOVE_ROOT command in the sysvol root. After that everything
was working properly.

Patrick

Probleem is opgelost. Heb de sysvol directory terug gelezen vanaf een backup
en met NTFRS_CMD_FILE_MOVE_ROOT commando file netlogon en ntfrs opgestart.
Hierna werkte alles naar behoren.
 
Back
Top