![所有新的 WSUS 客户端上均出现 0x8024401c](https://linux22.com/image/698143/%E6%89%80%E6%9C%89%E6%96%B0%E7%9A%84%20WSUS%20%E5%AE%A2%E6%88%B7%E7%AB%AF%E4%B8%8A%E5%9D%87%E5%87%BA%E7%8E%B0%200x8024401c.png)
我在连接到 WSUS 的所有新客户端上不断收到错误 0x8024401c。(仅限 Windows 10 和 Server 2016)
根据 Google 的说法,此错误导致“WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT”,但我可以 ping 服务器并从失败的客户端访问 /ClientWebService/client.asmx。
有人知道如何解决这个问题吗?
我应该担心那些 1601/01/01 日期吗?
...
2017/02/03 12:09:39.7930127 1868 8528 WebServices WS error: There was an error communicating with the endpoint at 'http://wsus.fqdn:8530/ClientWebService/client.asmx'.
2017/02/03 12:09:39.7930135 1868 8528 WebServices WS error: There was an error receiving the HTTP reply.
2017/02/03 12:09:39.7930143 1868 8528 WebServices WS error: The operation did not complete within the time allotted.
2017/02/03 12:09:39.7930150 1868 8528 WebServices WS error: The operation timed out
2017/02/03 12:09:39.7930162 1868 8528 WebServices Web service call failed with hr = 8024401c.
2017/02/03 12:09:39.7930162 1868 8528 WebServices Current service auth scheme=0.
2017/02/03 12:09:39.7930166 1868 8528 WebServices Current Proxy auth scheme=0.
2017/02/03 12:09:41.7937260 1868 8528 WebServices Auto proxy settings for this web service call.
1601/01/01 01:00:00.0000000 1868 8528 Unknown( 49): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).
1601/01/01 01:00:00.0000000 1868 8528 Unknown( 57): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).
1601/01/01 01:00:00.0000000 1868 8528 Unknown( 11): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).
...
编辑:
在谷歌搜索失败近一个月后,它又恢复了。也许是补丁修复了它。如果我发现什么,我会在这里发布结果。
答案1
- 尝试在问题客户端上运行它:
wuauclt/reportnow
wuauclt/detectnow
- 确保补丁没有改变任何防火墙设置。