Archived from groups: microsoft.public.win2000.active_directory (More info?)
Which DC does your AD clients point to for DNS?
DDS W 2k MVP MCSE
"Rick T." <Rick T.@discussions.microsoft.com> wrote in message
news:7D02169C-C96F-4C18-9359-3210DFFEEE1D@microsoft.com...
> We have a Win2k domain running in mixed mode with 2 DC's. DC #1 has all
> fsmo
> roles. If we take DC #2 down, nobody can logon. What are we doing wrong?
Archived from groups: microsoft.public.win2000.active_directory (More info?)
operations master pointed to the production server?
"Danny Sanders" <Danny.Sanders@NO-SPAMcpcmed.org> wrote in message
news:u5ANrh0HFHA.896@TK2MSFTNGP10.phx.gbl...
> Which DC does your AD clients point to for DNS?
>
>
> DDS W 2k MVP MCSE
>
> "Rick T." <Rick T.@discussions.microsoft.com> wrote in message
> news:7D02169C-C96F-4C18-9359-3210DFFEEE1D@microsoft.com...
> > We have a Win2k domain running in mixed mode with 2 DC's. DC #1 has all
> > fsmo
> > roles. If we take DC #2 down, nobody can logon. What are we doing wrong?
>
>
Archived from groups: microsoft.public.win2000.active_directory (More info?)
Yes, this is almost certainly the issue. However, don't rule out a GC. By
default the forest root (I assume DC01) is a GC, but you may have changed it
per the not-as-clear-as-they-could-be Infrastructure Master/ GC conflict
event log instructions.
If you've only got two DCs make them both GCs. The IM is defunct in a flat
forest (single domain). Also, make both DCs AD-Integrated DNS servers.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
DC#1 is the GC, operations master, and all clients point to it for DNS.
"Danny Sanders" wrote:
> Which DC does your AD clients point to for DNS?
>
>
> DDS W 2k MVP MCSE
>
> "Rick T." <Rick T.@discussions.microsoft.com> wrote in message
> news:7D02169C-C96F-4C18-9359-3210DFFEEE1D@microsoft.com...
> > We have a Win2k domain running in mixed mode with 2 DC's. DC #1 has all
> > fsmo
> > roles. If we take DC #2 down, nobody can logon. What are we doing wrong?
>
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.