With a little help from Process monitor: https://docs.microsoft.com/en-us/sysinternals/downloads/procmon , we found that the service was trying to access “…akamaitechnologies.com” on some IP-addresses. Probably to verify CRL’s or signatures on some code. As the environment don’t have access to Internet we figured it did not get a block from the firewall but rather a drop – giving a long timeout.
So we created our own block in windows firewall.
Just open Windows Defender Firewall with Advanced Security
Create a new outbound custom rule
Block everything towards at least 184.108.40.206 and 220.127.116.11 (we blocked 18.104.22.168/16 as we can’t access it anyway)
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.