Can SNMP be used for discovering Windows Servers?DescriptionIf Port Probes is in place, then SNMP can be used for discovering Windows Servers.InstructionsWhen a Discovery runs, the below phases play major role:1. Shazzam2. Classification3. Identification4. ExplorationThe first phase, Shazzam, is responsible to check what ports are opened on the target device. In this phase, Shazzam probes are released targeting the server to see on which port the Discovery process can connect. Depending upon the port it connects, Discovery comes to know what kind of device it is. On a Windows server, Discovery will connect to WMI port 135; if it is a Linux/Unix server, it will get connected to SSH port 22; if it is a Network Device, it will get connected to SNMP port 161.These ports follow a "Port Priority". If it is a Windows Server, the Priority is always WMI port 135. If it is a Linux/Unix server, the priority is SSH port 22. When you run a discovery against a Windows server, no matter if the SNMP port 161 is still opened, the priority is always WMI port 135 and that port is chosen for further communication. If the WMI port 135 is not opened on the Windows server, or is blocked, then it will fall back to the other ports it can connect to.The priority is as follows:1 - WMI2 - SSH3 - SNMP4 - HTTPThe SNMP port is in 3rd priority, so only when WMI and SSH are not reachable, the Discovery will fallback to the SNMP port.Additional InformationPort Probes