I have had a problem recently where there was a customer intranet which did not have access to the Internet.  This Intranet would takes up to 5 minutes to start up of a morning and then would "freeze" for up to 2 minutes during the day.

 

The Intranet was based on MOSS 2007 with Windows 2003 R2 as the operating system.  The installation of MOSS 2007 was as described in Technet.

 

Eventually it was found that various dlls were trying to access the certificate revocation List (CRL) at microsoft.com.  The Technet instructions say that you should install .NET 3.0 Framework as a pre-requisite to installing WSS 3.0 and MOSS 2007.

 

Unfortunately .NET 3.0 does not include .NET 2.0 (but .NET 3.5 does !)  There is a fix for the problem of dlls trying to access the CRL at Microsoft.com when being used within an environment which does not have access to the Internet which was part of .NET 2.0 SP1. As we had installed .NET 3.0 (as per Technet instructions) which did not include .NET 2.0, this is why we had the performance problem.

 

So the moral of this story is that you should install .NET 3.5 as a pre-requisite of WSS 3.0 and MOSS 2007 not .NET 3.0