Cannot connect to Active/Passive SQL2005 Failover Cluster via TCP/IP

I've installed a new active/passive SQL2005 failover cluster, everything *appears* to be fine, but I cannot connect to the SQL virtual server via TCP/IP.  Named pipes works fine, but I need TCP/IP.  I have run the Surface Area Configuration tool and tried both TCP/IP only and TCP/IP + Named Pipes to no avail.  Cluster fails between the two nodes without error, runs fine when connecting via named pipes.

I've successfully implemented several SQL2000 failover clusters but this is my first SQL2005.  Any help would be appreciated.

O/S is Windows 2003 Enterprise R2 SP2 x64.  SQL2005 Standard x32.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Jim P.Connect With a Mentor Commented:
To use the technical terms: It sounds like your instance is hosed.

I hate to say it, but your best bet is to de-install and then re-install the instance. I ran into similar situation where I tried to use the "-c -m -T3608" to move the master database on an instance. Once the cluster/msdtc service had it registered, the only thing I could do was re-install.

A few basic questions:

1. Can you ping the Virutal Server name from the client and does it resolve to the Virtual IP?
2. If #1 is okay, can you telnet to port 1433 on the Virutal IP/Server?
3. What  port  is the instance listenting on?
CampusHostingAuthor Commented:
Yes, I can ping the Virtual IP, and I discovered that the Virtual Server is, in fact, listening for TCP/IP connections, albeit on port 2560.  So now I need to find out how to properly modify which port its listening on.  The Virtual IP does not appear in the interfaces list in SQL Configuration Manager, and even if I change the port for IP_All, after a restart of the Virtual Server, those values have reverted back to what they were.
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

Your virtual IP doesn't show up in the IP Addresses tab in SQL Configuration Manager?  Also, are we talking about the right Virtual IP?  There will be 3 different virutal name / IP's associated with your cluster.

1. For the cluster itself.
2. For the MSDTC
3. For the SQL Serer Instance.

The third is the one you want.

CampusHostingAuthor Commented:
Yes, the SQL Virtual Instance IP,, is the IP I am referring to.  Cluster IP is .102, VIP is .103, and it is not listed in the Conf Mgr.  I did discover that the Virtual Server is listening ont he dynamic port 2560, but am not certain how to change that.
CampusHostingAuthor Commented:
One additional comment, I do not have a unique IP assigned to the MSDTC clustered instance.  When configuring that resource, specifically configuring a local storage resource, there were no drives in the droplist, so I apparently have that incorrectly configured as well.  The server has two local drives, C: and D:, and two volumes mapped via iSCSI, Q: for the Quorum and S: for the Data volume.
CampusHostingAuthor Commented:
I've tried using the method here:

To no avail.  When I bring the clustered sql instance back online it is still using dynamic port 2560.
bbaoIT ConsultantCommented:

1. is there any firewall enabled on either SQL server?
2. can you PING the SQL server's physical and virtual IPs by names (NETBIOS *and* DNS)?

Jim P.Commented:
I'm out of the office for a few days so I don't have all the normal SQL tools available and am working from memory.

In the Cluster Admin, you should have a Cluster Group which is your Q: drive and the MSDTC service and such.

Then you should have a SQL group that has a different virtual drive, the virtual IP and the SQL instance (SQL Server and SQL Agent) and such in it. You can only have one virtual instance per drive.

There is also a SQL Server Browser Service installed on each node as well. Make sure it is enabled on both.

Go into the SQL Configuration Manager and make the changes there on the active node.  There are 3 different places. Then flop to the inactive node and repeat.

If all else fails -- shut down all SQL services on both machines and manually edit it in the registry. Note that all warnings about regedit apply.


Note that sometimes iSCSI is too slow to come up to handle SQL.
CampusHostingAuthor Commented:

I do have the Cluster groups you mention, with the appropriate elements.  SQL Browser is enabled on both node's.

One odd thing, I do not see my Virtual IP in the SQL Config Manager.  I have the interface for my heartbeat connection, interface for the public connection, SQL cluster IP, system loopback, and then IPAll.

If I delete the TCP Dynamic Ports value for IPAll and enter 1433 for TCP Port, it returns back to port 2560 in the Dynamic field and <null> in the TCP Port field after I start the sql instance.

All of this is consistent across both nodes.

As I've been responding, I went back on the first node, made all the changes to 1433 (including in the registry location you specified), started the virtual instance, and <poof>, its back on 2560.

Must be something I'm still missing somewhere.


Jim P.Commented:
Sorry I couldn't have been of more assistance.  May all your days get brighter and brighter.
CampusHostingAuthor Commented:
Yes sorry, I ended up ripping everything out and reinstalling after which it is properly listening on port 1433 on the SQL Virtual IP.  Thanks for your help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.