I'm attempting to create an event log monitor to look for account lockouts (event ID 644). When I try to use the dropdown box for the log source and event source, I get the following message:
"Can not retrieve list of event logs from \\<servername>. Will be used local system list".
The server <servername> is actually a domain controller for a trusted domain. The hostmonitor server is in a different domain than this domain controller but there is a full two-way trust established. I tried using a "connect as" and putting the credentials in for a domain admin in the trusted domain, to no avail. The test always returns and "unknown" status.
I'm looking for some suggestions. Thanks.
Error when enumerating event logs
- what version of HostMonitor do you use?
- Windows version?
- HostMonitor started as application or as service?
- if it started as service, have you specified user account with necessary rights on Service page in the Options dialog?
- what about other tests (line UNC, CPU Usage, Process)? Are they work properly when you are trying to check the same remote server?
Regards
Alex
- Windows version?
- HostMonitor started as application or as service?
- if it started as service, have you specified user account with necessary rights on Service page in the Options dialog?
- what about other tests (line UNC, CPU Usage, Process)? Are they work properly when you are trying to check the same remote server?
Regards
Alex
-- Hostmonitor Version: 4.10
-- Windows Version: Windows 2000 Professional, SP4
-- Hostmonitor is started as a service
-- No other tests work, either
-- Monitored server is W2k Server, SP4
The interesting thing is that this is a Domain Controller for AD. We have 2 AD domain controllers. I can create the same test, point it at the other domain controller, and the test works fine. Both CPU and NT Log tests that I've created. Same username/password (confirmed multiple times). I use the same account for both, and since they're AD domain controllers, they both have the domain accounts present. Both are on the same network segment as the hostmonitor system.
Thanks.
-- Windows Version: Windows 2000 Professional, SP4
-- Hostmonitor is started as a service
-- No other tests work, either
-- Monitored server is W2k Server, SP4
The interesting thing is that this is a Domain Controller for AD. We have 2 AD domain controllers. I can create the same test, point it at the other domain controller, and the test works fine. Both CPU and NT Log tests that I've created. Same username/password (confirmed multiple times). I use the same account for both, and since they're AD domain controllers, they both have the domain accounts present. Both are on the same network segment as the hostmonitor system.
Thanks.