Cheshire Cat Computing

It would seem that way, I changed it to nagios.domain.local to protect our internal naming system - I've tried it via NetBIOS hostname (instanatly resolveable and pingable) FQDN (same) and IP Address, with a server reboot between each and it doesn't seem to make any difference.

This is starting to get frustrating - I might uninstall NSCA and EventLogAgent totally and start again. Thanks for replying Steve.

Try setting a password and using encryption methos 1 at both ends. Look in the syslog on the NSCA end and see if there are any messages.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

OK, tried that, restarted NSCA and the SysLog Event Service (which never seems to restart cleanly - I have to kill the process and start manually?!?!) and then the server the EventLog was on and still....nothing.

Sounds like you have a number of problems here.

First, do you have anything else using NSCA to verify that NSCA is working? Try using the send_nsca package on the Nagios server itself to send test NSCA messages and just verify that they are received, and appear in the nagios.log file. Then we can know NSCA is correct and nagios is processing the NSCA messages.

If you cannot stop the eventlog agent on the windows box then there is another problem. If you have win2k3 then you may need to set the security settings to allow the script to run and access the registry and to use the various DLLs. Run the agent in debug mode and see if there are any useful messages in the log.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11