First, you will want to check the obvious such as making sure the time is the same on both computers, verifying that the computer account on AD exists and is not disabled and that your credentials are valid and not expired among other things. When all of those check out it may mean that kerberos authentication is broken. Also, if you manage the server from another computer you may receive a detailed kerberos authentication error.
Often times, this can be resolved by signing into the server locally and de-joining/re-joining the computer to the domain. However, this requires at least one reboot, and potentially other problems, so you may not want to do that. You may be able to fix the problem with Powershell 3.0 as follows. If you do not have Powershell 3.0 you will need to install it or try alternate method #2.
- Sign In to the Computer locally (not the domain controller) - you may still be able to RDP into the computer using the IP (instead of name) and you must sign in with a local Administrator account
- Open Powershell
- Type $cred = Get-Credential
- Enter a Domain Administrator account when prompted.
- Type Reset-ComputerMachinePassword -Credential $cred -Server [domain name of primary DC ex- dc-hostname.domain]
- Sign In to the Computer locally (not the domain controller) - you may still be able to RDP into the computer using the IP (instead of name) and you must sign in with a local Administrator account
- Open Powershell
- Type Test-ComputerSecureChannel -Repair -Credential (get-credential)
- Download and install the Remote Server Administration Tools from Microsoft onto the Computer - not the domain controller.
- Open an elevated command prompt on the Computer.
- Type netdom.exe resetpwd /s:dc-hostname.domain /ud:domainadminusername /pd/*
- Enter a Domain Administrator account when prompted