Lost trust relationship between workstation and primary domain controller!!
I have had workstations lose their trust relationship with my DC before, and logging on as local administrator, taking the machine back out of the domain, restarting and putting the machine back into the domain usually fixes the problem. I have a machine
that won't logon to the local admin account with the same error?? Why would the machine still give a DC logon error when trying to logon to the local admin account??
If I unplug the machine from the network and try to get into the local administrator's account, I get " There are currently no logon servers available to service the logon request.."
I really need help in trying to recover this machine without having to completely rebuild the workstation...
June 27th, 2011 5:36pm
what operating system do you have and are you really trying to logon using local administrators credentials ?
Please do let us know the exact error.
Could you please try the same thing with the safe mode .
http://www.virmansec.com/blogs/skhairuddin
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 5:49pm
Hello,
if you have multiple DCs then I suspect that there is something wrong with one of your DCs (possibly a replication problem).
Please use Microsoft Skydrive to upload the output of these commands on all your DCs:
ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server]
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)
Once done, post a link here.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft Certified
Professional
Microsoft Certified
Systems Administrator: Security
Microsoft Certified
Systems Engineer: Security
Microsoft Certified
Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows 7, Configuring
Microsoft Certified
IT Professional: Enterprise Administrator
June 27th, 2011 9:18pm
Thanks for the quick response... Fortunately, I figured out my problem. I had the user's computer name wrong when trying to logon as local administrator. Once I had the correct computer name, I was able to logon as local admin and remove the workstation
from the domain, restart, and re-add to the domain without incident...
Thanks again...
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 9:20pm
Thanks for the quick response... Fortunately, I figured out my problem. I had the user's computer name wrong when trying to logon as local administrator. Once I had the correct computer name, I was able to logon as local admin and remove the workstation
from the domain, restart, and re-add to the domain without incident...
Thanks again...
Good for you but please specify how many DCs you have and post the files I suggested.
I suspect that you have replication problems and if yes this may explain why you lose trust relationships.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft Certified
Professional
Microsoft Certified
Systems Administrator: Security
Microsoft Certified
Systems Engineer: Security
Microsoft Certified
Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows 7, Configuring
Microsoft Certified
IT Professional: Enterprise Administrator
June 27th, 2011 9:35pm
Actually, my problems were caused by two machines (both in HR) having the same computer name... I realized it after having problems with the second one, that it had the same computer name as the first one I had problems with. I changed the computer name
on one of them and totally resolved my issue.
So in conclusion... My problems were human error!
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2011 4:18pm