Hi rmizzar!

It might be caused by what protocols that are used. I would try to first set the language to tcp/ip and if that does not work, to named pipes.

If you are logged in on the server when you do this, use the Client Network Utility and go to Aliases tab. Type in the servername and let use i.e. TCP/IP as protocol. Try to register the server, if not, go back and change to Named Pipes. Remeber that you have to do this on the server itself. You have Client Network Utitlty if you have the same problem on your workstation.

I have this problem between some of my servers, and I have not figured out why it behaves like this, but it does and the error I get is the same as your.

Good luck.