These problems occur if the following conditions are true:
- You try to connect by using a fully qualified domain name (FQDN) or a NetBIOS name.
- Both computers are in a Windows Server 2003-based domain.
- You have performed an authoritative restoration on the Users container in the Active Directory directory service.
Log
Name: System
Source: LsaSrv
Date:
Date
Event ID: 40961
Task Category: (3)
Level: Warning
User: N/A
Computer:
ComputerName
Description: The Security System
could not establish a secured connection with the server
ServerName. No authentication protocol was
available.
Log Name: System
Source:
Microsoft-Windows-GroupPolicy
Date: Date
Event ID: 1006
Task Category: None
Level: Error
User: SYSTEM
Computer: ComputerName
Description: The
processing of Group Policy failed. Windows could not authenticate to the Active
Directory service on a domain controller. (LDAP Bind function call failed).
Log Name: System
Source:
Microsoft-Windows-GroupPolicy
Date:
Date
Event ID: 1055
Task Category: None
Level: Error
User: SYSTEM
Computer:
ComputerName
Description: The processing of
Group Policy failed. Windows could not resolve the computer name.
Log Name: Directory Service
Source:
Microsoft-Windows-ActiveDirectory_DomainService
Date:
Date
Event ID: 1925
Task Category:
Knowledge Consistency Checker
Level: Warning
User: ANONYMOUS LOGON
Computer: ComputerName
Description:
The attempt to establish a replication link for the following writable
directory partition failed.
Directory partition:
CN=Schema,CN=Configuration,DC=Namespace,DC=Namespace
Source
directory service:
CN=NTDS
Settings,CN=DomainController,CN=Servers,CN=SiteName,CN=Sites,CN=Configuration,DC=Namespace,DC=Namespace
Source directory service address:
Address
This directory service will be
unable to replicate with the source directory service until this problem is
corrected.
Error value:
1396 Logon Failure: The target account name
is incorrect.
Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date:
Date
Event ID: 1645
Task Category: DS RPC
Client
Level: Error
User: ANONYMOUS LOGON
Computer:
ComputerName
Description: Active Directory
Domain Services did not perform an authenticated remote procedure call (RPC) to
another directory server because the desired service principal name (SPN) for
the destination directory server is not registered on the Key Distribution
Center (KDC) domain controller that resolves the SPN.
When you use Hyper-V Remote Management, the Hyper-V management console stops responding when you try to create a fixed-size virtual hard drive (VHD) on a remote Hyper-V server.
Note These problems do not occur if one of the following conditions is true:
- You connect by using the IP address of the remote computer and by using a local user account on the remote computer.
- You connect from a Windows XP-based computer to a Windows Vista-based computer.
- You connect from a Windows Vista-based computer to a Windows XP-based computer.