I'm trying to join a Windows Server 2003 SP2 box to our domain and when attempting to do so on the client server I am getting an error window with the title of "Computer Name Changes" with the text in the body of the window "The following error occurred attempting to join the domain "domain.local":" There are no more endpoints available from the endpoint mapper" Where domain.local is represents our domain name. This message appears about 20-30 seconds after I try to join the domain. This is the only box where the problem is occurring.
Nothing is logged into the event viewer on the client machine during this process. However on the domain controller I can see my account accessing Active Directory several times in the security log. This has not helped me. The computer account gets locked out during this process. Here's one security entry (note I've changed the domain name, my account and server names to generic placeholders)
Event Type: Success Audit
Event Source: Security
Event Category: Account Management
Event ID: 646
Date: 3/18/2008
Time: 10:55:50 AM
User: DOMAIN\myaccount
Computer: DOMAINCONTROLLERNAME
Description:
Computer Account Changed:
-
Target Account Name: SERVERNAME
Target Domain: DOMAIN
Target Account ID: DOMAIN\SERVERNAME
Caller User Name: myaccount
Caller Domain: DOMAIN
Caller Logon ID: (0x0,0x92E7A10)
Privileges: -
Changed Attributes:
Sam Account Name: -
Display Name: -
User Principal Name: -
Home Directory: -
Home Drive: -
Script Path: -
Profile Path: -
User Workstations: -
Password Last Set: -
Account Expires: -
Primary Group ID: -
AllowedToDelegateTo: -
Old UAC Value: 0x80
New UAC Value: 0x81
User Account Control:
Account Disabled
User Parameters: -
Sid History: -
Logon Hours: -
DNS Host Name: -
Service Principal Names: -
I've played with the permissions on the client server's RPC services to no success. I've checked and rechecked DNS. I can authenticate to the domain as I can access shares on it. I can see the domain. The domain controller registers this client servers name in the security event log and the IP address.
I'm hitting a wall here. I've been hitting MS, EE and google for a few days and not finding anyone with the same exact problem just similar issues. No firewall on this box btw.
Start Free Trial
