Local account not able to login
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
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
7 answers
Sort by: Most helpful
-
-
Amol tejankar 5 Reputation points
2026-03-02T05:19:19.01+00:00 local admin is not working how can i login
-
Amol tejankar 5 Reputation points
2026-03-02T05:18:48.17+00:00 the local administrator login is not working how can i login
-
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
-
Q&A Assist2026-03-02T05:00:58.38+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreChanging 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:
- Sign in using a local administrator account
- At the logon screen, use a local account in the form
SERVERNAME\LocalAdmin.
- At the logon screen, use a local account in the form
- Use PowerShell to test and repair the secure channel
- Open PowerShell as Administrator.
- Test the secure channel:
Test-ComputerSecureChannel- If it returns
False, continue.
- If it returns
- Attempt to repair the secure channel (you will need domain credentials with rights to reset the computer account):
Test-ComputerSecureChannel -Repair -Credential (Get-Credential) - If still not working, reset the computer account password and reboot:
$credential = Get-Credential Reset-ComputerMachinePassword -Credential $credential Restart-Computer -Force
- Alternative using Command Prompt (if PowerShell is not preferred)
- Open Command Prompt as Administrator.
- Verify the secure channel (replace placeholders):
netdom verify ComputerName /domain:YourDomainName - Reset the machine password (replace placeholders):
netdom resetpwd /server:DomainControllerName /userd:Domain\Username /passwordd:* - Reset the secure channel (replace placeholders):
netdom reset /domain:YourDomainName /userd:DomainUsername /passwordd:* - Restart the server.
- 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.
- After reboot, log on again with the local admin account and:
These steps repair the broken trust caused by the name change so domain logons and SCOM agent/management server communication can work again.
References:
- Join a computer to a domain (windows-server-2016)
- Join a computer to a domain (windows-server-2019)
- Join a computer to a domain (windows-server-2022)
- Join a computer to a domain (windows-server-2025)
- Join a computer to a domain (windows-client-10)
- Join a computer to a domain (windows-client-11)
- Client, service, and program issues can occur if you change security settings and user rights assignments
- Sign in using a local administrator account