How to Fix: Network Error: No connection could be made because the target machine actively refused it

The 'Network Error: No connection could be made because the target machine actively refused it' error occurs when a client attempts to establish a connection with a server that is not listening on the specified port. In this case, you're trying to bootstrap a server via Chef using WinRM (Windows Remote Management), but are encountering this error despite opening port 5985 on the remote server.

This issue can be frustrating, especially when troubleshooting and testing are involved. However, by following these steps, you should be able to resolve the problem and successfully connect to your target machine.

⚠️ Common Causes

• The primary reason for this error is that the WinRM service might not be running or configured correctly on the remote server. Even if the port is opened in the firewall, the service needs to be up and listening on that port for connections to be established.
• Another possible cause could be Windows Defender Firewall or other host-based firewalls blocking the incoming connection. Additionally, network policies or group policy settings might also prevent the connection from being made.

✅ Best Solutions to Fix It

✨ Wrapping Up

By following these steps, you should be able to resolve the 'Network Error: No connection could be made because the target machine actively refused it' issue and successfully connect to your remote server via WinRM. Remember to verify that the WinRM service is running and configured correctly, and ensure that any firewall rules are in place to allow incoming connections on port 5985.