Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have configured a Nagios server which is working well with all king of clients. But when I added a new windows machine to monitor, it gives a error message "connection refused". I have set everything as prior machines.
Now, I just wanted to know the process by which we can check if server is able to communicate with the client's NSclient daemon. In Linux, we simply issue "./check_nrpe -H hostname" and if ok, it gives the NRPE version which indicates the status ok.
I'm not familiar with Nagios, but Connection Refused suggests that at the basic network level you are not connecting, so either nothing is listening on that port, or it is being blocked. run "netstat -plunt" to see what's listening on your server (i wouldn't know which port specifically to check for, as i've not used it) If something is listening, check "iptables -L -n -v" for anything blocking it, and if there's still no joy, run a tcpdump on that server interface to watch for connection attempts from the source IP in question.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.