Quick troubleshooting view
Remote Desktop connection to a Windows server or post fails.
- Port 3389 filtered
- RDP deactivated
- Service:
- Test port
- Test IP connectivity
- Check service locally
- Restoring the RDP service
- Correcting the19/routing
- Correct the authentication or NLA policy
Contextual technician plan
Use Test-Net-Glogon on 3389.
Test-Net-Gonneur server.example.local -Port 3389The command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Check ping/routing if relevant.
Well-Service TermServiceThe command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
If you have a console access.
“Check service locally” should produce an observation that clearly confirms or rules out “Service:”.
If the observation is normal, lower “Service:” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Service:” first. Related action: Correct the authentication or NLA policy.
Distinguish network refusal and refusal of authentication.
“Read message of error” should produce an observation that clearly confirms or rules out “NLA/Authentication”.
If the observation is normal, lower “NLA/Authentication” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “NLA/Authentication” first.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Clash if multiple servers become inaccessible simultaneously via RDP.
Remote Desktop connection to a Windows server or post fails.
Causes probables
- Port 3389 filtered
- RDP deactivated
- Service:
- NLA/Authentication
- Routing/NPV
- Number of sessions or policies
Diagnostic étape par étape
- 1
Test port
Use Test-Net-Glogon on 3389.
- 2
Test IP connectivity
Check ping/routing if relevant.
- 3
Check service locally
If you have a console access.
- 4
Read message of error
Distinguish network refusal and refusal of authentication.
Commands utiles
Test-Net-Gonneur server.example.local -Port 3389Well-Service TermServiceSolutions possibles
- Restoring the RDP service
- Correcting the19/routing
- Correct the authentication or NLA policy
Clash if multiple servers become inaccessible simultaneously via RDP.