问题:
今天,我在连接到 Azure 托管的 Windows 2022 服务器时开始收到错误,而直到最近(2 或 3 天前)连接还正常。
症状:身份验证(仍在客户端应用程序中填写)并通过所有安全检查阶段后发生连接错误。当要呈现 RDP 屏幕时(它已创建但仍然全黑),它给出错误。
Your Remote Desktop Services session has ended, possibly for one of the following reasons:
The administrator has ended the session.
An error occurred while the connection was being established.
A network problem occurred.
For help solving the problem, see "Remote Desktop" in Help and Support.
[Expanded Information]
Error code: 0x3
Extended error code: 0x11
请注意,即使在服务器主机内部连接到自身(使用localhost
或127.0.0.1
),也会发生此错误。
更多信息:
该服务器的控制权由安装 AnyDesk 的技术人员负责,也许它引发了某种冲突,但我不确定是否相关。
使用组策略(gpedit.msc
)禁用与硬件加速/RemoteFX 优化/UDP 连接相关的所有 RDP 设置,但没有成功。
一些(可能)相关的事件日志消息(我自己从 pt-BR 翻译了它们 - 从最后到第一排序):
Info 103 The disconnection reason is 17
Info 72 Method interface call: GetServerAutoReconnectInfo
Info 72 Method interface call: GetServerAutoReconnectInfo
Info 72 Method interface call: DisconnectNotify
Info 72 Method interface call: SetErrorInfo(0x11)
Info 72 Method interface call: PreDisconnect(17)
Info 132 The rdpdr channel was connected between server and client using transport tunnel: 0.
Info 132 The Microsoft::Windows::RDS::Geometry::v08.01 channel was connected between server and client using transport tunnel: 0.
Info 132 The Microsoft::Windows::RDS::Geometry::v08.01 channel was connected between server and client using transport tunnel: 0.
Info 132 The Microsoft::Windows::RDS::Video::Data::v08.01 channel was connected between server and client using transport tunnel: 0.
Info 132 The Microsoft::Windows::RDS::Video::Control::v08.01 channel was connected between server and client using transport tunnel: 0.
Info 72 Method interface call: ConnectNotify(SessionId=1)
Info 162 The client offers support to version 0xA0400 of RDP graphics protocol, client mode: 2, AVC available: 0. Initial Profile: 2. Server: MyServer
Info 132 The Microsoft::Windows::RDS::Graphics channel was connected between server and client using transport tunnel: 0.
Info 132 The Microsoft::Windows::RDS::Telemetry channel was connected between server and client using transport tunnel: 0.
Info 72 Method interface call: OnReady
Info 72 Method interface call: OnConnected
Info 169 The client operating system type is (1, 0). Server: MyServer
Info 132 The rdpinpt channel was connected between server and client using transport tunnel: 0.
Info 33 The RDP protocol will be using RemoteFX guest module to connect to the client computer.
Info 132 The rdpgrfx channel was connected between server and client using transport tunnel: 0.
Info 66 The RDP-Tcp#0 connection was assigned to session: 1
Info 72 Method interface call: AuthenticateClientToSession
Info 135 The multitransport connection was completed for tunnel: 3. The transport type was defined as TCP: Reason Code: 2 (Forced by Server Configuration).
Info 135 The multitransport connection was completed for tunnel: 1. The transport type was defined as TCP: Reason Code: 1 (No Client UDP Support).
Info 100 The server confirmed the client multi-transport feature.
Info 98 The TCP connection was successfully established.
Info 72 Method interface call: ProtocolComplete
Info 72 Method interface call: SendClientLicense
Info 72 Method interface call: GetSecurityFilterCreds
Info 71 The RDP-Tcp#0 connection uses video driver RDPUDD.
Info 104 The client timezone is [-3] UTC Time
Info 72 Method interface call: AcceptConnection
Info 72 Method interface call: OnStartLicensing
答案1
今天,我的一个 Server 2022 节点也遇到了同样的问题。就我而言,我发现这是因为我在尝试将集群验证报告清除为零警告时禁用了 Microsoft 远程显示适配器。禁用适配器后,似乎无法通过 GUI 重新启用它。(我有一个 OOB 管理连接,所以我仍然可以访问 GUI)
我完全卸载了该设备并建立了一个新的 RDP 会话,驱动程序已恢复,我可以远程登录。
答案2
不管怎么说,我遇到了几乎完全相同的问题。它是在我部署虚拟机后 2-3 天开始的。一个区别是我得到的是 0x10,而不是像你那样的 0x11。
我仍然能够使用 PSREMOTING 进入服务器。因此,我从 CLI 禁用了 Sophos AV,它又开始工作了。我将重新安装 Sophos Endpoint,并尝试向他们开具一张票据,看看他们是否能解决这个问题。端点日志没有显示任何条目,但它是 Sophos,所以谁知道呢。
答案3
答案4
我们找到了问题的解决方案,在我们的案例中,问题出在防病毒软件(McAfee)上,我们有一个阻止访问 Windows Server 2022 计算机的策略。
谢谢大家的帮助,我希望我的意见可以帮助你们解决你们的问题。