URL Test fails (As Service/ Windows authentication)

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
Guerito
Posts: 7
Joined: Wed Oct 14, 2009 1:21 am

URL Test fails (As Service/ Windows authentication)

Post by Guerito »

I am trying to do a URL Test for an intranet site that uses Windows authentication (anonymous access is disabled). The test works from the desktop, but if I run HM as a service it fails. In HM options, I did set the proper login information (same as desktop user). However, in the Services console, the HM service still has the local system account. I cannot change this without losing the desktop interaction.

My workaround is that I do this URL test from an RMA Agent that runs on the desktop, which is a bit clumsy because I need to have the machine set to autologon.

Is there a better way to do this?

I am running HM 8.26 on Windows XP Pro SP3 in a VMWare virtual machine on an ESX server.
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

In HM options, I did set the proper login information (same as desktop user). However, in the Services console, the HM service still has the local system account
Yes, this is correct configuration.
The test works from the desktop, but if I run HM as a service it fails.
We cannot reproduce the problem. URL test works fine on our system.
You are using URL test method, right? not HTTP test?
Are you checking HTTP or HTTPS service?

Regards
Alex
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Ok, we are able to reproduce the problem. And I think I know the reason but I don't know how this can be fixed... have to read Microsoft manuals.
BTW: HTTP test may work fine for you (if you are not testing HTTPS server).

Regards
Alex
Guerito
Posts: 7
Joined: Wed Oct 14, 2009 1:21 am

Post by Guerito »

I tried HTTP test and it works together with Basic/ NTLM authentication. This is much better than my workaround. :)

Thanks!

Regards,
Juergen
Post Reply