Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
the trust relationship between this workstation and the primary domain failed

Answered the trust relationship between this workstation and the primary domain failed

  • Saturday, February 02, 2013 1:36 AM
     
     
    Sign In to Vote
    0

    hi, i am experiencing also this problem"the trust relationship between this workstation and the primary domain failed" with our company network, i tried to disjoin, delete the computer name in the domain and join again. but still the problem exists.

    please help

     

All Replies

  • Saturday, February 02, 2013 1:49 AM
     
     Proposed Answer Has Code
    Sign In to Vote
    0

    Generally I use netdom to reset the channel between the client and the domain.

    netdom reset machinename /domain:domainname

    Also, see this Wiki on the subject:

    http://social.technet.microsoft.com/wiki/contents/articles/9157.trust-relationship-between-workstation-and-primary-domain-failed.aspx

    Richard Mueller - MVP Directory Services

     
  • Saturday, February 02, 2013 2:18 AM
     
     
    Sign In to Vote
    0

    Hi Richard,

    I will try your suggestion. Btw, my workstation in Win7Pro and Win2008R2 is my Server

    Thanks

     
  • Saturday, February 02, 2013 6:32 AM
     
     
    Sign In to Vote
    0
    Could any one change the tread to question from disscusion.

    Best regards Biswajit Biswas Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin

     
  • Saturday, February 02, 2013 6:11 PM
     
     Answered
    Sign In to Vote
    0

    It seems to be dns name resolution issue.The error message "'The trust relationship between this workstation and the primary domain failed'
    indicates that secure channel between the client server and DC is broken.

    (1) Check the DNS & WINS entries?
     IP configuration on clients and member servers:
    -----------------------------------
    1. Each workstation/member server should point to local DNS server as primary DNS and other remote DNS servers as secondary.
    2. Do not set public DNS server in TCP/IP setting of WS.

    (2) Check whether the Firewall service is ON of OFF?
    Refer link this to diable the firewall:http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx

    (3) Check the status of the Browser service?
    It should be started.

    (4) Check the status of the machines account in the AD?(It may be disabled)
    If the Machine account is disable enable the same.

    (5) Remove the machine from the domain & readd it to the domain else try using netdom utility to reset the secure channel between the server & the domain controller?http://support.microsoft.com/kb/260575

    (6)Also check the DNS console for duplicate record for the host machine and remove the same.

    (7)Take a look at below hotfix too.A secure channel is broken after you change the computer password on a Windows 7 or Windows Server 2008 R2-based client computer:http://support.microsoft.com/kb/979495

    (8)It could be due to AV or 3rd party security application which act as firewall and block AD communuctaion.AV like Symantec,trend,etc have new features to "protect network traffic".Please check AV setting and disable the same if defined.

    (9)Did you create the system using any clone/images/ghost software, if yes then did you sysprep the system for assigning unique SID.

    Hope this helps

    Best Regards,

    Sandesh Dubey.

    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • Saturday, February 02, 2013 8:11 PM
     
     Answered
    Sign In to Vote
    0

    Hi,

    well this problem may occurred if the secure channel between the computer account and domain controller is broken. Most of the time the problem is solved by simply right clicking the computer account in Active Directory and reseting the account, but I have seen scenarios where reseting was not a successful solution. however "Rejoining" the computer to the domain sill can fix the problem as a last resort. 

    Mahdi Tehrani | Loves Powershell Spreadis Twitter LinkedIn Youtube

     
  • Sunday, February 03, 2013 5:33 AM
     
     
    Sign In to Vote
    0

    hi,

    Probably there are PCs with the same name in your network.