Have just encountered a nice feature where full text indexing on a SQL 2000 cluster had different results dependant on which node SQL was running on. Primarily the noise words that the fulltext process used was different.
Did the google hunt and found http://support.microsoft.com/default.aspx?scid=kb;en-us;889708.
Which indicates that the location SQL full text tries to find the noise file is stored in the registry. However the key is only stored on the node that full text was installed on to and is not copied over when resources move. Oh dear.
So the work around is to manually copy the registry key. We found that on the node that didn't have the key, full text seemed to just to a search of the hard drive and used the first noise file it could find. In our case in an $uninstall$ directory.