You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not limited to CLIENTVERSION but rather any attempt to query using check_nt. All other servers we have installed NSClient on respond normally with the NSClient version number. We have one particular server which simply will not allow itself to be accessed on port 12489. I have triple checked the firewall rules and there is nothing blocking it.
Actual Behavior
CRITICAL - Socket timeout after 10 seconds
Details
NSClient++ version: 0.5.2
OS and Version: Windows Server 2019
Checking from: Nagios Core 4.4.6
Checking with: check_nt
Additional Details
NSClient++ log:
The log is empty
The text was updated successfully, but these errors were encountered:
However when I try to test it from any other server, even servers from within the same security group, it cannot be accessed. I ran this command and got the same result from two other servers:
I would start by verifying if the right port can be accessed from the remote system: In your example you are checking the connection to port 14689 while the software on the remote host is listening on port 12489. This is expected to fail.
Issue and Steps to Reproduce
Describe your issue and tell us how to reproduce it.
Expected Behavior
This issue is not limited to CLIENTVERSION but rather any attempt to query using check_nt. All other servers we have installed NSClient on respond normally with the NSClient version number. We have one particular server which simply will not allow itself to be accessed on port 12489. I have triple checked the firewall rules and there is nothing blocking it.
Actual Behavior
CRITICAL - Socket timeout after 10 seconds
Details
Additional Details
NSClient++ log:
The text was updated successfully, but these errors were encountered: