It enables you to automatically convert the downloaded Flash video (.flv) to some of the popular video formats – .avi, .mpg, .mp4, .wmv, etc.

It comes also with a built-in (as an option) torrent downloader.

With SharePoint 3 the story is a bit different. When you create a site with host header through SharePoint Central Administration, that site is bound to the host header you created it with. This might cause problems with intranets (for example internal domain is one and external is other). Below is one solution (that I confess, I still have to try out) that might solve this problem:

Modifying ports and host headers on SharePoint

I also use the following trick: When the site is created, I go to the IIS administration console and add the desired host headers. Usually this will redirect to the original host header. Example: site is created with www.piflar.com, I’ve added also host header piflar.com. So when I visit http://piflar.com it automatically redirects to www.piflar.com.

The problem might occur with intranet sites. Internal domain can be http://companyweb2 and external http://intranet.company.com:444. If you visit the second url and redirects you to companyweb2 naturally you won’t be able to open the site.  

The solution can be that you add the default.aspx after the url. So if you visit http://intranet.company.com:444/default.aspx you won’t get redirected and you can see the SharePoint.

The reason for this is that SharePoint lost the connection to the database.

Reasons may be the following:

• SQL or WMSDE database may not be running

• IIS may be running in IIS 5.0 isolation mode
• The account for connecting to SQL or WMSDE might be gone or with changed password
• update – SQL Server Embedded Edition might not be running (check services) – Thanks, deanoc (see the comments)

The solution to these is on the following link:

http://support.microsoft.com/kb/823287/en-us

But I’ve found another reason that could be. Simple: The SQL is running, credentials are also ok and IIS isn’t in the 5.0 isolation mode. The problem may occur if sharepoint simply can’t find the database. Reasons for this may be many: the database has moved, dns has changed, … In my case was the later. By changing the DNS server in the network we’ve had to add one more record manually to point to the correct one and the sites started to work.