OK - so I have been running Nagios for some time now very successfully monitoring various m$ servers, routers, etc. Setting up was a bit of a bear to get going, but I beat the configs into submission and they finally started being more friendly :).
ANYWAY: Here’s my latest adventure-
So we have a server running windows server 2000 which we recently had to reboot. When it came back online Nagios decided that it no longer wanted to monitor any of the services that were being checked via pnsclient, however it was still watching for DNS and actual ping.
Seemed a bit odd at first but I quickly realized all of the things that were no longer working were all things that were being watched via pnsclient. A bit more digging later I find that port 1248 (default port for pnsclient) has been taken over by LDAP on the server before the pnsclient could launch.
So I’m ok to change the port for pnsclient but that would require doing it on all of the machines I monitor (shudder), or making another custom check plugin specific to this server that used a higher port.
Is there a way for me to get the server to let go of port 1248 and reserve it for pnsclient?
If so, how and what would be the consequences of doing so being that LDAP is whats currently using it?
*To quote my buddy whom I asked about this “NO, you can not ever ever change the port that LDAP uses, that will make your servers stop authenticating” - True?
Any thoughts, feedback welcome. I am just trying to keep this simple and prevent it from happening in the future.
ADVICE TO THE NAGIOS NOOBS: If/when you decide to use any of the remote plugins that use check_nt for disk, services, etc, be sure to make the port it operates on above 5000 so windows does not try to jack with it.
PS- Big thanks to Evert and all the Nagios gurus around here who have been so mega helpful int he past.