Re: Event Viewer Anomoly



Hello Parvardigar,

Please give some more infos about the kind of server, Domain controller DNS DHCP etc. and how they are located. Also what Operating system with which SP you run.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

I run the company and need to pay attention to technical matters. I
examined the event viewer. What is have listed below are shorted
version of the event. My impression is the event viewer should be
relatively clean.

I asked the Sys Admin to fix these issues. That was weeks ago. Am I
overreacting? I'm thinking the network should be without blemish.
We're using IP addresses to map over the Wan and I prefer FQDN. I told
the Sys Admin it's only three servers and 25 computers -and it
shouldn't be too esoteric to fix things.
Anyway have a look at these persistent events and let me know if I'm
too concerned.
Event Type: Error
Event Source: NETLOGON
Event ID: 5775
Deregistration of the DNS record
'_gc._tcp.Warehouse._sites.laeyeworks.com. 600 IN SRV 0 100 3268
LADC1.laeyeworks.com.' failed with the following error:
DNS operation refused.
Event Type: Error
Event Source: NETLOGON
Description:
The File Replication Service is having trouble enabling replication
from EYEWORKS-BDC to EYEWORKS-PDC2 for c:\winnt\sysvol\domain using
the DNS name eyeworks-bdc.laeyeworks.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name eyeworks-
bdc.laeyeworks.com from this computer.
[2] FRS is not running on eyeworks-bdc.laeyeworks.com.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers.
Event Source: DNS
Event ID: 4004
Description:
The DNS server was unable to complete directory service enumeration of
zone .. This DNS server is configured to use information obtained
from Active Directory for this zone and is unable to load the zone
without it. Check that the Active Directory is functioning properly
and repeat enumeration of the zone. The event data contains the
error.
Event Type: Error
Event Source: NTDS KCC
Event ID: 1311
Description:
The Directory Service consistency checker has determined that either
(a) there is not enough physical connectivity published via the Active
Directory Sites and Services Manager to create a spanning tree
connecting all the sites containing the Partition
CN=Configuration,DC=laeyeworks,DC=com, or (b) replication cannot be
performed with one or more critical servers in order for changes to
propagate across all sites (most often due to the servers being
unreachable).
For (a), please use the Active Directory Sites and Services Manager to
do one of the following:
1. Publish sufficient site connectivity information such that the
system can infer a route by which this Partition can reach this site.
This option is preferred.
2. Add an ntdsConnection object to a Domain Controller that contains
the Partition CN=Configuration,DC=laeyeworks,DC=com in this site from
a Domain Controller that contains the same Partition in another
site.
For (b), please see previous events logged by the NTDS KCC source that
identify the servers that could not be contacted.
These are the most glaring examples. It's just over the wire, a Wan,
office to factory, a three mile distance. With such a tiny network I'd
think our SysAdmin could easily correct these anomalies.

Thanks
Mark S


.



Relevant Pages

  • RE: Strange Irregular DNS/Networking Problems
    ... Never heard about this kind of problem with IPv6, but think this is because it is not used so much until now. ... What i heard is that firefox or some other not MS browsers and addons make problems with DNS resolving after changing DNS servers. ... After resetting the domain controller and booting up things are back ...
    (microsoft.public.windows.server.dns)
  • Re: Traveling Users Unable to Authenticate to AD
    ... authenticate to your AD while on the NDS network and you believe that DNS is ... One question that comes to mind is what DNS server is the client machine ... domain on the us.parent.com name servers. ... > MYCO.US.PARENT.COM Active Directory, get their mapped drives, access to ...
    (microsoft.public.windows.server.active_directory)
  • Event Viewer Anomoly
    ... DNS operation refused. ... The File Replication Service is having trouble enabling replication ... The topology information in the Active Directory for this replica ... performed with one or more critical servers in order for changes to ...
    (microsoft.public.win2000.networking)
  • Re: Event Viewer Anomoly
    ... I would also make the so called "BDC" a DNS server and use Active directory ... DNS servers as preferred DNS on the NIC itself and secondary the other. ... The File Replication Service is having trouble enabling ...
    (microsoft.public.win2000.networking)
  • Re: new domain setup
    ... DCs DNS servers. ... The only services that I usually allow to run on my DCs are DNS and DHCP... ... > Domain Controller for now until I can go get the other machines. ... Boot from CD and do base install. ...
    (microsoft.public.windows.server.setup)