Event Viewer Networking Connectivity

I need help. My company recently hired a new system administrator
replacing the former because of health reasons.

What we need is a very solid working network. I know enough, with
respect to the network, to get around. However, the duties of
maintaining this WAN belong to this systems administrator.

There are a few concerns. This fellow always presents a solid
explanation. He's new and I realized he would need a couple weeks to
settle in. Recently he informed me over at the warehouse the BDC
needed replacing. This topic came up because 'what used to work' no
longer works. I told him there were no indications in the event viewer
that we had a problem. He delivered a plausible explanation. But - I
was doubtful.

Here's what lead up to this scenario of BDC replacement.

Obviously I need to keep watch on this fellow as it is our company's
network and database. We do not have margin for mistakes. For a decade
nothing other than an occasional hardware failure -occurred. We may
say the network has been stable. No crashes, no rebuilding.

To keep alert I examine the netscreen logs, the event viewer, the
various applications -backup exec, terminal server, citrix, Navision
database and so forth.

The event viewer on the PDC, Term, BDC is use event viewer and connect
to the other servers from the workstation. An established habit for
years. Well I couldn't connect to the BDC. I mentioned this and he
explained the BDC was in need of replacement -the failure would be
immanent. It's a Dell desktop, Optiplex, 7 years old. I knew we needed
to replace it. But I was dubious if he was interpreting events
accurately.

I mention in remote desktop (Citrix) I could access the server but I
couldn't access the BDC. That bothered me. I told the system
administrator that in network neighborhood I could see all the
machines -except now I can't see the BDC.

On the corporate side I can see our servers. I went over to the
warehouse. On the BDC I can see all the computers on there side. But
not the PDC, Term, at the corporate office.

I can ping. Network wide logins. Everything as it should be -but I
can't view from the corporate office -in event viewer, in remote
desktop, in network neighborhood the Warehouse, BDC.

That bothered me. I'm convinced it's a DNS issue. That the situation
can be corrected within the Operating System. That the BDC is fine.

Please examine the event viewer saves posted below. If I can get a
strait understanding on the above stated anomaly, connection issue,
with the BDC, that would be encouraging. We're running windows 2000
server. I'm reading a screen shot: "Unable to connect to the BDC -
Network Path Not Found"
This is why is so perplexing. The new fellow says not to worry. The
users login from the Warehouse to Term, Citrix, and use the Navision
database located on the PDC. So we have network connectivity. I hope
my anxieties are unfounded.

Starting with Pdc > Term > BDC
Thanks for everyones assistance:

PDC Event System DNS August 11 2007

A few just from Saturday morning. 1,2,3. 4 & 5 from early morning. So
what's happening DNS Netlog early am?


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/11/2007
Time: 6:40:55 AM
User: N/A
Computer: EYEWORKS-PDC2
Description:
Registration of the DNS record
'_gc._tcp.Corporate._sites.laeyeworks.com. 600 IN SRV 0 100 3268
eyeworks-pdc2.laeyeworks.com.' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

----------------------------------------------
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/11/2007
Time: 6:40:43 AM
User: N/A
Computer: EYEWORKS-PDC2
Description:
Registration of the DNS record
'_ldap._tcp.Warehouse._sites.gc._msdcs.laeyeworks.com. 600 IN SRV 0
100 3268 eyeworks-pdc2.laeyeworks.com.' failed with the following
error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

----------------------------------------------------------------------
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/11/2007
Time: 6:29:51 AM
User: N/A
Computer: EYEWORKS-PDC2
Description:
Registration of the DNS record 'laeyeworks.com. 600 IN A
192.168.254.5' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..


==========================
4

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/11/2007
Time: 2:29:42 AM
User: N/A
Computer: EYEWORKS-PDC2
Description:
Registration of the DNS record 'laeyeworks.com. 600 IN A
192.168.254.5' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

5

Registration of the DNS record '_ldap._tcp.gc._msdcs.laeyeworks.com.
600 IN SRV 0 100 3268 eyeworks-pdc2.laeyeworks.com.' failed with the
following error:
DNS operation refused.

PDC Event Directory Services August 11
Repeatedly, unendingly, constantly
Knowledge Consistency Checker Event 1166 Event 1311

Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 8/11/2007
Time: 9:17:53 AM
User: N/A
Computer: EYEWORKS-PDC2
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.

-------------------------------------------------------

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 8/11/2007
Time: 9:17:53 AM
User: N/A
Computer: EYEWORKS-PDC2
Description:
All servers in site
CN=Warehouse,CN=Sites,CN=Configuration,DC=laeyeworks,DC=com that can
replicate partition CN=Configuration,DC=laeyeworks,DC=com over
transport CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=laeyeworks,DC=com are
currently unavailable.


PDC Event Applications August 11

Are you taking responsiblity on this core System Admin function. A
fully implemented backup?
The last backup:
August 5th ??
You said you ran a 'manual backup' Friday?
There's real time (users and network and stablity) and there's past
time (backup in event of the unexpected).
Your priorty should be user/network stablity and current media backup.



------------------------------------------------
Event Type: Information
Event Source: MSSQL$BKUPEXEC
Event Category: (2)
Event ID: 17055
Date: 8/11/2007
Time: 9:37:09 AM
User: EYEWORKS\mvincetti_admin
Computer: EYEWORKS-PDC2
Description:
8128 :
Using 'xplog70.dll' version '2000.80.760' to execute extended stored
procedure 'xp_msver'.

Data:
0000: c0 1f 00 00 0a 00 00 00 À.......
0008: 17 00 00 00 45 00 59 00 ....E.Y.
0010: 45 00 57 00 4f 00 52 00 E.W.O.R.
0018: 4b 00 53 00 2d 00 50 00 K.S.-.P.
0020: 44 00 43 00 32 00 5c 00 D.C.2.\.
0028: 42 00 4b 00 55 00 50 00 B.K.U.P.
0030: 45 00 58 00 45 00 43 00 E.X.E.C.
0038: 00 00 07 00 00 00 6d 00 ......m.
0040: 61 00 73 00 74 00 65 00 a.s.t.e.
0048: 72 00 00 00 r...

---------------------------------
Upon reveiw reinserted Tape

Event Type: Information
Event Source: Backup Exec
Event Category: None
Event ID: 58061
Date: 8/11/2007
Time: 4:15:37 AM
User: N/A
Computer: EYEWORKS-PDC2
Description:
Backup Exec Alert: Media Insert
(Server: "EYEWORKS-PDC2") (Job: "Nightly Backup") Please insert
overwritable media into the drive.

Overwritable media includes scratch, blank, and recyclable media.
Please note that depending on the current Media Overwrite Protection
setting, imported and allocated media may be overwritable as well.
Consult the online help for more information on overwritable media.

Respond Yes to acknowledge.
Respond No to retry the operation.
Respond Cancel to cancel the operation.

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml


--------------------------------

Term Server System Event

Consistent, Persistent
The log is full taking back to 7/30/2007

Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1010
Date: 8/11/2007
Time: 3:00:47 AM
User: N/A
Computer: EYEWORKS-TERM2
Description:
The terminal services could not locate a license server. Confirm that
all license servers on the network are registered in WINS\DNS,
accepting network requests, and the Terminal Services Licensing
Service is running.

Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1010
Date: 7/30/2007
Time: 11:14:12 AM
User: N/A
Computer: EYEWORKS-TERM2
Description:
The terminal services could not locate a license server. Confirm that
all license servers on the network are registered in WINS\DNS,
accepting network requests, and the Terminal Services Licensing
Service is running. .


Term Server Application Event


This Event never existed until 6/18/2007 and is now in repetition.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 8/11/2007
Time: 9:18:48 AM
User: NT AUTHORITY\SYSTEM
Computer: EYEWORKS-TERM2
Description:
Windows cannot determine the user or computer name. Return value
(1722).
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 6/18/2007
Time: 3:36:48 PM
User: NT AUTHORITY\SYSTEM
Computer: EYEWORKS-TERM2
Description:
Windows cannot determine the user or computer name. Return value
(1326).


BDC Sunday Event Viewer


Directory Services

Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 8/12/2007
Time: 6:21:04 AM
User: N/A
Computer: EYEWORKS-BDC
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.
_______________________________________________

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1265
Date: 8/12/2007
Time: 6:21:04 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
The attempt to establish a replication link with parameters

Partition: DC=laeyeworks,DC=com
Source DSA DN: CN=NTDS
Settings,CN=LAEXCHANGE1,CN=Servers,CN=Corporate,CN=Sites,CN=Configuration,DC=laeyeworks,DC=com
Source DSA Address: b81f3db5-a3a9-421d-
bb2a-2141dc82b9cc._msdcs.laeyeworks.com
Inter-site Transport (if any): CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=laeyeworks,DC=com

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup
failure.

The record data is the status code. This operation will be retried.
Data:
0000: 4c 21 00 00 L!..


BDC Sunday Event Viewer


System Log

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/12/2007
Time: 2:56:42 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
Registration of the DNS record
'_kerberos._tcp.dc._msdcs.laeyeworks.com. 600 IN SRV 0 100 88 eyeworks-
bdc.laeyeworks.com.' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

++++

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/12/2007
Time: 2:56:42 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
Registration of the DNS record
'_ldap._tcp.Warehouse._sites.laeyeworks.com. 600 IN SRV 0 100 389
eyeworks-bdc.laeyeworks.com.' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/12/2007
Time: 2:56:41 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
Registration of the DNS record '_ldap._tcp.dc._msdcs.laeyeworks.com.
600 IN SRV 0 100 389 eyeworks-bdc.laeyeworks.com.' failed with the
following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/12/2007
Time: 2:21:59 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
Registration of the DNS record '_kerberos._udp.laeyeworks.com. 600 IN
SRV 0 100 88 eyeworks-bdc.laeyeworks.com.' failed with the following
error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/12/2007
Time: 2:11:43 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
Registration of the DNS record
'_kerberos._tcp.Warehouse._sites.laeyeworks.com. 600 IN SRV 0 100 88
eyeworks-bdc.laeyeworks.com.' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/12/2007
Time: 2:11:43 AM
User: N/A
Computer: EYEWORKS-BDC
Description:
Registration of the DNS record '_kerberos._tcp.laeyeworks.com. 600 IN
SRV 0 100 88 eyeworks-bdc.laeyeworks.com.' failed with the following
error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..

Registration of the DNS record
'_ldap._tcp.Warehouse._sites.dc._msdcs.laeyeworks.com. 600 IN SRV 0
100 389 eyeworks-bdc.laeyeworks.com.' failed with the following
error:
DNS operation refused.

.

Relevant Pages

  • Re: NT PDC can no longer administer users it its own domain but can in others.
    ... >> shares etc from the fubar PDC to the new BDC then go from there. ... > Seriously, pull the network cable, reboot and see if it'll let you modify ... They were the addresses of two WINS servers at other locations. ...
    (microsoft.public.windows.server.general)
  • WINS - A Duplicate Name Exists On The Network
    ... We have a PDC and a BDC (that is also an Exchange 5.5 ... name exists on the network". ... is to reboot the BDC first while the PDC is still down. ... Although the servers are running, ...
    (microsoft.public.exchange.connectivity)
  • NT4 to W2K3 Migration
    ... I am about to emabark upon a test run of my migration, I have notes, as I ... I have 1 PDC and 1 BDC, firstly im going to add one more BDC and sync ... I have a Server (off network at present) that I am going to install AD ... *proper* servers that I have earmarked so I can copy AD to the correct ...
    (microsoft.public.windows.server.migration)
  • DNS Problem
    ... I recently been in charge of configuring a network and its ... Now one of the servers has been getting error ... messages such as "Registration of the DNS record '_kpasswd._udp." ... me too, but still no luck. ...
    (microsoft.public.win2000.dns)
  • Re: Dcidag errors
    ... Port blockage between servers ... Other sorts of networking issues (lack of connectivity between the points ... These errors are typically a result of a network connectivity issue of some ... > replicating this nc. ...
    (microsoft.public.windows.server.active_directory)