Backup Domain Controller problem

[Saucer Man]

I hope this is the correct newsgroup. I don't see much activity. Please
advise if this should be posted in a different group.

When our PDC is down, the BDC is showing some issues. PCs can logon,
however, not fully. The event logs show NETLOGON 5719 errors and
GroupPolicy 1129 errors. There are also Time-Service 129 warnings and DNS
Client Events 1014 warnings. In addition, the drive mappings fail with the
notification area pop-up "Could not reconnect all network drives."

Anyone know what is wrong and how to address this problem? Our DCs are
Windows 2003 Server.

Thanks!


--- Posted via news://freenews.netfront.net/ - Complaints to ***@netfront.net ---

[pete]

Post by Saucer Man
I hope this is the correct newsgroup. I don't see much activity.
Please advise if this should be posted in a different group.
When our PDC is down, the BDC is showing some issues. PCs can logon,
however, not fully. The event logs show NETLOGON 5719 errors and
GroupPolicy 1129 errors. There are also Time-Service 129 warnings and
DNS Client Events 1014 warnings. In addition, the drive mappings fail
with the notification area pop-up "Could not reconnect all network
drives."
Anyone know what is wrong and how to address this problem? Our DCs are
Windows 2003 Server.
Thanks!

Microsoft closed all the public NNTP groups last year (though some
activity still happens here) and moved them to their own forums.
cf: http://social.technet.microsoft.com/Forums/en-US/categories

as for your question, PDC/BDC hasn't really been the case since NT4 days.
Windows 2000 and beyond uses a multimaster way of handling authentication
requests but there are still some tasks that need to be handled by a
single specified computer (like changing passwords) - thus the PDC
Emulator role.
If you have to shut down your domain controllers (maintenance, patching,
etc) you should transfer any of the Operations Master roles to other
domain controllers first.
The DC with the PDC Emulator role is also automatically designated the
time server for the domain. Recommend pointing to a reliable external NTP
server or even an edge router might be a more stable option.
And if you have any mapped network drives to your "PDC", then yes you
will get errors. You might also get the network drive errors if you are
using DFS and only have the mappings stored on your "PDC" (though that
*shouldn't* be the case).

Hope that helps

[Saucer Man]

"pete" wrote in message news:4ec2ec4e$0$29892$c3e8da3$***@news.astraweb.com...


Microsoft closed all the public NNTP groups last year (though some
activity still happens here) and moved them to their own forums.
cf: http://social.technet.microsoft.com/Forums/en-US/categories

as for your question, PDC/BDC hasn't really been the case since NT4 days.
Windows 2000 and beyond uses a multimaster way of handling authentication
requests but there are still some tasks that need to be handled by a
single specified computer (like changing passwords) - thus the PDC
Emulator role.
If you have to shut down your domain controllers (maintenance, patching,
etc) you should transfer any of the Operations Master roles to other
domain controllers first.
The DC with the PDC Emulator role is also automatically designated the
time server for the domain. Recommend pointing to a reliable external NTP
server or even an edge router might be a more stable option.
And if you have any mapped network drives to your "PDC", then yes you
will get errors. You might also get the network drive errors if you are
using DFS and only have the mappings stored on your "PDC" (though that
*shouldn't* be the case).

Hope that helps