-
Гость, успей присоедениться к сообществу и получи доступ ко всем материалам. Подробности...
-
-
The Remote Desktop connection error 0x904 (Extended Error 0x7) typically indicates a general network connectivity or security negotiation failure. While often cited as a "dodgy connection" issue related to unstable network or slow VPNs, deeper technical analyses point to three primary root causes: expired RDP certificates, security layer mismatches, and firewall/compatibility bugs introduced in Windows 11 updates. Technical Root Causes
The "Extended Error 0x7" often surfaces when the client and server cannot agree on how to secure the connection:
Expired Self-Signed Certificates: Every RDP server uses a certificate to encrypt the session. If this certificate expires and fails to auto-renew, the connection fails with 0x904.
Security Negotiation Mismatch: Mismatched encryption ciphers or issues with Network Level Authentication (NLA) can cause the handshake to fail even if the server is reachable via port 3389.
Windows 11 Compatibility: Users frequently report this specific error after upgrading to Windows 11, which may involve changes to how mstsc.exe handles UDP traffic or security certificates. Evidence-Based Solutions
Based on technical discussions from Microsoft Q&A and sysadmin communities, use these methods to resolve the error:
Fixing an RDP error: This computer can't connect to the remote computer The Remote Desktop connection error 0x904 (Extended Error
The "Remote Desktop Connection Error 0x904 (Extended Error 0x7)" is a multifaceted technical barrier that typically signals a breakdown in the handshake between a client and a remote host. While it is officially categorized as a network connectivity error, its "Extended 0x7" suffix often points to deeper issues involving expired security certificates or protocol mismatches rather than a simple lack of internet access. The Nature of the Error
At its core, error 0x904 occurs when the Remote Desktop Protocol (RDP) client cannot establish or maintain a stable connection to the destination. The "Extended Error 0x7" specifically flags that while the network route might exist, the session was terminated prematurely during the initialization phase. This is common in environments utilizing VPNs, where latency or packet loss can cause the sensitive RDP handshake to time out. Primary Causes
Unstable Network Infrastructure: High packet loss or insufficient bandwidth can prevent the RDP session from reaching the necessary state for login.
Expired or Corrupt RDP Certificates: One of the most documented "hidden" causes is an expired self-signed certificate on the host machine. If the certificate used to encrypt the RDP session has lapsed, the client will reject the connection with a 0x904 error.
Firewall Interference: Security software, such as Windows Defender or Bitdefender, may block the mstsc.exe process or the standard RDP port (3389).
Network Level Authentication (NLA) Conflicts: Protocol mismatches, particularly after a Windows 11 upgrade, often trigger this code if the client and server cannot agree on the required security layer. Strategies for Resolution Open Remote Desktop Session Host Configuration ( tsconfig
Solving this error requires a tiered approach, starting with the network and moving toward the system's security architecture:
Validate Connectivity: Test the connection using the host's IP address rather than its DNS name to rule out name resolution issues. Use the command Test-NetConnection [IP] -Port 3389 in PowerShell to verify the port is open.
Renew Certificates: On the host machine, administrators should check the Certificates (Local Computer) snap-in. Deleting an expired Remote Desktop certificate and restarting the TermService (Remote Desktop Services) will force Windows to generate a fresh, valid certificate.
Adjust Security Layers: If certificates are not the issue, disabling NLA or forcing a specific security layer (like RDP instead of SSL) via Group Policy can sometimes bypass compatibility-driven disconnects.
Firewall Exceptions: Ensure both mstsc.exe and the "Remote Desktop" app are allowed through the firewall for both Private and Public profiles on the client and server.
In summary, the 0x904 / 0x7 error is rarely a sign of a "broken" computer, but rather a sign of a "misaligned" one. By ensuring certificates are current and network security rules are properly configured, users can restore the seamless remote access essential for modern digital workflows. Summary: The fastest fix is usually Solution 1
Are you experiencing this error on a personal computer or within a corporate environment using a VPN? Fixed: Remote Desktop 0x904 Error [2 Solutions] - AnyViewer
Based on the specific error codes you provided, this issue is most commonly caused by a Network Level Authentication (NLA) mismatch or a restriction on the number of allowed RDP sessions.
Here is a targeted troubleshooting piece to resolve this error.
Extended error code 0x7 can occasionally reference a refusal due to resource limits. If you are using the Remote Desktop Services (RDS) role rather than a standard desktop OS:
tsconfig.msc).Summary: The fastest fix is usually Solution 1. By disabling the NLA requirement, you force the connection to authenticate at the session layer rather than the network layer, bypassing the specific handshake causing error 0x904.