SQL Server Performance Forum – Threads Archive

Cannot contact clustered SQL via tcp/ip

We have an active / passive SQL2k cluster on Windows 2000.
Both named pipes and tcp/ip protocols are enabled, but we cannot connect from another machine via tcp/ip. (I ultimately need to connect through a firewall)
If the client is configured to use on tcp/ip the connection fails.
I have tried removing tcp/ip and re-adding it to the server, but no luck.
This only affects our clustered sql, no clustered are ok. Anyone know what the problem is? Thanks.
Phil

What was the error message? And check whether TCP/IP port is used by another application as mentioned in this KBAhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;293107 for information.
And also check Virtual SQL Server IP address for correct connection. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Thanks for replying.
When trying to connect via Enterprise Manager the error is usually
"SQL server does not exist or access denied"
I cannot telnet to 1433 like I can on several other SQL 2k servers here.
I’m not sure what you mean when you say
"And also check Virtual SQL Server IP address for correct connection."
but the IP I am using is correct, and belongs to the clustered virtual instance. Phil

A little more info that might help.
I have obtained and run PortQry, (PortQry -n virtualname -e 1433) this states that port 1433 is NOT listening on this server.

Check this KBAhttp://support.microsoft.com/?kbid=328306 for the potential causes of SQL Server does not exists error. And findout which port is assigned for SQL server to listen from error log. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Are you sure it’s using port 1433? Can you telnet to 1433 locally from the server running the sql instance?

It would appear that my problem is solved, thanks to satya I have spoken to Microsoft PSS and it appear that the value in HKLMSOFTWAREMicrosoftMSSQLServerClusterClusterIpAddr was incorrectly pointing at the wrong IP address. Although this appears to have had no other side effects! [<img src=’/community/emoticons/emotion-2.gif’ alt=’

‘ />] Thanks, Phil

]]>