Global Catalog / DNS Server Down

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Initially, one of the Windows 2000 servers (Server A) was the single global
catalog server and primary DNS server. However, when/if this server went
down nobody was able to authenticate to the domain.

To create a level of redundancy and ensure minimal downtime, I made my other
Windows 2000 Server (Server B) a GC as well. This machine was already a
backup DNS server.

Server A is currently down and users cannot access any network shares or
resources.

I thought I had taken care of this by making Server B a GC server as well,
but apparently I am missing something here. What can I do at this point to
resume normal operations, and what should I have done differently to prevent
this????
 
vzrogers said:
Initially, one of the Windows 2000 servers (Server A) was the single global
catalog server and primary DNS server. However, when/if this server went
down nobody was able to authenticate to the domain.

To create a level of redundancy and ensure minimal downtime, I made my other
Windows 2000 Server (Server B) a GC as well. This machine was already a
backup DNS server.

Server A is currently down and users cannot access any network shares or
resources.

I thought I had taken care of this by making Server B a GC server as well,
but apparently I am missing something here. What can I do at this point to
resume normal operations, and what should I have done differently to prevent
this????
Click to expand...
Are the clients set to use BOTH of the DCs as DNS in the NIC
properties?

Cheers,

Cliff
 
Check whether sysvol folder is shared and you can view all the properties. I

had similar problem and I have given information of how to resolve under
your question.
 
Back
Top