Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client > Windows Vista IT Pro Forums > Windows Vista Networking > Vista Error "Trust relationship between this workstation & primary domain failed"

Answered Vista Error "Trust relationship between this workstation & primary domain failed"

    •  
      Sunday, July 09, 2006 10:01 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      I'm running a small network at home with 3 clients, all XP SP2, 1 domain controller which is Server 2K3. Everything works perfectly.

      Just installed Vista on a partition of 1 client, still have XP installed on C: and both worked fine.

      I added the Vista OS to same the Domain and authenticated, could browse other PC,s, internet, etc..

      Then when I went back to XP and tried logging in, I had an error msg about the domain controller. So I logged on locally and removed & re-added it to the domain with the necessary reboots in between. I could then log back on to the domain.

      Now the problem is that I cannot log in to Vista and receive the above error msg in the Subject Field.

      I foolishly didn't create a local administrator account to log on locally to Vista and it cannot load the Domain admin account.

      Firstly what has caused this and is there anyway to log on to Vista? If there isn't it doesn't matter, I can reinstalled Vista on the same partition but dont want to have to be removing and re-adding from the domain each time I swap OS.

      Cannot find any help when dual-booting involves a domain. Thanks

       

       

    Answers

    • Wednesday, September 13, 2006 2:46 PM
       
       Answered
      Sign In to Vote
      2
      Sign In to Vote

       

      The Vista installation is trying to connect into the domain with old computer account credentials. The local 'true' Administrator account is disabled by default - but you can logon locally with a user name that you created at the end of setup and rejoin the computer into domain. If you have deleted this account like me, there's last hope - reboot into Safe mode and logon with DOMAIN\Administrator account and correct password. This time it doesn't use cached domain computer account and you can rejoin domain.

      Hope it helps!

      Olda

       

       

    All Replies

    • Wednesday, September 13, 2006 2:46 PM
       
       Answered
      Sign In to Vote
      2
      Sign In to Vote

       

      The Vista installation is trying to connect into the domain with old computer account credentials. The local 'true' Administrator account is disabled by default - but you can logon locally with a user name that you created at the end of setup and rejoin the computer into domain. If you have deleted this account like me, there's last hope - reboot into Safe mode and logon with DOMAIN\Administrator account and correct password. This time it doesn't use cached domain computer account and you can rejoin domain.

      Hope it helps!

      Olda

       

       
    • Tuesday, June 19, 2007 8:34 PM
       
       
      Sign In to Vote
      5
      Sign In to Vote
      Another thing to try is to simply disconnect the computer from the network and login.
       
    • Wednesday, June 27, 2007 9:10 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       DiscWog wrote:
      Another thing to try is to simply disconnect the computer from the network and login.

       

      your solution worked for us.

       

      cheers!

       
    • Wednesday, June 27, 2007 2:45 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      If you want to connect a dual-boot machine to a domain then you need to give each OS a different machine name (and hence machine account in AD) to avoid this problem recurring.
       
    • Monday, July 02, 2007 2:29 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

       

      ...no point in having the other boot use a different computer name.. when you then try to log back in to the XP boot (after Vista) you still have to leave and rejoin the domain. Is it possible the the MAC address is bound as part of the trust relationship?

       
    • Tuesday, July 03, 2007 10:57 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      No, the MAC address is not used for any part of domain authentication. It's important that both installs are given different NetBIOS names before ever attempting to join either one to AD though or you may already have corrupted the computer account object.
       
    • Friday, July 06, 2007 9:20 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      ahh, that explains that - I'd built the XP side, that was already on the domain when I started the Vista build, used the same name, got this issue, then renamed the vista build and had the same issue. Now I understand why.

       

      nice one!

       
    • Tuesday, January 01, 2008 12:55 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I know this was awhile back, but I'm getting the same error. I am unable to log-on to the network at all due to the trust failing.  I've gone back to the XP boot and renamed it, but when I try the Vista boot - it still fails ... I've tried safemode and all.  Is there away to easily clean this up, so that both boot modes work without fail?
       
    • Tuesday, February 05, 2008 4:01 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      TomB, try to change the Vista computer name and restart. It worked for me.

       
    • Friday, February 22, 2008 5:13 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      hey guys,

       

      is there any way to fix this error without rejoining the domain as i dont want to lose my profile.

       

      thanks

       
    • Friday, February 22, 2008 5:15 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Disconnecting and then re-joining a domain shouldn't cause you to lose your profile.

       

       
    • Monday, February 25, 2008 12:35 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      im sure it does, i dont want to take the risk and do this. i heard it may be due to sp updates?

       

       
    • Wednesday, February 27, 2008 8:15 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I've done this on a few occasions, and it didn't mess up the profiles.  I can think of some unusual cases where you have some roaming profile/caching settings on your DC where you might see something strange--but a standard config should rejoin and reuse existing profiles that you'd used for domain accounts previously on that computer.

       

       
    • Friday, April 11, 2008 8:15 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       DiscWog wrote:
      Another thing to try is to simply disconnect the computer from the network and login.

       

      This issue was fixed by the above however I do not have another copy of Windows on my PC. What has happend is that my machine was logged intot he server overnight when I scheduled a restart for an AV update.

       

      However simply disconnecting the LAN cable fixed the issue and I'm not up and working with no rejoining domains or safemode boots.

       

       

       
    • Saturday, May 17, 2008 10:28 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      This worked for me.  Thanks for the help.

       

       
    • Wednesday, July 09, 2008 3:07 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       DiscWog wrote:
      Another thing to try is to simply disconnect the computer from the network and login.

       

       

      This worked for me too. Thank you.

       
    • Wednesday, December 16, 2009 4:34 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      The solution worked for me as well. Thanks guys..:)
       
    • Tuesday, January 26, 2010 5:44 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I have a similar problem. If I disconnect the computer from the network and login, do I then rejoin to the domain? Eventually I need to connect this computer to the network, but right now my problem is just logging in at all.

       
    • Tuesday, January 26, 2010 5:47 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I have a similar problem. I don't have the local setup pw. However, when I boot in Safe Mode with my Domain Admin pw, I receive the error message that the pw is incorrect, which it isn't. Should I boot is Safe Mode or Safe Mode w/Networking? Should I boot in Safe Mode but still have the workstation connected to the network?

       
    • Thursday, July 08, 2010 3:12 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      DOWNLOAD "HIREN BOOT 10.4" BURN THE ISO ON CD... BOOT YOUR PC WITH THAT... GO IN THE OPTIONS KON BOOT... AND NOW YOUR PC WILL AGAIN BOOT IN THE OPERATING SYSTEM (IN YOUR CASE VISTA) and YUPPI........... YOU DON'T NEED ANY PASSWORD TO LOG IN TO ANY ACCOUNT... THERE ARE OTHER TOOLS TOO IN THIS CD TO CREATE AN ADMIN ACCOUNT WITHOUT LOGGIN IN... THIS IS THE ULTIMATE AND THE DEFINITE SOLUTION... -SAMARJIT ROY CHOUDHURY
       
    • Friday, June 10, 2011 2:45 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hey Guys..

       

                The problem is NOT fixing this issue..  The problem is preventing this issue from comming back again and again..  I have over 100 computer in just under half of them are in remote locations..  When the trust relationship issue happens, this is a huge inconvenience..

      The MS answer is not encouraging.. http://support.microsoft.com/kb/162797

                If anyone has found the root of this issue...  what makes this happen to some networks, but not others..  I would love to know..

      Note: this happens to Notebooks & Workstations..   it happens to those that travel lots with their PC as well as those that remain in the office all the time.