Re: Connecting to cluster instance from .NET

You need to separate out which are the NIC addresses, and which are the
Virtual IP addresses for the cluster resource groups.

The reason why this worked for the Stand-Alone installation is because by
default, SQL Server will listen on all available IP addresses, including the
localhost 127.0.0.1 loopback address. However, this is not the case for
clustered installation. SQL Server will listen on only those IP addresses
where cluster resources have been generated in the dedicated SQL Server
cluster resource group. This can only be done through the SQL Server setup
program.

Each node should have at least two NIC cards, and perhaps a third or a
fourth if you use dual-homing and/or dedicated management networks.

Regardless, each node will have a minimum of two networks: one public, and
one private.

Then, in a minimal cluster configuration, you will have 3 dedicated virtual
IP addresses for each of the following cluster resource groups: Cluster
Quorum (the cluster group), MS DTC, and SQL Server. These IPs will be in
the same subnet as the public facing cluster node IP addresses.

Based on your information, each node has 3 NIC cards. The 192.168.0.0
network is for LAN, 10.0.0.0 is for WAN/VPN, and 172.16.0.0 is for the
cluster heartbeat. This is odd because the 172.16 network is a Class B
network (which means it has more available addresses); whereas, your LAN is
based on only a Class C 192.168 network.

Regardless, if you want each of the virtual servers to be addressable to
both LAN and WAN clients, then you will need to add the additional IP
address resources to the various cluster groups.

In the Cluster Quorum Group and the MS DTC Group, you can manually add
additional IP Addresses. Each should have 2, one for the 192.168.0.0 and
one for the 10.0.0.0 subnets.

For SQL Server however, you will need to rerun the setup program. Under the
Advanced Installation Option, under Maintain an existing Cluster, you can
navigate to the cluster IP address screen and verify that two dedicated IP
addresses have been defined, again, one each for each subnet: 192.168.0.0
and 10.0.0.0, respectively. There should be no references to the 172.16.0.0
subnet anywhere in Cluster Administrator except for the detected networks
where this subnet has been designated for Heartbeat communications only.

One or both public subnets should be defined for Both Public and Internal
Communications, but the dedicate Heartbeat should be given Network Priority
in the main Cluster properties dialog.

Hope this helps.

Sincerely,


Anthony Thomas


--

"Gareth" <Gareth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9A831138-7E25-4370-9FEA-3C57B58CBA81@xxxxxxxxxxxxxxxx
Hi Tom

Thanks for the responce, yes i am sure that the 10.0.0.13 is the correct
IP
address.
The cluster IP address is 192.168.0.96.

We have a strange config. let me give you a little more info.

Our network in coventry is running on the 192.168.0.0 addressing, our SQL
servers have 3 cards, the 192.168 address is for LAN communictions, the
172.16.0.0 addresses are the private ones, and the 10.0.0.0 addresses are
used to communitcate via a VPN to our Webservers located in London.

I have obtained the PortqryUI utility from MS and have run this against
this
server and i have the following results

192.168.0.98 SQL LISTENING
10.0.0.13 SQL NOT LISTENING

also, as this server is replacing a single SQL 2000 server that we are
trying to decommision we have the same setup on another server. this
server
is not in a cluster but when checking the ports i get the following

192.168.0.x SQL LISTENING
10.0.0.x SQL LISTENING

does this make any more sense to you? is there a way that i can get SQL
to
see the 10.0.0.0 ip range.




"Tom Moreau" wrote:

Are you absolutely sure that you're connecting on 10.0.0.13? Typically,
that IP is used for the private heartbeat network between the 2 (or
more)
nodes in the cluster. Go into Cluster Admin and check which NICs are on
the
public network and which are on the private network.

Which IP's are in the SQL Server group? It's those IP's that you should
be
using for public access. They would be on the same network as the
public
NICs.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Gareth" <Gareth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2D46FD1E-FF02-4198-85E5-9408652BFA1B@xxxxxxxxxxxxxxxx
Hi

I think i have come accross the issue in hand. The server that we are
trying to connect to is in a cluster, that is not the issue. The issue
is
that the server has 3 network cards.
NIC one - 10.0.0.13
NIC two - 192.168.0.98
NIC three - 172.16.0.42

SQL is currecntly listening on NIC two 192.168.0.98 but we are
connecting on
the other network card which is on the 10.0.0.13 range. How, within SQL
can
i change which NIC SQL is associted with?

can someone shed some light on this one for me

thanks

Gareth Collins

"Gareth" wrote:

Hello

I am working on this issue with Edwaldo

The problem comes when i try and add the SQL instance within the
Enterprise
Manager or even if i try to TELNET to the server.
Any ideas? I have been thinking that this is something to do with the
way
that the one to one NAT is configured on the firewall. As it is set
for a
value of one at the Coventry end and the start ip address is 10.0.0.10
(which
is the old server and is working) So in the firewall rules they are
showing
as being outside the NAT pool.

The issue i have is that changing the NAT pool size with alter the
external
IP addresses of other servers which i can not really do. I can make
the
change for a couple of seconds and test but then need to change it
back.

Any help is greatfully received

Thanks for this

Gareth Collins

"Anthony Thomas" wrote:

Can you TELNET to the assigned service port? Say, for example, that
SQL
Server is listening on TCP 1433. Then if you TELNET <ip address or
server
name> <port number>, you should get a black screen, which means it
successfully connected. If it can't find the server or port, then
you
have
a server configuration issue. If you connect successfully, then you
have a
client configuration issue.

Sincerely,


Anthony Thomas


--

"edwaldo" <edwaldo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@xxxxxxxxxxxxxxxx
Thanks for your help - I'll take a look at that article.

I'm getting the message 'SQL Server does not exist or access is
denied" in
my .NET app. Not sure if it's the server or the database that I
can't
connect to, I can ping the server but that's it. Is there a
simple
way to
test database connectivity to the instance from my web server?

Thanks again.



"Linchi Shea" wrote:

And take a look at http://support.microsoft.com/kb/328306.
Connecting to
a
clustered instance is not that different from connecting to a
standalone
instance.

By the way, when you said "it can't find it", what was it, the
server or
the
database?

Linchi

"edwaldo" wrote:

Hi

Apologies if this isn't the right forum.

I have an instance of sql (2005) setup called SQL1\SQL1

I am trying to connect to a database (hm1) using the following
connection
string in my web.config:

server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;

..but it can't find it. I need to know if this is the correct
way
to
address an instance in the connection string - I've tried

server=10.0.0.8\SQL1;

and

server=10.0.0.8;database=SQL1\hm1;

But neither work. On the SQL server itself, apart from naming
the
instance,
are there any other configuration settings I might be missing?
(Unfortunately
I didn't set the server up and I know next to nothing about
SQL
clustering)

I feel like this a bit of a dumb question but any help really
appreciated.

Ed







.

Relevant Pages

  • Re: Differences in clustered system dbs vs standalone system dbs
    ... rely on the SQL Server name, not the cluster or server name. ... >> - Stop SQL on the standalone server ...
    (microsoft.public.sqlserver.clustering)
  • Re: Request for information
    ... The under dog is DISK IOPS!! ... So It is not only the hardware and software a cluster design / infrastructure design is more the a pile of boxes but use x64 where you can! ... How to cluster Microsoft SQL Server 2005 by using Microsoft Virtual Server ...
    (microsoft.public.windows.server.clustering)
  • Re: Request for information
    ... Two node Cluster for your mail and SQL. ... The under dog is DISK IOPS!! ... How to cluster Microsoft SQL Server 2005 by using ... Microsoft Virtual Server ...
    (microsoft.public.windows.server.clustering)
  • Re: upgrading sql2k cluster to sql2005
    ... It ain't that simple for SQL Server. ... that databases get locked off in the current cluster and then properly ...
    (microsoft.public.sqlserver.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine ... member of the NLB cluster, setup NLB on it, plug the NICs ...
    (microsoft.public.windows.server.clustering)