- If you configure SNMP Profiles in the Men & Mice Suite for router/switch discovery of ARP information as well as subnet information you want to check that the configured SNMP port (usually port 162/UDP) on the routers/switches is accessible
by the machine that is executing the Men & Mice Central process/service.
- The DNS/DHCP Controller service on Windows is utilizing RPC calls to communicate with the DNS/DHCP servers. Please make sure that the Controller service can access port 135/TCP and high ports (usually 49152-65535) on the
managed DNS/DHCP server. If the Controller is directly installed on the DNS/DHCP server (Microsoft with Agent Installed) this should not be an issue as the communication is done locally.
In case the Controller is used as proxy (Microsoft Agent-Free) and is not directly installed on the DNS/DHCP server, the mentioned ports (135/tcp and high ports) on the managed DNS/DHCP servers must be accessible by the machine that runs the Men & Mice Controller.
Please note that in a Microsoft DHCP Failover setup the Controller communicates also via RPC with the partner DHCP server directly!, e.g. if you update a DHCP reservation on server A, which runs a DHCP Controller, the Controller will connect via RPC
directly with the partner DHCP server B in order to update the DHCP reservation on server B too.
- If you configure PING sweeps (ICMP echo) on subnets in the Men & Mice Suite you want to make sure that ICMP echo requests are allowed by the machine that runs the Men & Mice Central process/service