RE: Event ID 14526 & 13529 and other errors

Hi,

We do have these same issue over here.
First we thought is was with DFS-FRS, but we keep on having this with DFS-R.

Event Type: Warning
Event Source: DfsSvc
Event Category: None
Event ID: 14526
Date: 7/16/2008
Time: 11:23:59 AM
User: N/A
Computer: DC1
Description:
DFS could not contact the DC1.Domain1.local Active Directory. DFS
will be using cached data. The return code is in the record data.

Event Type: Information
Event Source: DfsSvc
Event Category: None
Event ID: 14529
Date: 7/16/2008
Time: 11:24:41 AM
User: N/A
Computer: DC1
Description:

Situation:
- 12 DC W2K3-R2-SP2
- 3 Namespaces on each of our 3 "main" DC's (Each DC hold all 3 name spaces).
- Only on the DC with all FSMO roles this appears.
It can't find itself, so no network issues as far as I think.
DNS checked, also _msdcs\ settings.
- 14526 warning, and 1 - 50 sec later 14529.
- At the same time in SCOM (MOM 2007):
Date and Time: 16-7-2008 11:24:42 Description:
Log Name: Operations Manager AD Replication Monitoring : encountered a
runtime error. Failed to bind to
'LDAP://DC1.Domain1.Local/DC=ForestDnsZones,DC=Domain1,DC=Local' The error
returned was: 'The server is not operational.' (0x8007203A)
Source: Health Service Script
Event Number: 1000
Level: 2
Logging Computer: DC1
User: N/A
Event Data:


"Chris" wrote <Edited>:

> Hi group,
>
> We've been having the above errors in the System log of our domain
> controller for the past couple of weeks. I've run dcdiag and netdiag
> and will post all the pertinent information. The server holds all fsmo
> roles. Yesterday, I was not able to browse to \\domain.com\sysvol
> \domain.com on the actual server, though I could browse to this on my
> workstation. I restarted the server this morning and was able to
> successfully browse to the sysvol share. I have done some research on
> this and have tried the suggestions from eventid.net. I've also seen
> another post similar to this that pointed to this being a physical
> layer problem. I will check/replace the cable, nic driver and switch
> ports on the switch and post back the results. The only test I've seen
> fail on dcdiag or netdiag is systemlog. Also, NetBT name test shows a
> warning. I've looked at and addressed what I thought would be
> incorrect configurations (Enabled NetBIOS over TCP/IP and enabled
> Messenger service)....anyway, here's the errors from system log and
> netdiag/dcdiag.
>
> ************************************************** **********************************************