New install of UF windows, splunkd.log says "sock_error = 10054. SSL Error = No error"

[gregbo]

I just installed a new UF on a Windows VM, and I'm getting an error that connection to the host failed, with "sock_error = 10054. SSL Error = No error"

The indexers I'm trying to connect to can talk to a bunch of other Windows VMs.
The ports to the indexers are open from the Windows VM that's having the problem.
This configuration worked when I installed it on other VMs

What does "SSL Error = No error" mean?

[jhornsby_splunk]

"SSL Error = No error" means exactly that. The important error here is the 10054, which is WSAECONNRESET. From
https://docs.microsoft.com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
Is the configuration on the new UF and the working UFs definitely the same? Are they on the same network? Are there any external firewalls in the path? Can you try using the Test-NetConnection PowerShell cmdlet to verify connectivity (may not be available in old versions of Windows, so do following instead: (New-Object System.Net.Sockets.TcpClient <host>, <port>).Close()).