r/SCCM • u/Longjumping_Town_397 • 1h ago
Unsolved :( System.Net.WebException: Unable to connect to the remote server (WSUS error)
Hello,
For the past few days, we have been seeing errors in our MECM environment in both WCM.log and wsyncmgr.log stating that the site server is unable to establish a remote connection to the WSUS server.
The issue appeared suddenly. The last successful synchronization was working normally, and approximately one hour later the synchronization started failing without any known changes being made to the MECM or WSUS configuration.
According to the logs, the primary site server can no longer connect to the Software Update Point (SUP) where WSUS is installed. The error reported is essentially:
"Remote connection failed" / "Unable to connect to the remote server"
We have already verified the following:
- WSUS services are running.
- IIS is running correctly.
- The WSUS website is bound to HTTPS on port 8531.
- The WSUS server is actively servicing clients and has many established connections on port 8531.
- The SSL certificate is valid and not expired.
- DNS resolution works correctly between the servers.
- Both servers are located in the same subnet (10.100.206.0/24).
- ARP resolution works correctly between the two servers.
However, the following behavior is extremely unusual:
- The primary site server and the SUP server can no longer ping each other.
- TCP connections between the two servers fail in both directions.
Test-NetConnectionto port 8531 fails from the site server.- Even SMB/RPC related ports such as 445 and 135 cannot be reached between these two servers.
- Other servers in the environment can successfully reach the SUP server.
- WSUS clients can still connect to the SUP and are actively communicating with it.
We also tested Windows Firewall rules and even created explicit allow rules between the two servers, but the behavior did not change.
At this point, the issue does not appear to be related directly to WSUS, IIS, certificates, or DNS. It looks more like a communication problem that affects only these two specific servers, despite them being in the same subnet.
Has anyone experienced something similar before, or are there any additional areas (VMware networking, NSX, endpoint security, Windows networking, etc.) that we should investigate?
Thanks.