• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question Unmonitored servers! Services that should be monitored in DHCP, DNS and Print Servers?

PrimoMando

Junior Member
Greetings,

My company's network isn't being monitored!
I was given the task of identifying the services that run in DHCP, DNS and Print Servers that need and should to be monitored.
A list of the various services would be what I'm looking for, because then I could google each one and "learn them".
The question is assuredly vague, but I would appreciate any kind of assistance and explanation.

About the DNS Server services I found something like this, if it helps (probably wrong):
Imagem

Thank you very much.
Primo

Edit 1:

Our infrastructure is Windows Server 2012 and Windows Server 2016.
CPU and HDD are already being monitored.
I'm trying to promote an idea. I am trying to monitor the availability of the DHCP, Print, DNS servers but I need to know the running services/processes of each server that should be monitored.
 
Last edited:
Too vague of a task. What is the problem your company is trying to solve? And what type of networking equipment do they have? (Complete network layout needed to properly advise.)
 
@SamirD
Our infrastructure is Windows Server 2012 and Windows Server 2016.
CPU and HDD are already being monitored.
I'm trying to promote an idea. I am trying to monitor the availability of the DHCP, Print, DNS servers but I need to know the running services/processes of each server that should be monitored.
 
Last edited:
This are examples that might help translating the abstract need to concrete solution.





😎
 
You could do this two ways:

1) You could monitor the services on the servers themselves (which usually requires installing some kind of agent on each server)

2) You can set up some kind of network monitor that tries to connect the services that are supposed to be there (for example, by trying to do a DNS lookup) and throws an alert if something that is supposed to work, doesn't. This has the benefit of you-don't-need-to-change-your-servers but it's also a little less flexible.

If you're already doing CPU and Storage monitoring, it's entirely likely/possible that you already have an agent of some kind installed on the servers. (Unless they're all VMs, in which case you get that for "free" essentially.)

You could use something like Zabbix to do it, adhering to either model, depending on how clever you are with custom hooks.
 
Back
Top