Cannot Ping SQL Network Name after Failover

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi,

I have created a two node Cluster Running Windows 2003 R2 64 bit with a
32 bit SQL Server Cluster running on it, this has been service packed
up to SP4. The cluster is running on two IBM eServer x366 servers
connecting to an IBM DS4800 SAN which is home to all the shared disks.

The Problem I have is when I failover the cluster from Node1 to Node2
everything failsover ok in Cluster Administrator however I cannot see
the SQL Server Virtual Name when doing a ping from another destination,
however the Windows 2003 Cluster IP address does failover successfully.

I have followed all the recomended installation procedures for the
Public and Private networks. If anyone has any suggestions of what I
could try that would be appreciated.

Thanks

.

Relevant Pages

  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Now, for the first problem, adding the 3rd node as a member of the cluster. ... You then installed a 2nd instance of SQL Server. ... DBC01 (Disks, SQL Server resources) ... Install RTM SS2K and designate the node membership. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: active/passive with multiple instances
    ... An Active/Passive cluster is always called that and never Passive/Active. ... There is only 1 SQL Server per instance:) Just so other don't get confused. ... It does matter about the hardware, to achieve true HA it needs to happen at ... a SQL Server DBA plain and simply doesn't care about it being ...
    (microsoft.public.sqlserver.clustering)
  • Re: High Availability
    ... The cluster uses heartbeat to detect whether a node is alive or not responding. ... You may want to research SQL Server Replication/ Log Shipping if you can have some latency. ... Typical Uses of Replication ... Introducing New Features in Microsoft SQL Server 2000 Transactional Replication ...
    (microsoft.public.sqlserver.clustering)
  • Re: Bad startup parameter on clustered instance
    ... you shouldn't directly edit the registry entries of a cluster-aware ... SQL Server resource to keep failing the startup. ... This is because the cluster service checkpoints its changes and basically ... Check the registry entries for the startup parameters on the node to make ...
    (microsoft.public.sqlserver.clustering)