Nagios Support Forum

I deleted the windows host, have the NSC ++ client pointing at the new nagios server and am allowing connections there from any nsc client. I ran the configuration wizard and it failed. I am going to work on this from home and would like some input on what my next steps might be.

Also I wanted to delete the host and start fresh but was warned of dependencies that won't allow me to delete. How do I clear those dependencies.

Okay, I have edited the /etc/xinetd.d/ncas file to allow connections from any host and I reinstalled the nsc++ agent on the windows server to point at the nagiosxi server. Now all the services are critical with message "connect to address 172.22.2.45 and port 12489 connection refused. Also I ge...

Does the OVM come with nrpe installed and automatically communicates with NSC+

I am using a stable 64 bit client of NSC+ on the Windows client, but where is the link to download the recommended nagios and I will go on the Windows Server and download it. However several windows servers were added during the quick start and they seemed to work. What and how do I do this: If not ...

trying to add a host to be monitored and all fails except ping. I know the NSC client is running on the Windows server I am trying to monitor. First I just ried adding and monitoring common alerts usually done, cpu, uptime,disk usage, and of course ping. Then I tried adding the host in the nagios in...

heated debate...I don't bother, I have been using vi for a lifetime and it just works...I am on the website by using a browser on the same subnet...I am configuring, but what files need to be configured in http config to allow myadmin? I'll figure out the netowrk subnet problem after. I'm just glad ...

I think I can access from the same subnet. I will do that and use the configuration manager to finish configuring...standby...and thanks

I cannot use DHCP here. Not allowed except on the desktop pcs
The device is alive(eth0) but I can't ping it so I don't think I can use traceroute from another machine to reach it
the netmask is set to 255.255.255.0 which is what the netmask is on all the servers

if config shows device is broadcasting on the local loopback and on eth0....