UNC Failures

[sadek76]

I'm running W2K server SP3 with Hostmon version 4.86. I have a UNC "Alert when resource is unavailable" test setup. The test fails, I receive "Logon failure: unknown user name or bad password". I have HM started as a service and in the Options section I have "Use account" selected. If I go into this section and click "Save" I receive the message that the username that I have in the box is logged on. If I change this option to "Local system account" the test fails with "Access denied". In a command prompt window if I run the following command: net use \\165.168.17.11\hostmon$ /user:bsna\_IT-NASMON * Which prompts me for the password, which I put in and receive "The command completed successfully". The username and password that I used in the manual command is what I have set up in the UNC test for Connect as. This test works fine on another machine only "when I don't start it as a service".

[KS-Soft]

As I understand "_IT-NASMON" account exists on "bsna" system but local system does not have this account? What if you create the same account (with the same password) on local system? Or probably better use domain user account...

Regards
Alex

[sadek76]

Correct "_IT-NASMON" is an account on the "bsna" domain and not local to the server being checked. I tried creating a local account "manager", changed the test to use this account, but it still failed. Why does it work when the application is not running as a service?
I also changed the application "Start>Service Use account" to use my own account and changed the UNC test to connect using my account. Now I receive "A duplicate name exists on the network" in the reply field.

[KS-Soft]

[sadek76]

[KS-Soft]

[sadek76]

I tried this with both accounts and got the same results for each.

What command is the hostmon application using to make the unc connection?

I tried net use * \\165.168.17.11\hostmon$ /user:bsna\_it-nasmon * from the command prompt and it worked. Using the first * lets me map to my next available drive letter. I then went to that drive did a dir and found out that the admin had shared the entire C: drive instead of just a blank folder called hostmon$. I'm having the admin recreate the share the correct way and will let you know the results.

[KS-Soft]

HostMonitor uses WNetAddConnection2 function
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wnet/wnet/wnetaddconnection2.asp
I have not find any notes specific to service mode...

Regards
Alex

[Marcus]

If you still get the "logon failure: unknown user name or bad password", then check the security log on the remote system. It will tell you with which account hostmonitor tries to log on to the system (which could be different from what you think it should be).

We monitor many servers on many different domains (and forrests) and have no problem. This is how we have setup HostMonitor:

- Installed HostMonitor as a service
- Configured the start-up account for the HostMonitor service to a monitoring account (hmmon)
- Configured the same start-up account (hmmon) on the options dialog.
- Configured the same start-up account (hmmon) on every server. This should be a local account for non domain controllers!

We then log on to the server running HostMonitor, using the start-up account (hmmon), stop the service, start HostMonitor as an application, make our modifications (and save them), stop HostMonitor and start HostMonitor as a service (do you stop the HostMonitor service before you make modifications?)

But first: Check the remote security log!

[sadek76]

Checked the security log and it showed that Success Audit for the user "manager" and in a different test "Success Audit" for user "_IT-NASMON." But the hostmon application still showed that the test failed. And before you ask, "I don't have Reverse Alert box checked"

[KS-Soft]

As I understand you have this problem with single system? What if you simply install RMA on that system?

Regards
Alex

[sadek76]

[KS-Soft]