Timeout or Connection Error

If you see a Connection Error state for Resources from the Nodinite Windows Server Monitoring Agent, this guide helps you quickly identify and resolve the most common causes.

✅ Diagnose network, firewall, and port issues step by step
✅ Learn how to use ping, telnet, and PowerShell for troubleshooting
✅ Optimize agent configuration for large-scale monitoring

Common Problems

• There is a network connection problem between the Nodinite Monitoring Service and the installed instance of the Nodinite Windows Server Monitoring Agent.
• There is a network connection problem between the installed instance of the Nodinite Windows Server Monitoring Agent and one or more of the configured Windows Servers to monitor.
• The number of configured Windows Servers monitored from the agent is too high, and the default timeout to fetch monitoring information is exceeded.
• Firewalls are blocking required ports.
• The PowerShell feature requires WinRM to be enabled on remote Windows Servers.

Common Solutions

• Investigate the network for connection problems. If allowed, try to ping or use a telnet session to test connectivity.
• If you do not plan to add more servers to monitor, try increasing the Timeout for the agent. If you plan to add more servers, split the monitored servers across several installed instances of this agent.
• Make sure both software and hardware firewalls allow the required traffic.