Geoff, thanks again for your attention.

I'm using Windows 2000 Advanced on both servers, SQL 2000 Enterprise
edition also.
The client is SQL 2000 client.

This is the only installation of SQL in the cluster, so it is the
default.

I can PING everything across domains, that being the machines, the
cluster, and SQL cluster.

The name of the individual servers is Jupiter1 and Jupiter 2, the
Virtual Clustered system is ATNCLUSTER, the name of the Virtual SQL
Cluster Server is SQLCLUSTER, and that's the name I'm trying to register
on a Client. (like I said, works fine within it's own domain and a SQL
2000 client, but not from a different domain, even though I can ping and
see it on Network Places...)



Thanks again,



Ivan

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Can you register the SQL server from within the domain?

Update MDAC on the client. Earlier versions cannot understand clusters or
named instances.

Try setting up an alias pointing to the IP address of the virtual server and
specifying the port number of the SQL instance.

If this doesn't work, try reposting the question. I am about to leave for
the holiday weekend.

--
Geoff N. Hiten
Senior Database Administrator
Careerbuilder.com



Try setting an alias using Client Network Utility
"Ivan Gastaldo" <anonymous (AT) devdex (DOT) com> wrote

What is the security model is set on the cluster and under what security
context are you attemting to connect?

"Ivan Gastaldo" <anonymous (AT) devdex (DOT) com> wrote