We had to evict, rebuild, and readd a cluster node to a windows 2003 x64 enterprise cluster running sql 2005 enterprise edition. when attempting failover to the new node we get the below error messages in the application event logs. SQL Browser *is* running which is the solution I have seen on any similar error posted on forums and blogs. unable to validate if allowing remote connections is enabled or not as we cannot get SAC to connect to the virtual name. only assuming it is since no changes have taken place when it was working previously in regards to the instances, only that the node was rebuilt. any assistance would be appreciated.
00001994.00001334::2012/08/01-18:25:23.421 ERR SQL Server <SQL Server (TT)>: [sqsrvres] ODBC sqldriverconnect failed
00001994.00001334::2012/08/01-18:25:23.421 ERR SQL Server <SQL Server (TT)>: [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
00001994.00001334::2012/08/01-18:25:23.421 ERR SQL Server <SQL Server (TT)>: [sqsrvres] ODBC sqldriverconnect failed
00001994.00001334::2012/08/01-18:25:23.421 ERR SQL Server <SQL Server (TT)>: [sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Login timeout expired
00001994.00001334::2012/08/01-18:25:23.421 ERR SQL Server <SQL Server (TT)>: [sqsrvres] ODBC sqldriverconnect failed
00001994.00001334::2012/08/01-18:25:23.421 ERR SQL Server <SQL Server (TT)>: [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]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.