This normally occurs if ipMonitor cannot communicate with the remote device using SNMP or WMI.
-To test SNMP, use the steps in the following article:
-To test WMI, use the steps in the following article:
Hope this helps.
Chris Foley | Support Specialist
SolarWinds | IT Management, Inspired By You
Support:866.530.8040 || Fax:512.857.0125
Thanks for your reply, I have managed to add SQL server service but need to add the SQl Server Type to monitor overall performance of SQL Server. I am trying this by:
Add New Monitor
Givign the the monitor a name and o.k but geting message "unable to connect to the server".
Need to force the Monitor to use NTLM Authentication instead of impersonation.
To do that, you simply create a new Credential and only select “may be used for NTLM authentication”. The problem is you can’t do that in ipMonitor 9 so use option 2 if you can't upgrade:
1. Upgrade to ipMonitor 10 and do the above trick
2. Modify Local Policies to allow account assigned to ipMonitorSrv service the ability to impersonate properly. The account needs to be added to the following policies:
- Act as part of the operating system
- Bypass traverse checking
- Log on as a Service
- Replace a process level token