when i try to connect to a windows server with nsclient Version NSClientpp (Nagios) 0.2.6 2006-12-05 installed i run into an error:
[root@nagios scripts]# /usr/local/nagios/libexec/check_nt -H windows server name -p 12489 -v CLIENTVERSION
NSClient - ERROR: Invalid password.
Is it possible to run the nsclient daemon without password authentication?
My nsc.ini configuration
[Settings]
;obfuscated_password=
;
;# PASSWORD
; This is the password (-s) that is required to access NSClient remotely. If you leave this blank everyone will be able to access the daemon remotly.
password=
;
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
allowed_hosts=
;
;# USE THIS FILE
; Use the INI file as opposed to the registry if this is 0 and the use_reg in the registry is set to 1
; the registry will be used instead.
use_file=1
[log]
;# LOG DEBUG
; Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test)
debug=1
;
;# LOG FILE
; The file to print log statements to
file=d:\logs\nsc.log
;
;# LOG DATE MASK
; The format to for the date/time part of the log entry written to file.
;date_mask=%Y-%m-%d %H:%M:%S
[NSClient]
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to NSClient deamon.
; If you leave this blank the global version will be used instead.
allowed_hosts=
;
;# NSCLIENT PORT NUMBER
; This is the port the NSClientListener.dll will listen to.
port=12489
;obfuscated_password=
password=
;
;# BIND TO ADDRESS
; Allows you to bind server to a specific local address. This has to be a dotted ip adress not a hostname.
; Leaving this blank will bind to all avalible IP adresses.
; bind_to_address=
Thanks for Help
Bernd
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had the same problem you are describing, and I discovered that the nsclient++ recuires a password even though the sample configuration says that you can leave it blank.
So you have to enter a password, and everything works as it should.
/Kasper
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this is (was) a bug and have been fixed in the latest nightly...
// MickeM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-14
Hi all,
I have same problem!
At the moment I recieve Invalid password about twice a week.I have NSClient++ 0.2.7 installed on about 8 servers. I have checked the NSClient++ log file, there I can see NSClient++ is missing first character of the password!
I thought password problem has been solved in 0.2.7 version.
Thanks,
Harry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
feel free to use the trac site instead as I dont really use sf much (since I think it is slow and suck) anyways, This seems to be a "new password" issue, that I have not heard of, could you send me the log from when it is happening, and are you experiencing any other problems?
Seems strange that it would "miss" the first char but I can look into it, but any more details would be appreciated.
// Michael Medin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
when i try to connect to a windows server with nsclient Version NSClientpp (Nagios) 0.2.6 2006-12-05 installed i run into an error:
[root@nagios scripts]# /usr/local/nagios/libexec/check_nt -H windows server name -p 12489 -v CLIENTVERSION
NSClient - ERROR: Invalid password.
Is it possible to run the nsclient daemon without password authentication?
My nsc.ini configuration
[Settings]
;obfuscated_password=
;
;# PASSWORD
; This is the password (-s) that is required to access NSClient remotely. If you leave this blank everyone will be able to access the daemon remotly.
password=
;
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
allowed_hosts=
;
;# USE THIS FILE
; Use the INI file as opposed to the registry if this is 0 and the use_reg in the registry is set to 1
; the registry will be used instead.
use_file=1
[log]
;# LOG DEBUG
; Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test)
debug=1
;
;# LOG FILE
; The file to print log statements to
file=d:\logs\nsc.log
;
;# LOG DATE MASK
; The format to for the date/time part of the log entry written to file.
;date_mask=%Y-%m-%d %H:%M:%S
[NSClient]
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to NSClient deamon.
; If you leave this blank the global version will be used instead.
allowed_hosts=
;
;# NSCLIENT PORT NUMBER
; This is the port the NSClientListener.dll will listen to.
port=12489
;obfuscated_password=
password=
;
;# BIND TO ADDRESS
; Allows you to bind server to a specific local address. This has to be a dotted ip adress not a hostname.
; Leaving this blank will bind to all avalible IP adresses.
; bind_to_address=
Thanks for Help
Bernd
Hi Bernd.
I had the same problem you are describing, and I discovered that the nsclient++ recuires a password even though the sample configuration says that you can leave it blank.
So you have to enter a password, and everything works as it should.
/Kasper
this is (was) a bug and have been fixed in the latest nightly...
// MickeM
Hi all,
I have same problem!
At the moment I recieve Invalid password about twice a week.I have NSClient++ 0.2.7 installed on about 8 servers. I have checked the NSClient++ log file, there I can see NSClient++ is missing first character of the password!
I thought password problem has been solved in 0.2.7 version.
Thanks,
Harry
feel free to use the trac site instead as I dont really use sf much (since I think it is slow and suck) anyways, This seems to be a "new password" issue, that I have not heard of, could you send me the log from when it is happening, and are you experiencing any other problems?
Seems strange that it would "miss" the first char but I can look into it, but any more details would be appreciated.
// Michael Medin
I have the same problem, but I do use a password.