In our windows (2012) environment we have PRTG checking mainly the basic auto discovered sensors (cpu, memory, disks etc)
We have noticed that when PRTG is running we get denied traffic in our firewall where the destination port is in the old windows dynamic range (1024-5000) mainly on TCP, which seems to coincide with issues in the PRTG logs related to WMI fallback failing and timeouts.
What could be causing this? Does any element of PRTG use these ports directly or indirectly through calls to the OS and if so can this be configured to use the now default 49152-65535?
Add comment