A
Andreas Stephanou
We have a Win2K forest with only one Domain and only 2
Win2K DC's. About 140 Clients are either Win2K or Win XP
Pro.
We are using a BIND 9.2 UNIX based DDNS which accepts
dynamic update requests from all DC's.
This installation functions properly over the last 2-3
years.
I am repeatedly trying to add a Win2K3 DC to our
enviroment without full success. After successfull ADPREP
and AD replication, the SYSVOL and NETLOGON shares never
appear on the new Win2K3 DC, obviously because of LDAP
unavailability.
All DNS-records in c:\windows\system32\config\netlogon.dns
of the Win2K3 DC (14 records) are dynamically registered
in the BIND 9.2 DDNS.
When I install Win2K on the same machine, I have no
problems when adding it as a DC to our enviroment.
The following errors and warnings are observed on the
Win2K3 DC:
Can anyone help me out of this situation, or shall I
forget all about Win2K3 and continue with the good old
Win2K?
ERRORS AND WARNINGS OBSERVED ON THE WIN2K3 DC:
DCDIAG.EXE returns:
Domain Controller Diagnosis
Performing initial setup:
[ringsted] LDAP search failed with error 55,
The specified network resource or device is no longer
available..
LDP.EXE -> CONNECT returns:
ld = ldap_open("ringsted", 389);
Established connection to ringsted.
Retrieving base DSA information...
Server error: <empty>
Error<94>: ldap_parse_result failed: No result present in
message
Getting 0 entries:
-----------
EVENT VIEWER in chronological order:
DIRECTORY SERVICE 20:34:00
Event Type: Error
Event Source: NTDS Inter-site Messaging
Event Category: Intersite Messaging
Event ID: 1824
Date: 01-11-2003
Time: 20:34:00
User: N/A
Computer: RINGSTED
Description:
The Intersite Messaging Service requested to perform an
LDAP bind operation. The operation was unsuccessful.
The error message is as follows:
The specified server cannot perform the requested
operation.
Additional data
Error value:
58
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
DIRECTORY SERVICE 20:34:00
Event Type: Warning
Event Source: NTDS Inter-site Messaging
Event Category: Intersite Messaging
Event ID: 1473
Date: 01-11-2003
Time: 20:34:00
User: N/A
Computer: RINGSTED
Description:
The Intersite Messaging service could not read the
intersite transport objects from Active Directory.
As a result, the Intersite Messaging service has stopped.
The Knowledge Consistency Checker (KCC) will be unable to
calculate intersite topology without this service.
User Action
Verify that LDAP queries function properly on this
machine.
Restart the Intersite Messaging service to continue
intersite communication.
Additional Data
Error value:
58 The specified server cannot perform the requested
operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
FILE REPLICATION SERVICE 20:34:00
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 01-11-2003
Time: 20:34:00
User: N/A
Computer: RINGSTED
Description:
File Replication Service is initializing the system volume
with data from another domain controller. Computer
RINGSTED cannot become a domain controller until this
process is complete. The system volume will then be shared
as SYSVOL.
To check for the SYSVOL share, at the command prompt,
type:
net share
When File Replication Service completes the initialization
process, the SYSVOL share will appear.
The initialization of the system volume can take some
time. The time is dependent on the amount of data in the
system volume, the availability of other domain
controllers, and the replication interval between domain
controllers.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SECURITY 20:34:04
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 01-11-2003
Time: 20:34:04
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Logon Failure:
Reason: An error occurred during logon
User Name:
Domain:
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC00002F5
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
APPLICATION 20:34:04
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1097
Date: 01-11-2003
Time: 20:34:04
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Windows cannot find the machine account, The Local
Security Authority cannot be contacted .
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
APPLICATION 20:34:04
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 01-11-2003
Time: 20:34:04
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Windows cannot query for the list of Group Policy objects.
Check the event log for possible messages previously
logged by the policy engine that describes the reason for
this.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SYSTEM 20:35:15:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 01-11-2003
Time: 20:35:15
User: N/A
Computer: RINGSTED
Description:
The Intersite Messaging service terminated with the
following error:
The specified server cannot perform the requested
operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SECURITY 20:35:29
Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 673
Date: 01-11-2003
Time: 20:35:29
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Service Ticket Request:
User Name:
User Domain: MIP.SDU.DK
Service Name: host/ringsted.mip.sdu.dk
Service ID: -
Ticket Options: 0x40830000
Ticket Encryption Type: -
Client Address: 127.0.0.1
Failure Code: 0xD
Logon GUID: -
Transited Services: -
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
FILE REPLICATION SERVICE 20:37:30
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: 01-11-2003
Time: 20:37:30
User: N/A
Computer: RINGSTED
Description:
Following is the summary of warnings and errors
encountered by File Replication Service while polling the
Domain Controller ringsted.mip.sdu.dk for FRS replica set
configuration information.
Could not bind to a Domain Controller. Will try again at
next polling cycle.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
DIRECTORY SERVICE 20:38:54
Event Type: Warning
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 2046
Date: 01-11-2003
Time: 20:38:54
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: RINGSTED
Description:
All of Active Directory's LDAP send queues are full. This
can be caused by clients that continue to send requests
faster than they are processing the results. In order to
prevent the server from becoming unresponsive as a result
of this condition Active Directory has closed 8
connections that are not bound as Administrators. Active
Directory will continue to close connections until enough
send queue space has been recovered to operate normally.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
END OF QUESTION - END OF QUESTION - END OF QUESTION - END
OF QUESTION
Win2K DC's. About 140 Clients are either Win2K or Win XP
Pro.
We are using a BIND 9.2 UNIX based DDNS which accepts
dynamic update requests from all DC's.
This installation functions properly over the last 2-3
years.
I am repeatedly trying to add a Win2K3 DC to our
enviroment without full success. After successfull ADPREP
and AD replication, the SYSVOL and NETLOGON shares never
appear on the new Win2K3 DC, obviously because of LDAP
unavailability.
All DNS-records in c:\windows\system32\config\netlogon.dns
of the Win2K3 DC (14 records) are dynamically registered
in the BIND 9.2 DDNS.
When I install Win2K on the same machine, I have no
problems when adding it as a DC to our enviroment.
The following errors and warnings are observed on the
Win2K3 DC:
Can anyone help me out of this situation, or shall I
forget all about Win2K3 and continue with the good old
Win2K?
ERRORS AND WARNINGS OBSERVED ON THE WIN2K3 DC:
DCDIAG.EXE returns:
Domain Controller Diagnosis
Performing initial setup:
[ringsted] LDAP search failed with error 55,
The specified network resource or device is no longer
available..
LDP.EXE -> CONNECT returns:
ld = ldap_open("ringsted", 389);
Established connection to ringsted.
Retrieving base DSA information...
Server error: <empty>
Error<94>: ldap_parse_result failed: No result present in
message
Getting 0 entries:
-----------
EVENT VIEWER in chronological order:
DIRECTORY SERVICE 20:34:00
Event Type: Error
Event Source: NTDS Inter-site Messaging
Event Category: Intersite Messaging
Event ID: 1824
Date: 01-11-2003
Time: 20:34:00
User: N/A
Computer: RINGSTED
Description:
The Intersite Messaging Service requested to perform an
LDAP bind operation. The operation was unsuccessful.
The error message is as follows:
The specified server cannot perform the requested
operation.
Additional data
Error value:
58
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
DIRECTORY SERVICE 20:34:00
Event Type: Warning
Event Source: NTDS Inter-site Messaging
Event Category: Intersite Messaging
Event ID: 1473
Date: 01-11-2003
Time: 20:34:00
User: N/A
Computer: RINGSTED
Description:
The Intersite Messaging service could not read the
intersite transport objects from Active Directory.
As a result, the Intersite Messaging service has stopped.
The Knowledge Consistency Checker (KCC) will be unable to
calculate intersite topology without this service.
User Action
Verify that LDAP queries function properly on this
machine.
Restart the Intersite Messaging service to continue
intersite communication.
Additional Data
Error value:
58 The specified server cannot perform the requested
operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
FILE REPLICATION SERVICE 20:34:00
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 01-11-2003
Time: 20:34:00
User: N/A
Computer: RINGSTED
Description:
File Replication Service is initializing the system volume
with data from another domain controller. Computer
RINGSTED cannot become a domain controller until this
process is complete. The system volume will then be shared
as SYSVOL.
To check for the SYSVOL share, at the command prompt,
type:
net share
When File Replication Service completes the initialization
process, the SYSVOL share will appear.
The initialization of the system volume can take some
time. The time is dependent on the amount of data in the
system volume, the availability of other domain
controllers, and the replication interval between domain
controllers.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SECURITY 20:34:04
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 01-11-2003
Time: 20:34:04
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Logon Failure:
Reason: An error occurred during logon
User Name:
Domain:
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC00002F5
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
APPLICATION 20:34:04
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1097
Date: 01-11-2003
Time: 20:34:04
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Windows cannot find the machine account, The Local
Security Authority cannot be contacted .
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
APPLICATION 20:34:04
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 01-11-2003
Time: 20:34:04
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Windows cannot query for the list of Group Policy objects.
Check the event log for possible messages previously
logged by the policy engine that describes the reason for
this.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SYSTEM 20:35:15:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 01-11-2003
Time: 20:35:15
User: N/A
Computer: RINGSTED
Description:
The Intersite Messaging service terminated with the
following error:
The specified server cannot perform the requested
operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SECURITY 20:35:29
Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 673
Date: 01-11-2003
Time: 20:35:29
User: NT AUTHORITY\SYSTEM
Computer: RINGSTED
Description:
Service Ticket Request:
User Name:
User Domain: MIP.SDU.DK
Service Name: host/ringsted.mip.sdu.dk
Service ID: -
Ticket Options: 0x40830000
Ticket Encryption Type: -
Client Address: 127.0.0.1
Failure Code: 0xD
Logon GUID: -
Transited Services: -
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
FILE REPLICATION SERVICE 20:37:30
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: 01-11-2003
Time: 20:37:30
User: N/A
Computer: RINGSTED
Description:
Following is the summary of warnings and errors
encountered by File Replication Service while polling the
Domain Controller ringsted.mip.sdu.dk for FRS replica set
configuration information.
Could not bind to a Domain Controller. Will try again at
next polling cycle.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
DIRECTORY SERVICE 20:38:54
Event Type: Warning
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 2046
Date: 01-11-2003
Time: 20:38:54
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: RINGSTED
Description:
All of Active Directory's LDAP send queues are full. This
can be caused by clients that continue to send requests
faster than they are processing the results. In order to
prevent the server from becoming unresponsive as a result
of this condition Active Directory has closed 8
connections that are not bound as Administrators. Active
Directory will continue to close connections until enough
send queue space has been recovered to operate normally.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
END OF QUESTION - END OF QUESTION - END OF QUESTION - END
OF QUESTION