Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / July 2008

Tip: Looking for answers? Try searching our database.

Remote connections on Clustered instance

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
TKE402 - 10 Jul 2008 22:34 GMT
Hello,

Here's the environment:

SQL2005; 2 nodes; Active/Passive; Named Instance

I used SQL Server SAC to connect to the Virtual server. I noticed that
remote connections is already enabled and the option "Local connections only"
is greyed out. However, I am receiving errors from various tests that say
remote connections is not enabled.

So for giggles I conencted Sql Server SAC to the localhost but I receive an
error saying that I'm on a clustered server and I have to connect to the
virutal server name instead.  

How to I confirm that remote connections is really enabled? If there T-Sql
that I can use instead of through the GUI?

Thanks

TKE402
Denny Cherry - 11 Jul 2008 01:24 GMT
remote connections is always enabled on a clustered install.  The
Windows firewall, or other filewall on the node(s) could be blocking
access to the SQL Server port.

>Hello,
>
[quoted text clipped - 17 lines]
>
>TKE402
TKE402 - 11 Jul 2008 14:47 GMT
Thanks for the response.

I have verified that there is no firewall on the clients as well as the
servers. They are also on the same physical network segment.

> remote connections is always enabled on a clustered install.  The
> Windows firewall, or other filewall on the node(s) could be blocking
[quoted text clipped - 21 lines]
> >
> >TKE402
Denny Cherry - 11 Jul 2008 21:20 GMT
Try logging onto the physical node and try to telnet to the SQL port.
If that works try from the other node.  Id that works try from another
machine outside the cluster.

Have you started the SQL Browser on both nodes?  Are you using a
static port or a dynamic port?  Are you connecting to the name of the
virtual world that you entered during SQL Server setup or another
name?

I would have asked these earlier, but it didn't click that you were
using a named instance.

Denny

>Thanks for the response.
>
[quoted text clipped - 26 lines]
>> >
>> >TKE402

Denny Cherry
Senior DBA / Architect
MCSA, MCDBA, MCTS, MCITP
TKE402 - 11 Jul 2008 22:03 GMT
I tried telnetting to the node name and it did not connect. I tried
telnetting to the virtual cluster name and that worked from both the cluster
node and a seperate machine.

SQL browser is turned on on all nodes

Using default ports

Just to clarify in case I'm describing wrong. The nodes are named
server1,server2 and the virtual cluster name is servernew. Does that mean
it's a named instance?

> Try logging onto the physical node and try to telnet to the SQL port.
> If that works try from the other node.  Id that works try from another
[quoted text clipped - 44 lines]
> Senior DBA / Architect
> MCSA, MCDBA, MCTS, MCITP
Uri Dimant - 13 Jul 2008 08:05 GMT
Hi
> How to I confirm that remote connections is really enabled? If there T-Sql
> that I can use instead of through the GUI?

Value =1 means it is enabled

select * from

sys.configurations

where name like '%remote%'

> Hello,
>
[quoted text clipped - 19 lines]
>
> TKE402
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.