Re: Connecting to an instance in a cluster

OK. Go into the cluster admin tool and find the IP address for the public NICs. That is the port you have to open on the firewall. You have to add 1434 if you want to resolve SQL Instances by name instead of just IP address and port number. Note that traffic may appear to the firewall as originating from the underlying physical NIC address, not the virtual address of the SQL instance.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"Yuhong" <Yuhong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:975E3D7D-BB1B-472B-B102-D3A50024CDC1@xxxxxxxxxxxxxxxx
The public IP for that SQL Instance is not listed. I must have missed
something. I am in SQL Server Configuration Manager, SQL Server 2005 Network
Configuration, Protocols for Instance1, and TCP/IP Properties-IP Addresses
window. It has the IP of the SQL Virtual Server I installed before it, but
not the IP for this instance and the instance which I installed afterwards.
Thanks!

"Geoff N. Hiten" wrote:

The only IP you need to fix is the Public IP for the SQL Instance.

GNH


"Yuhong" <Yuhong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:136D4B36-754C-4ACC-B995-9829A4616B8F@xxxxxxxxxxxxxxxx
> Hi Geoff,
> Thanks for your information. There are many IPs in the TCP/IP > properties
> window in SQL Server Configuration Manager. Which one should I use? > Should
> I
> do the lookback adapter IP or do them all? Sorry I am really confused
> about
> this part. The online help is not very clear about this. Thanks again!
>
> "Geoff N. Hiten" wrote:
>
>> You will need to use the SQL Server Configuration Manager to set a >> static
>> port for each named instance. You only need to set it once or each
>> instance on the cluster. You cannot use port 1434 or 1433. Then you
>> open
>> the firewall for those ports. Note that you will have to restart each
>> SQL
>> instance after setting the ports so SQL can bind correctly.
>>
>> -- >> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>>
>>
>> "Yuhong" <Yuhong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:54E0E94E-FAD2-4EDE-86A3-5D63C4E6E5E4@xxxxxxxxxxxxxxxx
>> > Browser Service is running on all nodes. Dynamic ports are used by
>> > default
>> > and I did not change it. The servers are behind a firewall. I opened
>> > port
>> > 1434. And port 1433 is open too. I can connect to the default >> > instance
>> > fine
>> > remotely and can connect any instances locally.
>> >
>> > "Anthony Thomas" wrote:
>> >
>> >> Did you configure static or dynamic ports? Is the Browser service
>> >> running
>> >> on all cluster nodes?
>> >>
>> >>
>> >> Anthony Thomas
>> >>
>> >>
>> >> -- >> >>
>> >> "Yuhong" <Yuhong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:05184BB4-026E-4FBF-AD14-8684B121A86F@xxxxxxxxxxxxxxxx
>> >> > Yes.
>> >> >
>> >> > "Hilary Cotter" wrote:
>> >> >
>> >> > > is the virtual server enabled for remote connections?
>> >> > >
>> >> > > -- >> >> > > Hilary Cotter
>> >> > >
>> >> > > Looking for a SQL Server replication book?
>> >> > > http://www.nwsu.com/0974973602.html
>> >> > >
>> >> > > Looking for a FAQ on Indexing Services/SQL FTS
>> >> > > http://www.indexserverfaq.com
>> >> > >
>> >> > >
>> >> > >
>> >> > > "Yuhong" <Yuhong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> > > news:065C8B43-891D-41CC-8602-04FB551CFE34@xxxxxxxxxxxxxxxx
>> >> > > > Hello, I just setup a few instances on a cluster. But somehow >> >> > > > I
>> >> > > > cannot
>> >> > > > conntect to the instances remotely using SQL Server >> >> > > > Management
>> >> > > > Studio.
>> >> I
>> >> > > > can
>> >> > > > connect to them locally. I can also connect to the default
>> >> > > > instance
>> >> fine.
>> >> > > > Any
>> >> > > > idea?
>> >> > > > Thanks!
>> >> > >
>> >> > >
>> >> > >
>> >>
>> >>
>> >>
>>
>>



.

Relevant Pages

  • Re: Connecting to an instance in a cluster
    ... "Geoff N. Hiten" wrote: ... you cannot reuse port numbers. ... Microsoft SQL Server MVP ... That is the port you have to open on the firewall. ...
    (microsoft.public.sqlserver.clustering)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... Queries to the Data Engine must go to the port that SQL Server is ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2008 remote connection problem
    ... Hitchhiker’s Guide to Visual Studio and SQL Server ... default instance of the SQL Server Database Engine listens on TCP port 1433", ... > I was trying to establish a remote connection to SQL Server 2008 from ... The server is running the XP firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server connection problem
    ... no firewall is installed? ... Also i have check that port 1433 is not ... Will SQL server only connect to this ... > to configure the firewall to permit connections to SQL Server. ...
    (comp.databases.ms-sqlserver)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)