If I want to query the status of the CPU on a server based on the IP address, I get the value correctly.
When I change the IP address to the hostname, I get the error "Cannot connect to remote Registry. Code #5".
With the System uptime I get the message:
Error: Unable to access the desired computer of service. Check the permissions and authentication of the log service of the interactive user session against those on the computer or service being monitored.
What could be the cause of this, and where can I find the log service?
Thank you.
Error code #5 IP and Hostname
Yes, sometimes Windows works this way and we are are not always sure why.
You may try to use FQDN name instead of just hostname, often this helps.
What exactly Windows do you use?
- on HostMonitor system?
- on domain controller?
- on target system?
HostMonitor started as service or application?
HostMonitor started under domain account? local account?
HostMonitor system and target systems belong to the same domain?
Have you specified user account for the test using Connection Manager (menu Profiles)?
>What could be the cause of this, and where can I find the log service?
Windows Event Log Viewer -> Security log
Regards
Alex
You may try to use FQDN name instead of just hostname, often this helps.
What exactly Windows do you use?
- on HostMonitor system?
- on domain controller?
- on target system?
HostMonitor started as service or application?
HostMonitor started under domain account? local account?
HostMonitor system and target systems belong to the same domain?
Have you specified user account for the test using Connection Manager (menu Profiles)?
>What could be the cause of this, and where can I find the log service?
Windows Event Log Viewer -> Security log
Regards
Alex
What exactly Windows do you use?
Windows Server 2022
- on HostMonitor system?
Windows Server 2022, connect to the domain
- on domain controller?
This is the target PC indeed
HostMonitor started as service or application?
Hostmonitor is installed as application on the Win 2022 server
HostMonitor started under domain account? local account?
Hostmonitor is installed as the SA account with full access
HostMonitor system and target systems belong to the same domain?
Yes, they are in the same domain
Have you specified user account for the test using Connection Manager (menu Profiles)?
No
In the logging I only see Audit Success.
What I have found out is below settings work:
CPU check - \\Hostname
Free Physical memory - \\FQDN
System Up Time - \\Hostname
When I use FQDN in CPU I get the error, also when I use only the Hostname for Free Physical memory I get also the errors.
Windows Server 2022
- on HostMonitor system?
Windows Server 2022, connect to the domain
- on domain controller?
This is the target PC indeed
HostMonitor started as service or application?
Hostmonitor is installed as application on the Win 2022 server
HostMonitor started under domain account? local account?
Hostmonitor is installed as the SA account with full access
HostMonitor system and target systems belong to the same domain?
Yes, they are in the same domain
Have you specified user account for the test using Connection Manager (menu Profiles)?
No
In the logging I only see Audit Success.
What I have found out is below settings work:
CPU check - \\Hostname
Free Physical memory - \\FQDN
System Up Time - \\Hostname
When I use FQDN in CPU I get the error, also when I use only the Hostname for Free Physical memory I get also the errors.
That's strange. CPU Usage and Memory tests use different Windows API. But we though FQDN should work in both cases.When I use FQDN in CPU I get the error, also when I use only the Hostname for Free Physical memory I get also the errors.
I tried to find some official explanation, again, but failed
Regards
Alex