π L2 Server Management – Advanced Troubleshooting Guide (Part 2) π
Here’s Part 2 of the ultimate L2 server troubleshooting guide! If you missed Part 1, go back and check it for critical troubleshooting steps on disk space issues, RDP failures, and Active Directory problems.
Now, let’s dive into more advanced issues and real-world solutions every L2 Engineer must know!
πΉ Advanced L2 Server Issues & Fixes
1️⃣ DNS Resolution Failing – Websites & Internal Apps Not Loading π
✅ Clear local DNS cache:
ipconfig /flushdns
✅ Check DNS forwarding settings:
Get-DnsServerForwarder
✅ If Active Directory DNS is failing, check:
repadmin /syncall
2️⃣ Hyper-V / VMware VM Boot Failures π½
✅ If a VM fails to start, check event logs for VMMS (Hyper-V Virtual Machine Management Service) errors.
✅ Fix corrupt VM configurations:
Get-VM | Where-Object {$_.State -eq "Off"} | Start-VM
✅ In VMware, check if the VM is locked due to file corruption or snapshot issues.
3️⃣ Windows Defender ATP Blocking Services π₯
✅ Check Defender logs:
Get-MpThreatDetection
✅ Exclude necessary services from ATP blocking:
Set-MpPreference -ExclusionPath "C:\Program Files\MyApp"
4️⃣ Kerberos Authentication Failures – Users Cannot Log In π
✅ Check Kerberos tickets:
klist
✅ If tickets are expired, refresh:
klist purge
✅ Verify time synchronization between servers using:
w32tm /query /status
Windows Basic Troubleshooting with CMD Commands
As IT professionals, we often rely on Command Prompt (CMD) for quick and effective troubleshooting in Windows. Here are some essential CMD commands that can help diagnose and fix common issues:
1️⃣ Check Network Issues
πΉ ping google.com – Check internet connectivity
πΉ ipconfig /all – View IP details
πΉ ipconfig /flushdns – Clear DNS cache
2️⃣ Fix Connectivity Problems
πΉ netsh winsock reset – Reset network adapter
πΉ netsh int ip reset – Reset TCP/IP stack
3️⃣ Check and Repair System Files
πΉ sfc /scannow – Scan and repair corrupted system files
πΉ chkdsk /f – Fix disk errors
4️⃣ Monitor System Performance
πΉ tasklist – View running processes
πΉ taskkill /F /PID <PID> – Force close a process
5️⃣ Check Windows Startup Issues
πΉ msconfig – Open System Configuration
πΉ bcdedit /enum – Check boot configuration
CMD is a powerful tool that can save time and effort in troubleshooting. What are your go-to CMD commands for quick fixes? Share in the comments!
π Top Windows Troubleshooting Commands Every System Admin Must Know!
πΉ Tired of clicking through menus to fix issues?
πΉ Want to troubleshoot like a pro in seconds?
Use these powerful CMD commands to diagnose and fix common Windows issues FAST!
π System & Performance Issues
πΉ Check system uptime:
wmic os get lastbootuptime
πΉ View system logs for errors:
eventvwr.msc
πΉ Scan and repair system files:
sfc /scannow
πΉ Check for corrupted Windows files:
dism /online /cleanup-image /scanhealth
πΉ Fix Windows Update issues:
net stop wuauserv
net stop bits
net start wuauserv
net start bits
π Network Troubleshooting
πΉ Check IP configuration:
ipconfig /all
πΉ Release and renew IP address:
ipconfig /release
ipconfig /renew
πΉ Test network latency:
ping 8.8.8.8 -t
πΉ Trace network route:
tracert google.com
πΉ List active network connections:
netstat -ano
πΉ Find which process is using a port:
netstat -ano | find "80"
π Disk & Storage Issues
πΉ Check disk for errors:
chkdsk C: /f /r
πΉ Show detailed disk usage:
wmic logicaldisk get size,freespace,caption
πΉ Check disk performance:
winsat disk
πΉ List all partitions:
diskpart
list disk
π User & Access Issues
πΉ Reset a local user password:
net user AdminUser NewPassword
πΉ Find locked-out users in Active Directory:
net user /domain | find "Lockout"
πΉ Force logout a user session remotely:
logoff /server:RemotePCName
πΉ List all user sessions on a server:
qwinsta
π Remote Management & Services
πΉ Check running services:
sc query state= all
πΉ Restart a service:
net stop spooler && net start spooler
πΉ Enable RDP remotely:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
πΉ Reboot a remote PC:
shutdown /r /m \\RemotePCName /t 0
π‘ Why Use These Commands?
✅ Fix issues faster – No need to dig through GUI menus
✅ Improve efficiency – Get things done in seconds
✅ Be a pro – Handle any system issue with confidence
πΉ Which command do you use the most? Comment below!
Comments
Post a Comment