Windows authetification error using Connection Manager

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
Przemo
Posts: 18
Joined: Mon Sep 26, 2005 5:09 am
Location: Poland: Warsaw

Windows authetification error using Connection Manager

Post by Przemo »

Hi!
I have some problems doing 'count files' and 'folder/file size' tests on Windows server outside local domain. In the same time there is no problem doing 'check service' using the same authentification (in this case 'administrator' with blank password).
Additionally in mensioned tests I'd like to monitor files using default Windows share for drive letters (i.e. C$, D$ etc.) to do not modyfy anything on monitored server.
The matter of problem:
I get status 'unknown' for these tests.

I've provided any nessesary data for these tests in Connection Manager.
In file ConnMgr.log (for log fail attempts) a get entries:

Code: Select all

[2005-10-07 10:26:34]	Sys	Resource: \\server_name\m$	Login: administrator	Connection error #1326: Błąd logowania: nieznana nazwa użytkownika lub nieprawidłowe hasło.
<- #1326: translation to english: Login error: unknown user name or wrong password.
When I open the connection in Windows (i.e. when I map network drive from this server: \\server_name\m$ using user name server_name\administrator and appropriate password - the same as in Connection Manager) the tests work well, but I get such entry in ConnMgr.log:

Code: Select all

[2005-10-07 10:49:05]	Sys	Resource: \\server_name\m$	Login: administrator	Connection error #1219:
("The credentials supplied conflict with an existing set of credentials" - so there is already opened other connection for this netwour resource - for me this is no problem).

I've used both options in Connection Manager: 'keep active connections' and 'reconnect if necessary'

I don't want to reconnet each network drive each time I restart Host Monitor's computer to get the tests working - for me these kind of tools should work independently (to much additional aspects of its work).

HM ver: 5.38 & 5.64 Bete
HM is installed on Windows XP Prof SP2 PL
Monitored host: Windows 2000 Entpr. Server

I won't be original saying that 'this tool is great', but I want to:
THIS TOOL IS GREAT! :)
When I've presented it to my boss, he without any questions gave me free hand to buy it on enterprise licence with lifetime updates :)

Greetings,
Przemek
Poland

PS. Alex if You want my presentation of HM in english in PPT format I can send it to You (I've prepared it for an interanational viosiocall for my company)... Maybe it could be useful for Your marketing :) (of course I will cut off any data regarding my company)
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

It sounds like one old problem... HostMonitor calls Windows API function to establish communication with remote system using username and password specified for that resource, but sometimes Windows uses name and password of the user that is logged in (instead of directly specified name and password).
Unfortunately we did not find reason of that strange behavior, it happens with different versions of the Windows but not all the time.

Solution?
There is one trick:
- setup special account for HostMonitor on local system
- if HostMonitor is running as service, specify this account on Service page in the Options dialog. Otherwise log in under that account
- setup account with the same name and password on remote system

Another possible solution - install RMA on some server in that domain
THIS TOOL IS GREAT!
Alex if You want my presentation of HM in english in PPT format I can send it to You (I've prepared it for an interanational viosiocall for my company)... Maybe it could be useful for Your marketing (of course I will cut off any data regarding my company)
Thank you :)
You may send PPT to support@ks-soft.net. Its interesting how other people imagine HostMonitor.

Regards
Alex
Przemo
Posts: 18
Joined: Mon Sep 26, 2005 5:09 am
Location: Poland: Warsaw

Post by Przemo »

Hello.
Unfortunately we did not find reason of that strange behavior, it happens with different versions of the Windows but not all the time.
Could You suggest me the best Windows version for HM to avoid this problem? (I can use all versions: form NT to 2003 Server)
OR
Solution?
There is one trick:
- setup special account for HostMonitor on local system
- if HostMonitor is running as service, specify this account on Service page in the Options dialog. Otherwise log in under that account
- setup account with the same name and password on remote system

Another possible solution - install RMA on some server in that domain
Maybe there are some other tricks?
It's very important for me to do not modify anything on remote hosts.

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

Post by KS-Soft »

Could You suggest me the best Windows version for HM to avoid this problem? (I can use all versions: form NT to 2003 Server)
We recommend Windows 2000 SP4.
IMHO Windows XP, 2003 has more bugs. Windows NT is too old and does not support some functions.
Maybe there are some other tricks?
It's very important for me to do not modify anything on remote hosts.
Could you install agent on some host in that remote domain? Usually single agent may monitor entire network/domain.

Regards
Alex
Post Reply