TFTP Server failed to start – solved

Seashore

Symptoms

Running an upgrade from NPM and NCM 2019.4 to 2020.2.1 with offline installer.

We failed on the TFTP server install and saw that the server after a long timeout just didn’t want to start. Tried to extend the “service pipe timeout” according to https://thwack.solarwinds.com/t5/TFTP-Server-Discussions/TFTP-Server-software-install-problem/m-p/267164 but that didn’t help.

Diagnosis

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.

Solution

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 93.184.220.29 and 93.184.221.240 (we blocked 93.184.0.0/16 as we can’t access it anyway)

Rerun the installation and all should be fine!

twomonkeysayoyo

This worked for me but support may have a better workaround regarding changing a line in a .NET config file.

Before installation:

c:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config

Change the line

<runtime />

To:

<runtime>

   <generatePublisherEvidence enabled="false"/>

</runtime>