Using Hostmon Version 7.10.
Remote host (Windows 2003 - different domain to hostmon system) using an agent at the remonte end.
The credentials for tests were set and working fine. Then we changed the password on the account in the remote domain. We reset the passwords in hostmon however they continue to get rejected with either...
RMA: 301 - Logon failure: unknown user name or bad password
or
RMA: 301 - The reference account is currently locked out and may not be logged on to.
I can unlock the account - still fails
I tried a different account altogether - still fails ( as though the one I set in the first place is now locked in).
Changed the password at the remote end back to the original - leaving all the tests still set with the new password - all tests now work, even though the passwords were supposedly wrong.
tests in question were "UNC (availability/free space)", "CPU Usage"
A U"RL request" to a secure site requiring credentials works when I update the password.
It is as though once I've created the test and set the credientias I cannot change them without re-creating the test. This would not be an huge issue except that we have alot of statistics gathered for those tests and creating new tests would cause a discontiunity in the statistics.
Svend.
Tests fail after password change
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
As I understand, RMA is running as a service, right? What account do you use to start RMA's service? Have you changed this account after you changed account in the remote domain? You may specify new username/password for the "KS Remote Monitoring Agent" service using standard windows "Services" applet.
Regards,
Max
Regards,
Max
ok so last night I set the password on the remote account back to the old password and all tests worked fine.
The remote servers were restarted this morning for unrelated reasons.
I checked and yes the RMA service logs in on the remote server as a totally different account to the one that I give as credentials for the tests to be carried out. I don't see how the two are related - one is a local account that can run the service, the other is an account with domain wide access that is able to carry out the test and has been working fine till I tried to change its password.
Today it gets wierder (remember the servers got rebooted this morning).
Now I changed the password on the account used for tests (not the account used to run the RMA service). Guess what? The tests keep working fine without any need to change the credentials being used. The one exception is the URL test that I ues to test access to the secure web site.
I changes the credentials on one of the Drive Space tests to a boguis password. It still works? But it shouldn't!
Confused? I am!
The remote servers were restarted this morning for unrelated reasons.
I checked and yes the RMA service logs in on the remote server as a totally different account to the one that I give as credentials for the tests to be carried out. I don't see how the two are related - one is a local account that can run the service, the other is an account with domain wide access that is able to carry out the test and has been working fine till I tried to change its password.
Today it gets wierder (remember the servers got rebooted this morning).
Now I changed the password on the account used for tests (not the account used to run the RMA service). Guess what? The tests keep working fine without any need to change the credentials being used. The one exception is the URL test that I ues to test access to the secure web site.
I changes the credentials on one of the Drive Space tests to a boguis password. It still works? But it shouldn't!
Confused? I am!
Yes, we know such things happen sometimes but its not our fault. Sometimes(?) Windows uses "current" account instead of account directly specified in the call (HostMonitor/RMA calls Windows API to establish network connection).
We were talking about such problem several times here but we do not have fix for that and we could not find any explanation in Windows manuals
Regards
Alex
We were talking about such problem several times here but we do not have fix for that and we could not find any explanation in Windows manuals

Regards
Alex