Requires Aliase Name Connect to Named Instance -- sql server clustering

Dave
3/11/2004 3:59:37 PM

I have two Windows 2000 Advanced server cluster servers
one for developement (DEV) and the other acceptance (ACC)
servers. These cluster servers are set up as
Active/Active. These servers are set up as a Primary
Process server (Node A) and Secondary Process server (Node
B). Several months ago something changed and we were
unable to register the Node B server without set up an
aliase in the Client Network Utlility using TCP/IP as the
Network Library on SQL Server client connect to this
server. We were able to connect to Node A without an
aliase from a SQL Server client connection. I have
several other SQL Servers that are set up as default name
instances that do not require an aliase to connect these
servers.

I have MDAC 2.8 SP1 with SQL Server 2000 SP3A on the
client computer.

So my MDAC version should be current enough to resolve SQL
Server named instances.

Please help me resolve this issue.

Thank You,

Dave

Steve Schofield
3/12/2004 7:29:15 AM

In my experience you have to put VirtualServerName\Instancename in SQL
Enterprise manager and connection strings for web pages. Do you have WINS
resolution at your place of work?

* ----------------------------------------- *
* Steve Schofield - MCP, CCA
* steve@adminblogs.com
*
* Microsoft MVP - ASP.NET
* http://www.adminblogs.com
* ----------------------------------------- *

[quoted text, click to view]

sql server clustering : Requires Aliase Name Connect to Named Instance