Originally posted by: dphantom
What ype of Windows domain? 2000, 2003 or NT. What are the associated event viewer IDs as well?
It's a Windows 2003 Server domain. The events before disjoining the domain were RPC related error messages also. I do have ISA Server 2004 installed on it, and it is my web server. I have two NIC's installed in it, one for external and one for internal connections.
I've always seen these error messages so I thought leaving the domain, reseting the computer account in AD, and then rejoining the domain would fix it. When I try to rejoin the domain it will ask for username, and password to join the domain.
I then type in the administrator user account, and passoword then recieve that error message while it's trying to join the domain.
Here are the error messages I was getting when it was a member server in the domain. I would usually get these when logging on the server. No other servers have any errors atm, the two AD domain controllers are both clean in the event viewer logs.
Source: Netlogon
Event ID 5719
This computer was not able to set up a secure session with a domain controller in domain DOMAINNAME due to the following:
The remote procedure call failed and did not execute.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
Source Userrenv
Event ID 1053
Windows cannot determine the user or computer name. (The remote procedure call failed and did not execute. ). Group Policy processing aborted.
I have tried fixing the problems above by reading Microsoft hotfixes, windows updates, and even things people said fixed it on
www.eventid.net and nothing worked. I've tried registry fixes, and etc.
Funny thing is that the services for RPC are started, and all dependencies are started. I did a registry fix that made DNS start before RPC would start so it wouldn't have that problem. That did not fix it. I was getting the same problems listed above at one time on one of my Terminal Services servers. Leaving the domain, and rejoining fixed those problems above.
This server though, won't even let me rejoin the domain.
here is a link from the KB Article which may be more specific to your issue since you run ISA 2004...
Facebook
Twitter