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

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?

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.

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.

Yes, the SQL Virtual Instance IP, 10.26.100.103, 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.

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.

I've tried using the method here:

http://www.sqlserverfaq.net/2008/05/17/how-to-change-the-dynamic-port-of-the-sql-server-named-instance-to-the-static-port-in-a-sql-server-2005-clustered-instance/

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

umm....

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)?

regards,
bbao

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.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI10.0\tcp\Property1

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

Jimpen,

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.

Thanks

Sorry I couldn't have been of more assistance.  May all your days get brighter and brighter.

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.