Thanks for the reply. I had a similar issue to you where the named pipes registry settings for the cluster causing the problems was incorrect.
Again I had to hack this to change it, however I am not sure if this was related to the original issue. I feel that because this is a SQL 2000 Cluster issue many DBAs won't be aware of these issue or possible solutions as they are running 2005/8 Clusters.
MSDN/MS aside are there any SQL 2000 Cluster troubleshooting websites out there?
Rgds.
qh