techie08 Posted September 5, 2011 Posted September 5, 2011 Help!!!!!!!!!!! Im getting a lot of error on my windows 7 desktops with the following error: "The trust relationship between the workstation and the primary domain failed" Does anyone know why this is happening? its not on all stations but about 12 or so this morning alone! I can enable to administrator account and re add it but i dont know why its happening in the first place! Thanks everyone.
Mcshammer_dj Posted September 5, 2011 Posted September 5, 2011 trust relationship bet. this workstation & the primary domain failed - Windows 7 Forums
Gatt Posted September 5, 2011 Posted September 5, 2011 I had this spradically in 2 IT Suites in the school and never did figure out what the problem was Times weren't out of sync and all updates had been applied The build was no different to the PCs elsewhere that were stable It would successfully rejoin to the domain and function quite happily...
Guest TheLibrarian Posted September 5, 2011 Posted September 5, 2011 We experienced this with ~5 of 30 PC's. Never quite got to the bottom of it but it does appear to be fixed. For reasons best known to themselves the PC's time was out; even though at the time they were joined to the domain the time was correct. The steps we took that solved the issue (he says while touching wood): 1/ Remove the machine accounts from AD. 2/ Add the machines to a workgroup. 3/ Wait 30 minutes for replication (I know it's only 15 but we waited 30 anyway). 4/ Re add the machines using the FQDN instead of the NetBIOS domain name. Seems to have fixed those PC's. We didn't manage to trace where / why they were getting the incorrect time from.
techie08 Posted September 5, 2011 Author Posted September 5, 2011 You didnt accidently delete the OU? No i didnt. The machines has been reimaged from from XP to Windows 7 though and i didn't delete the existing machine in AD.
rbance Posted September 5, 2011 Posted September 5, 2011 No i didnt. The machines has been reimaged from from XP to Windows 7 though and i didn't delete the existing machine in AD. I think you answered the question above. You may need to reset the accounts. Check the NETLOGON service to just of curiosity. Out of interest what OS is the DC? The net time thing is definitely worth looking at.
techie08 Posted September 5, 2011 Author Posted September 5, 2011 I think you answered the question above. You may need to reset the accounts. Check the NETLOGON service to just of curiosity. Out of interest what OS is the DC? The net time thing is definitely worth looking at. The time is exactly the same on all 3 DCs (2008R2) Also the netlogon service is started on all 3. I think my next course of action is to restart all 3 DCs as per link in earlier post. Is it also good practice to delete the Machine in AD if you are re-imaging?
rbance Posted September 5, 2011 Posted September 5, 2011 I meant on the clients.....check them... I would start again...ie delete...I am actually building a new domain at the moment in preparation for moving to Windows 7......but that was more to do with issues with the current 2003 domain i have inherited...
DaveyPitch Posted September 5, 2011 Posted September 5, 2011 I saw this problem on some of my machines here, and found out the culprit was the way the machines were renamed and then joined to the domain as part of the Windows System Image Manager. I ended up solving it by re-ordering the way things were done, and using a small batch file to join the PC to the domain as part of an automatic first logon. It now works flawlessly and all I have to do after re-imaging a machine is rename it, and the script takes care of the rest.
Mcshammer_dj Posted September 5, 2011 Posted September 5, 2011 I saw this problem on some of my machines here, and found out the culprit was the way the machines were renamed and then joined to the domain as part of the Windows System Image Manager. I ended up solving it by re-ordering the way things were done, and using a small batch file to join the PC to the domain as part of an automatic first logon. It now works flawlessly and all I have to do after re-imaging a machine is rename it, and the script takes care of the rest. Can i get a look at that script as I know a school that have been having that problem.
DaveyPitch Posted September 5, 2011 Posted September 5, 2011 Can i get a look at that script as I know a school that have been having that problem. Sure, no probs. Are you familiar with the Windows SIM at all? I used that to set the machines to do an automatic login with local admin credentials on first boot. Then I just set it up to run the following command line..... c:\windows\system32\netdom.exe join %computername% /Domain:domainname /UserD:AdminUser /PasswordD:AdminPassword The bits in bold are the bits you'll need to change for your own domain. Also, the netdom command isn't part of Windows 7 as standard. You'll need to download the RSAT tools from MS website (if you haven't already), and when it's installed, enable the Active Directory parts of it (which puts netdom on the computer). That's probably as clear as mud. If it doesn't make sense let me know, and if needed I can show you my unattend.xml file I use for sysprep, which contains everything I did. Cheers, Dave
techie08 Posted September 5, 2011 Author Posted September 5, 2011 I saw this problem on some of my machines here, and found out the culprit was the way the machines were renamed and then joined to the domain as part of the Windows System Image Manager. I ended up solving it by re-ordering the way things were done, and using a small batch file to join the PC to the domain as part of an automatic first logon. It now works flawlessly and all I have to do after re-imaging a machine is rename it, and the script takes care of the rest. I deploy my images using using DELL KACE's deployment appliance. The images have been sysprep'd using mysysprep and sysprep also joins them to the domain. Im going to try a few things first such as checking the time on the machine and deleting the machine name in AD before rejoining to the domain. Im also at some point going to restart my DCs.
DaveyPitch Posted September 5, 2011 Posted September 5, 2011 I deploy my images using using DELL KACE's deployment appliance. The images have been sysprep'd using mysysprep and sysprep also joins them to the domain. I've not used that appliance, but the problem I had was with Sysprep joining the machines to the domain. Check in AD and see if the machines are in there with the correct name. In my case, when using sysprep normally, the order was wrong, and it would join the machine to the domain with a random name, then rename the PC, but it wouldn't rename the PC in AD as well, so even though the PC would say it was part of a domain, Active Directory would have no record of the new name. Check it out and see if you're getting the same issuse.
rich_tech Posted September 5, 2011 Posted September 5, 2011 duplicate machine names caused this problem for me on my work network, once that was sorted, taking them off and readding them to the domain sorted it.
Guest TheLibrarian Posted September 6, 2011 Posted September 6, 2011 I spoke too soon, lost two machines this morning and another 8 about 20 minutes ago.
Guest TheLibrarian Posted September 7, 2011 Posted September 7, 2011 OK guys I need some information from you please. What network card is being used to connect to the domain on the PC's that are losing trust? Our are all Realtek PCIe GBE Family Controller / PCI\VEN_10EC&DEV_8168&SUBSYS_80001025&REV_06. For what it's worth the PC's that are failing are all Acer Veritons and one Acer Revo: I do not blame Acer for this but I am beginning to suspect the nic driver. Obviously I am hoping the failing PC's you have are the same card - a long shot but who knows... P.S. By 4p.m. yesterday we'd lost 20 out of 30 PC's.
techie08 Posted September 7, 2011 Author Posted September 7, 2011 OK guys I need some information from you please. What network card is being used to connect to the domain on the PC's that are losing trust? Our are all Realtek PCIe GBE Family Controller / PCI\VEN_10EC&DEV_8168&SUBSYS_80001025&REV_06. For what it's worth the PC's that are failing are all Acer Veritons and one Acer Revo: I do not blame Acer for this but I am beginning to suspect the nic driver. Obviously I am hoping the failing PC's you have are the same card - a long shot but who knows... P.S. By 4p.m. yesterday we'd lost 20 out of 30 PC's. Mines a mixture of NEC Powermate ML450 (Realtek) and HP DC7800 and DC8000 (broadcom i think). We have also had it on the dual boot macs!!!!
Guest TheLibrarian Posted September 8, 2011 Posted September 8, 2011 Mines a mixture of NEC Powermate ML450 (Realtek) and HP DC7800 and DC8000 (broadcom i think). We have also had it on the dual boot macs!!!! I was really hoping it was going to be a driver issue.
tommej Posted September 8, 2011 Posted September 8, 2011 We had this issue and found it to be related to naming the machines when joining the domain for the first time. Taking all the machines out of the domain and renaming then rejoining seemed to fix it for good.
Guest TheLibrarian Posted September 8, 2011 Posted September 8, 2011 That's been done on a number of occasions; even created entirely new accounts for the machines by renaming the machines while they were off the domain.
Guest TheLibrarian Posted September 8, 2011 Posted September 8, 2011 What DC's are being used? 2003? 2008? 2008R2? Domain functional level? Our are 2003r2 at not sure what level but I will try to find out.
sister_annex Posted September 12, 2011 Posted September 12, 2011 @TheLibrarian We are running at 2003 functional level
techie08 Posted September 12, 2011 Author Posted September 12, 2011 2003r2 Domain Level Here also! All DCs on 2008r2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now