Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Status:unassigned Failure reason: Scheduler Error

I have installed SolarWinds onto Windows 2008 R2 Standard and added all SNMP details, plus given the server free roam through the firewall.

I have added a few nodes and then scanned for applications, any server that is on the same domain as the Solarwinds server picks up both applications I asked, which is IIS and Windows 2003 and 2008 but when I attempt to scan nodes that are on a different domain it picks up no applications, even though IIS and Windows 2008 are installed on the,.

SNMP details are set and correct. We also have a domain policy firewall configured and I have set this to Allow Any inbound and outbound rules but still this does not pick either of the applications and once the scan is complete it states the the subject line message for this post.

Is there something I am missing?

Hope to get this resolved.

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

The Windows Server 2003 - 2008 and IIS Application templates in APM use WMI and RPC, not SNMP to collect their data. This is likely the issue you're facing. If you look at dropped packet logs on your firewall you'll likely notice a fair number of entries coming from your Orion Server. WMI is not a firewall friendly because it uses a dynamic port range. You may want to consider changing the fetching method in the service component monitors to RPC instead of WMI. The Windows Performance Counters already use RPC. I encourage you to look over the APM Administrators Guide for more information of which ports APM uses for each component monitor type.

neilgmt

Ok thanks for that but does that explain why it picks up the counters on servers on the same domain. As they must be the same component monitors not matter what domain they are on.

aLTeReGo

When applying applications to nodes in a different domain than the Orion APM server, ensure you specify a valid administrative account in the domain of the server that's being monitored, with the domain name prepended to the username in the credentials specified for the application. I.G. "mydomain\myusername".

neilgmt

I am using my own account as I am a Domain Admin on that domain, so I narrowed that down