Working on maintaining a substantial set of SQL Server Integration Services 2008 R2 packages, I\'ve run into an oddball problem.
These packages make frequent use of
Yes, your guess is correct and this is a (fairly) well-known issue. The .NET runtime contacts crl.microsoft.com to check for revoked certificates; if your machine has no internet access then the runtime waits until the connection attempt times out, which can result in SSIS packages starting very slowly, Visual Studio apparently locking up etc.
Common fixes are to allow internet access to crl.microsoft.com only, or to use the local HOSTS file to redirect the name to 127.0.0.1.