This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Windows Service Monitoring for server in DMZ

matt_wassall over 7 years ago

I am throwing this out there and I know others have had the issue, but according to my Google search, it hasn't been answered yet. So, I'm trying to figure out the best and most secure way to set up Windows service monitoring on a server that sits in our DMZ? I don't want to open up a bunch of ports in the firewall so it can be reached by WMI. I've considered using the agent, but I didn't know if that's what was recommended, or if that would even work? If someone has been able to successfully do this, I would love to hear how you did it. Thank you in advance for any input.

Thanks,

Matt

Top Replies

Parents

0 duncan.murray over 7 years ago

Hi there. Although I have not implemented this, I was advised from our Solarwinds provider yesterday that the use of an agent deployed into the DMZ is the best way. We are in the same situation and deploying the agent requires a single port port to be opened on the firewall (according to them)
We also plan to deploy a simular method for our Azure VMs where access is only via the internet.
I hope this helps.
Cancel
Vote Up +3 Vote Down

Cancel
0 matt_wassall over 7 years ago in reply to duncan.murray

Thank you for your response, it is very much appreciated! I got the same information you did, that we need to open up :17790 in order for the agent to talk to Orion. I'm currently waiting on our Security team to make the firewall mod. I can let you know if it was successful once it is done if you'd like?
Cancel
Vote Up +3 Vote Down

Cancel

Reply

0 matt_wassall over 7 years ago in reply to duncan.murray

Thank you for your response, it is very much appreciated! I got the same information you did, that we need to open up :17790 in order for the agent to talk to Orion. I'm currently waiting on our Security team to make the firewall mod. I can let you know if it was successful once it is done if you'd like?
Cancel
Vote Up +3 Vote Down

Cancel

Children

0 duncan.murray over 7 years ago in reply to matt_wassall

Brilliant, please let me know. Its going to be the new year before we implement.
Duncan
Cancel
Vote Up 0 Vote Down

Cancel
0 designerfx over 7 years ago in reply to matt_wassall

It doesn't *have* to be port 17790, you can pick a port and/or configure the agent locally to use a particular proxy. I've done this exactly as duncan.murray@capita.co.uk mentions for the same purpose - to monitor azure VM's. However, in my case I wanted a single IP and a single port - so I had one of the VM's in each cloud serve as a proxy - and all the other agents were configured to use said VM as a proxy in order to send data back to onsite.
Cancel
Vote Up +3 Vote Down

Cancel