For the Remote Desktop timeout error, check these items in order:
- Verify the remote computer is available.
- Make sure the remote computer is turned on.
- Try connecting by computer name and by IP address.
- Confirm the remote computer is reachable on the network.
- Confirm Remote Desktop is allowed.
- The error can occur if remote access is not enabled on the target machine.
- Also make sure no policy is blocking Remote Desktop connections.
- Check Windows Firewall on the remote computer.
- Open wf.msc.
- Go to Inbound Rules.
- Make sure these rules are enabled for all profiles:
- Remote Desktop - User Mode (TCP-In)
- Remote Desktop - User Mode (UDP-In)
- PowerShell alternative in an elevated session:
Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True
- Check other network controls.
- If there is a firewall, proxy, antivirus, or network security filtering between the two computers, it may be blocking RDP traffic.
- If possible, temporarily disable antivirus and test again.
- In Azure, verify the Network Security Group allows RDP.
- Verify the machine state.
- If the machine is running but still cannot be reached, test access through console access if available.
- If the machine cannot be put into a running state, or console access also fails, Microsoft Support is required.
- If the issue is specifically a timeout on a remote management connection using WMI, use the maximum wait flag.
- For
SWbemLocator.ConnectServerorIWbemLocator::ConnectServer, setwbemConnectFlagUseMaxWaitorWBEM_FLAG_CONNECT_USE_MAX_WAITto128 (0x80)to impose a two-minute timeout.
- For
If the connection still fails after firewall and network checks, and connectivity tests remain unsuccessful, contact Microsoft Support.