|
Home > Archive > MS SQL Server Connectivity > December 2006 > Remote connections to named instances fails on SQL 2005 cluster
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Remote connections to named instances fails on SQL 2005 cluster
|
|
| Bill Q 2006-12-07, 7:12 pm |
| I have a new SQL Server 2005 cluster with multiple named instances of SQL
Server 2005 running. From any cluster machine, I can connect to any instance
of SQL Server running in the cluster. From remote machines, I can connect to
the default instance of SQL Server, but I can not connect to any named
instances. Help?
+ SQL Browser is running on one physical machine in the cluster
+ Surface Area Configuration has "remote clients" enabled for all instances
+ Named pipes and TCP/IP are enabled
+ DTC is running on the cluster. It is configured to allow network access
on each physical machine.
+ Windows firewall is disabled. Remote machines on same subnet as cluster
machines.
+ Client machine can ping virtual servers
| |
| Bill Q 2006-12-07, 7:12 pm |
| ???
After waiting a few hours, remote connections now work
???
"Bill Q" wrote:
> I have a new SQL Server 2005 cluster with multiple named instances of SQL
> Server 2005 running. From any cluster machine, I can connect to any instance
> of SQL Server running in the cluster. From remote machines, I can connect to
> the default instance of SQL Server, but I can not connect to any named
> instances. Help?
>
> + SQL Browser is running on one physical machine in the cluster
> + Surface Area Configuration has "remote clients" enabled for all instances
> + Named pipes and TCP/IP are enabled
> + DTC is running on the cluster. It is configured to allow network access
> on each physical machine.
> + Windows firewall is disabled. Remote machines on same subnet as cluster
> machines.
> + Client machine can ping virtual servers
|
|
|
|
|