Unable to Connect Error - Service Monitor

Is the node already added into the "nodes table" and is it only giving the error when you add the SAM Template, or do you already face the issue when adding the node itself.

I'm attempting to add the node. I could ostensibly add the node - I'm using SNMP, and the other monitors come back just fine. It's any service-based monitors I'm trying to add.

please try the following:

open a mmc on the Orion Server with the user you want to use to monitor the services, add snap-in , add computer management, do not use the local machine but try connecting to the failing server with that snapin (you need to specify \\servername)

if that works we need to check otherwise, if that doesn't work there is something wrong outside of Solarwinds

That worked. I was able to MMC, Add Snap-In, select Computer Management, specify the name of the server I want to monitor, and have Computer Management successfully load for the target server.

Alright, so we know most remote management functionality is there. Could you try to monitor the node via wmi and then inherit the credentials from the node in the SAM Template. This is to check if it is a credentials issue.

I get the following error:

Server unavailable using WMI. Unable to connect to <IP Address> for WMI access. Unable to connect to server <IP Address> as user <Domain\MonitorAccount>.

Could you check here: Test remote WMI connectivity

I am not sure if you can monitor the Services over SNMP... I have to check that.

I performed the WMI test, and got results back as the test indicates I should.

Looks like a tough one. at the moment I am out of ideas that do not need any "remote connection" from my side to actually "see" the issue. if you want, we can try to figure out a way to do a quick remote session

It's strange. Shortly after I ran the WMI test, the application monitors that utilize WMI began to work, and I was seeing data. But when I checked this morning, they are in unknown status with the 'Server Unavailable' error once more.