In every version that we have of DotNetNuke (including the latest version that comes with FCK as a default), we cannot get it to work at all.  When you click on the "Rich Text Editor" radio button, you get a bunch of html code starting with:

<!--
* FCKeditor - The text editor for Internet - http://www.fckeditor.net
* Copyright (C) 2003-2008 Frederico Caldeira Knabben
*
etc.....


We do not see the toolbar or any kind of control.  Just a textbox.

I'm guessing that it's some kind of setting on IIS or Folder setting since it doesn't work on 3 separate instances of DotNetNuke, including the latest (Version 5.14).  We can get it to work on our local dev server. 

Any ideas?

This is odd. Have you tried a clean install -- just for testing?

You said the "latest version" but can you confirm that it's 5.1.x? And, since this is a universal problem for you, it would seem that something is missing. Is AJAX installed? Can you check the .NET version?

here's the rest of what's missing from my question:
In every version that we have of DotNetNuke (including the latest version that comes with FCK as a default), we cannot get it to work at all. When you click on the "Rich Text Editor" radio button, you get a bunch of html code starting with:

!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
* FCKeditor - The text editor for Internet - http://www.fckeditor.net
* Copyright (C) 2003-2008 Frederico Caldeira Knabben
*
etc.....

We do not see the toolbar or any kind of control. Just a textbox.

I'm guessing that it's some kind of setting on IIS or Folder setting since it doesn't work on 3 separate instances of DotNetNuke, including the latest (Version 5.14). We can get it to work on our local dev server.

-->
There was an unclosed comment tag and no responses could be seen. so I reopened the question here:
http://www.dnncreative.com/Forum/ta...fault.aspx

My only suggestion is that you see if the DotNetNuke team can help you. This is NOT normal behavior.

Solved it:
The IIS had a invalid setup in the host header:
there was a wildcard mime type for .* to application/octet-stream
Which means ASP.NET was trying to process your .js files, and wasn't serving them to your clients.

We removed the wildcard and it works fine.