Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of SQL 2005 installed (i.e. no named instance). Node2 has a named instance of SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005 without problem. When I attempt to connect to node2 remotely I get an error basically stating "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)".

When I connect I am using node2\sqlb as the connection name--this should give me access to the named instance. I can however access node2\sqlb from node2 directly (locally on the server). Yes, I have made sure named pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is that I was able to make a remote connection for a short time (like two hours) and then I couldn't anymore.

I am using a Windows Vista Ultimate RTM machine with SQL 2005 management console installed locally. Any information would be greatly appreciated.

.

Relevant Pages

  • login fails when connecting to named instance from different subnet
    ... I have a default instance and a named instance of SQL ... Server 2000 on the same PC running NT server. ... the "Test Connection" button is able to connect ...
    (microsoft.public.sqlserver.security)
  • Cant connect to named instance across subnets
    ... I have a default instance and a named instance of SQL ... Server 2000 on the same PC running NT server. ... the "Test Connection" button is able to connect ...
    (microsoft.public.sqlserver.security)
  • SQL error 10060
    ... Two named instances of SQL server: ... when I create an odbc connection using the IP address of the server ... tell it is not seeing the named instance Dynamics. ...
    (microsoft.public.sqlserver.connect)
  • Re: Error Deploying Sample Cube
    ... SQL2k5 as a named instance. ... deployment servers of "localhost" which you will need to change to point ... If this is the case - you need to change the connection property in the ... > this failure may be caused by the fact that under the default settings SQL ...
    (microsoft.public.sqlserver.olap)
  • Re: Concurrent database access in SQL 2005 Mobile
    ... Please stick to having an "dummy" connection in Open State. ... SQL CE/Mobile has a background thread that flushes the changes ... they run for long hours and we have not seen memory leaks so far. ... then opens his work forms and it's in ...
    (microsoft.public.sqlserver.ce)