Thanks for the response.
I have verified that there is no firewall on the clients as well as the
servers. They are also on the same physical network segment.
> remote connections is always enabled on a clustered install. The
> Windows firewall, or other filewall on the node(s) could be blocking
[quoted text clipped - 21 lines]
> >
> >TKE402
Try logging onto the physical node and try to telnet to the SQL port.
If that works try from the other node. Id that works try from another
machine outside the cluster.
Have you started the SQL Browser on both nodes? Are you using a
static port or a dynamic port? Are you connecting to the name of the
virtual world that you entered during SQL Server setup or another
name?
I would have asked these earlier, but it didn't click that you were
using a named instance.
Denny
>Thanks for the response.
>
[quoted text clipped - 26 lines]
>> >
>> >TKE402
Denny Cherry
Senior DBA / Architect
MCSA, MCDBA, MCTS, MCITP
TKE402 - 11 Jul 2008 22:03 GMT
I tried telnetting to the node name and it did not connect. I tried
telnetting to the virtual cluster name and that worked from both the cluster
node and a seperate machine.
SQL browser is turned on on all nodes
Using default ports
Just to clarify in case I'm describing wrong. The nodes are named
server1,server2 and the virtual cluster name is servernew. Does that mean
it's a named instance?
> Try logging onto the physical node and try to telnet to the SQL port.
> If that works try from the other node. Id that works try from another
[quoted text clipped - 44 lines]
> Senior DBA / Architect
> MCSA, MCDBA, MCTS, MCITP