WebJul 20, 2016 · Something appears to be preventing NSClient from binding to ports 12489 and 5666. Have you run "NSClient Test"? It may provide further clues. Cheers, Andrew flag Report Was this post helpful? thumb_up thumb_down OP michaelhuang2 pimiento Jul 20th, 2016 at 4:28 AM check Best Answer Thanks for the reply. I was able to figure out the issue. WebMay 25, 2024 · I try to put -t 30 at the end of the command and i got : connect to address IP_of_my_server and port 12489 : connection refused. (i disabled firewall too) example of request i do on sol.cfg (the name of the file for windows define service) : Code: Select all define service { use generic-service host_name sol service_description Firewall
Connection Refused error with NSClient on Windows Box - Nagios …
WebMar 5, 2013 · Port 12489 is a check_nt port only, not a nrpe port. Port 5666 is for NRPE. You need to make sure that both ports are open on both the Nagios server, and the remote NSClient++ host. The errors you are getting are still indicative of a connection interruption between the two. WebAug 6, 2024 · port 12489 Connection refused issue. I'm using NCPA to monitor a Windows machine with NRDP (passive check) and quite sure there's no port blocking issue as … how to start makeup business in nigeria
Nagios Error Message - "Could not fetch server information"
WebThis appears to be your primary problem, as only 127.0.0.1:3000 is listed in your netstat output. You will also need to ensure that "mydomain.com" resolves to the correct IP … WebJul 10, 2014 · You will also need to make sure that windows system is using 5666 for the nsclient protocol port and not 12489, which is default. You're going to want to make sure NRPE on those systems is not using 5666 anymore either otherwise you will run into socket lease issues if you are running both nrpe and check_nt checks to that system. WebAug 12, 2024 · When I try to reach any other port, my connection is timed out: $ curl myurl.com:4244 curl: (7) Failed to connect to myurl.com port 4244: Operation timed out. I have the following inbound rule on AWS: I am able to curl it on the server: $ curl localhost:4296 Hello World. My netstat: $ netstat -a grep 4296 tcp 0 0 localhost:4296 … react icons map