Quantcast
Channel: THWACK: Unanswered Discussions - All Communities
Viewing all articles
Browse latest Browse all 19321

Assistance Needed with Windows Monitors

$
0
0

I am mainly a Unix System Admin that has now implemented NPM and SAM on AIX and Solaris nodes.  My company also produces Windows software and I am now tasked with adding monitors for those servers.  The only local nodes to the Orion server are the Orion server itself and the firewall.  Everything else is on remote sites and accessed through VPN tunnels through the local firewall.

 

I started with creating a node of the Orion server and assigning the "Windows Server 2003-2008 Services and Counters" Application Monitor which has been working well for some time.  Now I am attempting to add the newer "Windows Server 2003-2012 Services and Counters" Application Monitor to a remote Windows server.  The local Orion server was simple to set up from what I recall but this one has been more difficult.  I think I have it mostly figured out but need some assistance with the last few steps and have not found the answer here in the forums.

 

At this point, I have node added to NPM and it is recognizing and reporting on the typical CPU, Memory, Disk, etc. resources for that node.  I needed to open port 135 in the tunnel to make this work.

 

I have also added the "Windows Server 2003-2012 Services and Counters" Application Monitor to that same remote node.  With the 135 port open in the tunnel the "Windows Service Monitor" Component Monitors work but not the "Performance Counter Monitor" Component Monitors which error with a "The network path was not found." error.  If I don't restrict ports, all node and Application monitors work.

 

I know that DCOM is in play here for some of these and have read Setting a fixed port for WMI.  I did run into the later advfirewall option of netsh and seem to have worked my way through the new syntax.  I now have an in and an outbound rule in the nodes Windows firewall that I can "show".  I was not sure if I needed in or out so created both with slightly different rule names but the same port number.

 

When I again limit the ports through the tunnel and include 135 and the new WMI Fixed Port I created on the node, I get the same result as before when the ports were limited through the tunnel.  It appears to make no difference if the WMI Fixed Port is included or not.

 

I am likely missing a step somewhere, like maybe an option to the advfirewall rule creation.  Can someone guide me in the right direction?

 

 

THANKS

 

Mikewmi


Viewing all articles
Browse latest Browse all 19321

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>