Windows monitoring nagios check_nt problem

[tgriep]

Can you post your nsclient.ini file after the reinstall?
Can you try putting a blank password in the ini file and see that works?

Code: Select all

password =

[Box293]

What happens when you stop the service on the Windows server? Does it still report invalid password?

Do you have a file in the NSClient++ directory called boot or boot.ini ? If yes, what are the contents.

[donKanon]

Can you post your nsclient.ini file after the reinstall?
Can you try putting a blank password in the ini file and see that works?

Code: Select all

password =

I leave that just like for default

;password=

[donKanon]

What happens when you stop the service on the Windows server? Does it still report invalid password?

Do you have a file in the NSClient++ directory called boot or boot.ini ? If yes, what are the contents.

the report show a grey status.

the NSCLIENT++ have a boot.ini this is:

[settings]
1=ini://${exe-path}/nsclient.ini
[main]
write=ini://${exe-path}/nsclient.ini

that I metioned that we have a older nagios version full operational with the same configuration and all the server are reporting properly.

[Box293]

Can you post your nsclient.ini file after the reinstall?
Can you try putting a blank password in the ini file and see that works?

Code: Select all

password =

I leave that just like for default

;password=

He's asking you to uncomment it (remove the ; at the start) to see if that helps.

Can you post your nsclient.ini file.

What happens when you stop the service on the Windows server? Does it still report invalid password?

Do you have a file in the NSClient++ directory called boot or boot.ini ? If yes, what are the contents.

the report show a grey status.

What output / error message is produced ?

[donKanon]

the result I show it below and Attach the nsclient.ini with the password =

[Box293]

I just tried your config file and it works correctly, no password error.

First thing I would do is restart the server that NSClient++ is running on.



Can you double check that 10.30.1.80 is the IP address of the machine that you provided the nsclient.ini file from.

[donKanon]

yes it's the IP... and of course I restart de service many times..

[rkennedy]

Did you restart the entire machine, or just the service?

If this is working fine on another machine, can you show us the full input / output and check_command definitions it's using?

What happens when you stop the service on the Windows server? Does it still report invalid password?

Do you have a file in the NSClient++ directory called boot or boot.ini ? If yes, what are the contents.

the report show a grey status.

Can you show us what you mean by a 'grey' status? What is the error message?