How to pass thru Windows domain authentication?

[Eug]

I'm going to post this in case it may help with identifying the problem with the URL request authentication (on password protected page ).

My Lite version (6.82) running on Windows 2000 had been testing some of my internal sharepoint sites just fine for a couple of weeks.

Then today I decided to change it to run as a service.

After I rebooted and signed in to the box as an Administrator, that settings dialog (the one you see when you first install) popped up as if it was a new install. I clicked save and watched as all my other tests worked except for my SharePoint ones.

Just spent that last couple of hours, uninstalling, reinstalling to no avail.

Finally, I uninstalled and ran CCleaner. Then I reinstalled and now it works.

I had been running (and now running again) URL request tests for both HTTP and HTTPS. Both worked, then broke at the same time, and now both work again.

[KS-Soft Europe]

Finally, I uninstalled and ran CCleaner. Then I reinstalled and now it works.

So, "CCleaner" helped you to make HostMonitor to perform "URL" tests, when it was running as a serivce? Interesting... Thank you for your feedback.
Could you provide information, what exact authentication method is used by your "Sharepoint" server? "Integrated Windows Authentication"? "Basic authentication"? "Digest Authenticaton for windows domain servers"? ".Net passport authentication"?

Regads,
Max

[Eug]

Finally, I uninstalled and ran CCleaner. Then I reinstalled and now it works.

So, "CCleaner" helped you to make HostMonitor to perform "URL" tests, when it was running as a serivce? Interesting... Thank you for your feedback.
Could you provide information, what exact authentication method is used by your "Sharepoint" server? "Integrated Windows Authentication"? "Basic authentication"? "Digest Authenticaton for windows domain servers"? ".Net passport authentication"?

Regads,
Max

Well, IIS is set for Integrated Windows Authentication but SharePoint actually authenticates against a different container so I always have to sign in - it doesn't really look at my windows credentials from my PC.

One other note - after it stopped working as a service, I couldn't get the URL test to work when HM was running as an application with the service stopped and then later, removed.

After the CCLEANER, I reinstalled the app and tried to run the URL test (as an app) and it started working. I then opened up my original HTM file with all my tests and things were good. I then installed it as a service and it all seemed to run. (I'm on light w/o the web component so I don't think there's a way for me to talk to the service, but I was monitoring the logs and I would also stop the service, start the app and view the counters and saw they were increasing.)

Sometime last night, one of my URL tests (an HTTP test to my sharepoint site) started failing. The other URL test (an HTTPS test to my sharepoint site) continued to work. The log said it failed twice and then nothing else - somehow the tests stopped. Maybe it got hung?

When I would stop the service and fire up the app, the HTTP test would be successful.

So, I've made some progress where I can have the app running the tests again successfully, but the service is still an issue.

It runs as LOCAL SERVICE and I use HM to put in the userid and password of a user that has full access to my servers, as well as a userid and password in the advanced properties that is allowed into the sharepoint site.

I'm more than happy to clear up anything that my be confusing in the post, or even perform any tests that may help you.

Let me know.

[KS-Soft Europe]

One other note - after it stopped working as a service, I couldn't get the URL test to work when HM was running as an application with the service stopped and then later, removed.

Probably, it is a certificates issue? There are several settings for the "URL" test located in "Settings for the URL test" area in "Miscellaneous" tab of the "Options" dialog. Are the certificates settings enabled? Also certificates settings are located in "Test properties" window for the "URL" tests. By default these options are greyed out, this means HostMonitor should use global options specified on Misc page in the Options dialog. If you mark or unmark test options, these settings will override global options (for this specific test item only).

Sometime last night, one of my URL tests (an HTTP test to my sharepoint site) started failing. The other URL test (an HTTPS test to my sharepoint site) continued to work. The log said it failed twice and then nothing else - somehow the tests stopped. Maybe it got hung?

Hm. I do not think it got hung. What exact logging mode is specified in "Log settings" tab of the "Options" dialog? You should select "save information about every performed test (Full) from "Default logging mode" dropdown to make HostMonitor record a log about every performed test. Could you also review the IIS log for the same time period? Probably, it helps us to resolve the problems.

It runs as LOCAL SERVICE and I use HM to put in the userid and password of a user that has full access to my servers, as well as a userid and password in the advanced properties that is allowed into the sharepoint site.

I think, you should assign "Log on as service" privilege to the technical account, that is used to start HostMonitor service. You may do it using Local Security Policy applet (Start > Run > secpol.msc > Local Policies > User Right Assignment > Log on as a service). It might help.

Regards,
Max

[MikaelK]

Sorry, it seems HostMonitor does not support "Integrated Windows authentication" in some cases. We have added this task in our "to do" list. Low priority.

Regards,
Max

Are there any new development on this issue?
Am having the same problem, using Windows2003 as OS on Hostmon-server, wishing to do an URL-check against the web-part of the sharepoint-service.
Running HostMon 6.82... Has the issue been addressed in 7.0x?

Regards,
MikaelK

[KS-Soft Europe]

Are there any new development on this issue?

We have tested HostMonitor using Integrated windows authentication and it looks like it works fine. However, HostMonitor has not supported NTLM, Digest and .NET Passport authentication. These features will be implemented in future versions.

Am having the same problem, using Windows2003 as OS on Hostmon-server, wishing to do an URL-check against the web-part of the sharepoint-service.

Could you find out what exact authentication method is used by your sharepoint-service?

Has the issue been addressed in 7.0x?

"URL" test method was improved in version 7.0 and it now supports client's certificates, optional headers and POST request method. However, NTLM, Digest and .NET Passport authentication have not been implemented yet.

Regards,
Max

[david.matthewson]

I've been looking at using HM to check that a Sharepoint server (hereafter MOSS...) is correctly serving pages by looking for a specific word in the served page. (I've used this before on Appache sites with no probs - also on plain IIS6)

On MOSS it fails though. Digging deeper I see a connect on port 80 - good - and the a 402 error - failed authentication. Bad.

I've tried explicitly setting the domain admin account - and HM is running under the domain services account with God like privs.

The MOSS site asks new users for their domain login the first time they use it - so i guess this is the issue. (I've also used wget to see what happens and this too fails to authenticate so the problemis MOSS and not HM.. what I need is a way to get HM to authenticate)

I also see that HM uses bits of IE & the host registry so there may be issues there too...

Thanks in advance,

David

[KS-Soft Europe]

On MOSS it fails though. Digging deeper I see a connect on port 80 - good - and the a 402 error - failed authentication. Bad.

Error 402? As I know code 402 stands for "Payment Required". This code is reserved, but not yet described in the HTTP/1.1 specifications. Probably, you do mean 401 error?

Since version 7.00 HostMontor supports authentication using client certificates. If your MOSS server is configured to accept certificates for authentication, you may try this option. Quote from the manual:
http://www.ks-soft.net/hostmon.eng/mfra ... ts.htm#url
===============================
Use client certificate
An HTTPS server may require client authentication, in which case a local client certificate should be sent to the server for authentication. Client certificates contain information that identifies the user, as well as information about the organization that issued the certificate.
"Use client certificate" option allows you to choose certificate that will be sent to the server. If test will be performed directly by HostMonitor, application shows list of certificates installed on local system.
===============================

Regards,
Max

[david.matthewson]

Duh! Thanks Max - yes, it was a typo - I meant 401 not 402.

I'll try the certificate stuff & revert.

Many thanks for a fast & helpful reply.. if only Microsoft were as good... sigh!

David

[Guillaume]

I have the lastest version of Hostmonitor and I am very happy about this tool.

I faced a issue to test SharePoint web application based on SSO authentication. The test was all time bad status. I manage to solve the problem when I change the login / password.

It was not a issue with the login itself because I managed to test the application through runas IE but the issue was the DOMAIN and the PASSWORD.
I remove domain on the test (as the Hsotmonitor server is on the domain) and I use a login with a simple password.

I think the reason is: the usage of complexe word, for example domain with "-" like tot-it or password using something like "&..."