25 - Windows Server 2012 How to Fix Problem Client Cannot Login to Server (Video in Khmer)

Hello my friend! Today I show you step-by-step how to Fix Problem Client Cannot Login to Server on Windows Server 2012 R2 inside VMware! When client PC cannot log in to domain server, error messages like "There are currently no logon servers available" or "The trust relationship between this workstation and primary domain failed" can happen! Follow troubleshooting steps below with video tutorial in Khmer! Let's get started!

💡 Tip: 90% of domain login problems are caused by incorrect DNS IP address on client PC or time desynchronization between client and Domain Controller server!

Watch Video Tutorial (Khmer)

Watch full step-by-step video tutorial below to see complete process in Khmer:

Step 1: Verify Client DNS Server Settings & Ping Server

1. On client PC, press Win + R > type ncpa.cpl > press Enter.
2. Right-click Ethernet adapter > select Properties > double-click Internet Protocol Version 4 (TCP/IPv4).
3. Verify Preferred DNS server is set to Domain Controller IP address (example: 192.168.1.100).
4. Open Command Prompt (cmd) > type ping mydomain.local to verify server responds.

💡 Tip: If client DNS points to home router IP (like 192.168.1.1 or 8.8.8.8) instead of DC IP address, client PC cannot locate Domain Controller for login!

Step 2: Sync System Time & Date with Domain Controller

1. Check system date and time on client PC vs. Domain Controller server.
2. If time gap is more than 5 minutes, Kerberos domain authentication will fail automatically!
3. On client PC, open Command Prompt (cmd) as Administrator > run: net time \\YourDomainControllerIP /set /y
4. Time synchronizes with server immediately!

💡 Tip: Active Directory domain security requires client and server clock times to be synchronized within a 5-minute threshold!

Step 3: Check Account Status & Unlock Account on Server

1. On Domain Controller, open Active Directory Users and Computers (dsa.msc).
2. Find target user account > double-click to open properties > click Account tab.
3. Make sure box Account is disabled is UNCHECKED.
4. If account is locked out, check box Unlock account > click Apply.
5. Right-click user account > select Reset Password... if user forgot password.

💡 Tip: If user account has "User must change password at next logon" checked, client PC prompts user to create new password at login screen!

Step 4: Fix Broken Domain Trust Relationship (Re-join Domain)

If client shows error "The trust relationship between this workstation and primary domain failed":

1. On client PC, press Win + R > type sysdm.cpl > press Enter.
2. Click Change... button > change domain to WORKGROUP (example: WORKGROUP) > click OK > Restart Now.
3. Log in with local administrator account.
4. Open sysdm.cpl > change back to Domain (example: mydomain.local) > enter Domain Admin credentials > Restart Now.
5. Domain trust relationship is repaired and client can log in successfully!

💡 Tip: Shortcut! Run PowerShell command Test-ComputerSecureChannel -Repair -Credential (Get-Credential) on client PC to repair broken domain trust without restarting twice!

Related Tutorials

• 🎓 Windows Server 2012 Complete Tutorial Series (Video in Khmer)
• 💻 07 - Windows Server 2012 Join Domain Client to Domain Controller (Video in Khmer)
• ⌨️ 09 - Windows Server 2012 Join Domain using Command Line (Video in Khmer)
• 🔑 15 - Windows Server 2012 Allow User to Reset Password (Video in Khmer)
• 🌐 19 - Windows Server 2012 Configure DNS Server (Video in Khmer)

Hope this tutorial help you fix problem client cannot login to server on Windows Server 2012 R2 easily! Practice Active Directory domain troubleshooting today. Happy learning my friends! Sharing is caring!