We have a WSUS server, running on Windows Server 2019, and synchronization fails to IP address 13.95.31.95 with a timeout error.

Question

Every scheduled/manual WSUS synchronization fails when trying to connect to source server, to the IP address of 13.95.31.95, with a response timeout error.

What is going on here?

It pulls down update content from other source servers but always fails at this IP address.

Answer 1

Our Cisco Meraki firwalls are not filtering this address, nor is the server itself.

The error is:

WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 13.95.31.95:443

at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

at System.Net.HttpWebRequest.GetRequestStream()

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)

at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List1 allMetadata, List1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)

at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List1 neededUpdates, List1 allMetadata, List`1 allFileUrls, Boolean isConfigData)

at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAndSaveUpdateMetadata(List`1 updates)

at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

Answer 2

Hello,

The error message you provided indicates that the WSUS server running on Windows Server 2019 is experiencing a timeout when attempting to synchronize with a specific IP address, 13.95.31.95, over port 443 (HTTPS). Although you mentioned that your Cisco Meraki firewalls and the server itself are not explicitly filtering this address, there could still be various factors causing the synchronization failure. Here are some troubleshooting steps to help identify the issue:

1.Perform a basic ping test from the WSUS server to the IP address 13.95.31.95 to check for basic network connectivity. If the ping fails or times out, there might be routing or network infrastructure issues between your WSUS server and the destination IP.Use tracert 13.95.31.95 to trace the route taken by packets to reach the destination IP. This can help identify any hops along the path that might be causing delays or blocking the connection.

2.Ensure that the IP address 13.95.31.95 is resolving correctly to the intended WSUS upstream server. Misconfigured or incorrect DNS entries could lead to timeouts or connection failures.

3. If the IP address belongs to a public Microsoft update server, temporary ISP issues, network congestion, or upstream routing problems might be affecting the connection. Contact your ISP or check online status pages for any reported issues.

Best regards

Zunhui

Answer 3

Hi Sam,

Did you get your issue fix?

Thank you