Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kp4hf
Starting Member
1 Post |
 Posted - 2011-08-04 : 10:57:05
|
| Hi.My config - 2 Windows 2008 R2 Sp1 and SQL 2005 SP4 running cluster in 2 nodes. ESX virtual servers in different servers. Both are in the same subnet 10.x.x.x.When node 1 is up all services and connections are working. When I failed to node #2 all services come online but I can't connect to the database from the client. I can ping and resolve the connection and can login fine with management studio from any server.One thing I notice is if I change the client ODBC configuration on the named pipes when node 2 is up to "\\sqlservername\pipe\sql\query" then I can connect. I've check the configuration manager in node2 and it is set to "\\.\pipe\$$\sqlservername\sql\query" like node1 is.I am having the same problem with SQL2008 in another configuration with 2 other servers.I've looked everywhere and can't fins a solution. Any ideas will be very helpful.Thank you. |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2011-09-09 : 14:51:09
|
| do you use dynamic tcp port for the sql server or set it as default?did you check your firewall for the tcp port?what is the exact connection error message you get?--------------------keeping it simple... |
 |
|
|
|
|
|
Cannot connect failover server