Can one instance listen on multi IP Addresses?

Hi Everybody,
Is it possible to configure one virtual SQL server named instance to listen
on multi IP Address those additional IP Addresses associate with different
virtual SQL network name?
At the result like for example: SQL Server 2005 EE installed on (Windows
2003 64 bit OS cluster server) named instance SQL-V01\test1, it listen on IP
172.11.1.10. And it also should listens on IP 172.11.1.11, virtual network
name is SQL-V02\test1 as well as IP 172.11.1.12, virtual network name is
SQL-V03\test1.
Regards!
-Chen
You can indeed add extra IPs. We do it to add a backup network into the mix,
works great.
Now for the extra network name, you can add a name but I honestly don't know
how SQL will answer on it. SQL is configured for only one.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:E8A70912-0AAD-4E78-9F5A-2E32C7802D97@.microsoft.com...
> Hi Everybody,
> Is it possible to configure one virtual SQL server named instance to
> listen
> on multi IP Address those additional IP Addresses associate with different
> virtual SQL network name?
> At the result like for example: SQL Server 2005 EE installed on (Windows
> 2003 64 bit OS cluster server) named instance SQL-V01\test1, it listen on
> IP
> 172.11.1.10. And it also should listens on IP 172.11.1.11, virtual network
> name is SQL-V02\test1 as well as IP 172.11.1.12, virtual network name is
> SQL-V03\test1.
> Regards!
> -Chen
>
|||Thanks for quick response. Can you indicate some article I can follow to add
second IP Address in one instance?
"Rodney R. Fournier [MVP]" wrote:

> You can indeed add extra IPs. We do it to add a backup network into the mix,
> works great.
> Now for the extra network name, you can add a name but I honestly don't know
> how SQL will answer on it. SQL is configured for only one.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Chen" <Chen@.discussions.microsoft.com> wrote in message
> news:E8A70912-0AAD-4E78-9F5A-2E32C7802D97@.microsoft.com...
>
>
|||Right-click add resource. IP Address. Dependencies none. Then make the
network name for SQL dependent on it, if it's mission critical to also have
this second IP online.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:A214ED7F-C0A1-4D4A-A8B2-AB2FEFCFA6F3@.microsoft.com...[vbcol=seagreen]
> Thanks for quick response. Can you indicate some article I can follow to
> add
> second IP Address in one instance?
> "Rodney R. Fournier [MVP]" wrote:
|||It is much easier to set a network name at the DNS level rather than the
machine lever. Use a SRV record type in DNS to map a network name to an
IPaddress/port number combination.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:e9Kpm6V7GHA.4288@.TK2MSFTNGP02.phx.gbl...
> Right-click add resource. IP Address. Dependencies none. Then make the
> network name for SQL dependent on it, if it's mission critical to also
> have this second IP online.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Chen" <Chen@.discussions.microsoft.com> wrote in message
> news:A214ED7F-C0A1-4D4A-A8B2-AB2FEFCFA6F3@.microsoft.com...
>
|||Agreed! And not cause I know better then to ever disagree with you on SQL
matters
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23GVaS5W7GHA.728@.TK2MSFTNGP04.phx.gbl...
> It is much easier to set a network name at the DNS level rather than the
> machine lever. Use a SRV record type in DNS to map a network name to an
> IPaddress/port number combination.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:e9Kpm6V7GHA.4288@.TK2MSFTNGP02.phx.gbl...
>

Can not remote connect

I am presented with...
TITLE: Connect to Server
Cannot connect to LARRYTESTBOX\SQLEXPRESS.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLS erver&EvtID=-1&LinkId=20476[/url]
BUTTONS:
OK
I installed SQLExpress on a Windows 2000 Pro machine. It is configured Mix
Mode. I have it's browser running. It is visible from my computer under
Network Servers. I attempt to log on as sa.
Strangely, I did exactly the same last week for a client. The only
difference was that the machine was XP Pro SP-2. Should that make a
difference? I have DotNet 3.0 installed. What else shoudl I check?
TIA
Check the firewall settings and my blog for a checklist on getting
connected.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Larry Killen" <lkillen@.charter.net> wrote in message
news:tii9i.626$3j6.282@.newsfe03.lga...
>I am presented with...
> TITLE: Connect to Server
> --
> Cannot connect to LARRYTESTBOX\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (Microsoft SQL Server, Error: -1)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLS erver&EvtID=-1&LinkId=20476[/url]
> --
> BUTTONS:
> OK
> --
> I installed SQLExpress on a Windows 2000 Pro machine. It is configured
> Mix Mode. I have it's browser running. It is visible from my computer
> under Network Servers. I attempt to log on as sa.
> Strangely, I did exactly the same last week for a client. The only
> difference was that the machine was XP Pro SP-2. Should that make a
> difference? I have DotNet 3.0 installed. What else shoudl I check?
> TIA
>

Can not remote connect

I am presented with...
TITLE: Connect to Server
--
Cannot connect to LARRYTESTBOX\SQLEXPRESS.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
BUTTONS:
OK
--
I installed SQLExpress on a Windows 2000 Pro machine. It is configured Mix
Mode. I have it's browser running. It is visible from my computer under
Network Servers. I attempt to log on as sa.
Strangely, I did exactly the same last week for a client. The only
difference was that the machine was XP Pro SP-2. Should that make a
difference? I have DotNet 3.0 installed. What else shoudl I check?
TIACheck the firewall settings and my blog for a checklist on getting
connected.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Larry Killen" <lkillen@.charter.net> wrote in message
news:tii9i.626$3j6.282@.newsfe03.lga...
>I am presented with...
> TITLE: Connect to Server
> --
> Cannot connect to LARRYTESTBOX\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I installed SQLExpress on a Windows 2000 Pro machine. It is configured
> Mix Mode. I have it's browser running. It is visible from my computer
> under Network Servers. I attempt to log on as sa.
> Strangely, I did exactly the same last week for a client. The only
> difference was that the machine was XP Pro SP-2. Should that make a
> difference? I have DotNet 3.0 installed. What else shoudl I check?
> TIA
>