0x11 - Rdp 0x3
Date: October 26, 2023 Category: System Administration / Windows Server Tags: RDP, Windows Server, Troubleshooting, Licensing
Large RDP packets may be fragmented incorrectly. Aggressive firewalls or VPNs that drop ICMP "fragmentation needed" packets can cause the RDP handshake to time out and log 0x11. rdp 0x3 0x11
These two errors together frequently appear when: Date: October 26, 2023 Category: System Administration /
Typical Event ID: 38, 39, or 40 from TerminalServices‑LocalSessionManager. Typical Event ID: 38 , 39 , or
| Code | Name | Meaning |
|------|------|---------|
| 0x3 | ERROR_PATH_NOT_FOUND | The system cannot find the path specified. Often indicates profile path issues (roaming profiles, home drives, or user profile disk). |
| 0x11 | ERROR_BAD_NET_NAME | The network name cannot be found. Points to a missing or inaccessible network share/resource. |
The Microsoft RDP client (mstsc.exe) stores cache files. Corruption in bitmap cache or certificate cache on the client side can also trigger this error.
You will typically see a generic dialog box: "An internal error has occurred."
But behind the scenes, the Event Viewer tells the real story: