Share via

I have change the Server name and after that i am not able to login the server showing trust login issue. i tried to disconnet the network adapter but same error is getting can you please help here

Amol tejankar 5 Reputation points
2026-03-02T05:00:47.0166667+00:00

I have change the Server name and after that i am not able to login the server showing trust login issue. i tried to disconnet the network adapter but same error is getting can you please help here

Windows for business | Windows Server | Directory services | User logon and profiles
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Amol tejankar 5 Reputation points
    2026-03-02T05:34:09.14+00:00

    Local account not able to login

    0 comments No comments

  2. Amol tejankar 5 Reputation points
    2026-03-02T05:19:19.01+00:00

    local admin is not working how can i login

    0 comments No comments

  3. Amol tejankar 5 Reputation points
    2026-03-02T05:18:48.17+00:00

    the local administrator login is not working how can i login

    0 comments No comments

  4. Amol tejankar 5 Reputation points
    2026-03-02T05:06:26.5033333+00:00

    After trying to login the loal account getting error network logon services not started

    0 comments No comments

  5. Q&A Assist
    2026-03-02T05:00:58.38+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Changing the server name on a domain-joined machine can break the secure channel with the domain and cause the error “The trust relationship between this workstation and the primary domain failed.” This must be repaired from a local admin session.

    Follow these steps on the affected server:

    1. Sign in using a local administrator account
      • At the logon screen, use a local account in the form SERVERNAME\LocalAdmin.
    2. Use PowerShell to test and repair the secure channel
      1. Open PowerShell as Administrator.
      2. Test the secure channel:
              Test-ComputerSecureChannel
        
        • If it returns False, continue.
      3. Attempt to repair the secure channel (you will need domain credentials with rights to reset the computer account):
              Test-ComputerSecureChannel -Repair -Credential (Get-Credential)
        
      4. If still not working, reset the computer account password and reboot:
              $credential = Get-Credential
              Reset-ComputerMachinePassword -Credential $credential
              Restart-Computer -Force
        
    3. Alternative using Command Prompt (if PowerShell is not preferred)
      1. Open Command Prompt as Administrator.
      2. Verify the secure channel (replace placeholders):
              netdom verify ComputerName /domain:YourDomainName
        
      3. Reset the machine password (replace placeholders):
              netdom resetpwd /server:DomainControllerName /userd:Domain\Username /passwordd:*
        
      4. Reset the secure channel (replace placeholders):
              netdom reset /domain:YourDomainName /userd:DomainUsername /passwordd:*
        
      5. Restart the server.
    4. If the trust issue persists after repair
      • After reboot, log on again with the local admin account and:
        • Remove the server from the domain (join to a workgroup), reboot.
        • Join it back to the domain with proper domain credentials, reboot again.

    These steps repair the broken trust caused by the name change so domain logons and SCOM agent/management server communication can work again.


    References:


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.