Re: Connecting to an instance in a cluster



Each virtual server has its own IP address so you can reuse port numbers between instances. Without a cluster, you cannot reuse port numbers.

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



"Yuhong" <Yuhong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:85AC15AA-1E22-4317-B1B6-5A1BE2975B6F@xxxxxxxxxxxxxxxx
The IP for the public NIC has a port assigned for the default instance. It
won't affect the default instance if I assign it another port for other named
instances, right?

"Geoff N. Hiten" wrote:

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: SQL2005: Cannot connect error 11001
    ... The famous Windows Firewall (turned on my Server from which I'm trying to ... Exception Details: System.Data.SqlClient.SqlException: Login failed for user ... Try starting the SQL Server ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • 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: Failed connections to remote 2k SQL Server
    ... It could be a port issue - that would be my first guess. ... you need to open up UDP 1434 for SQL Server name ... TCP Ports Needed for Communication to SQL Server ... >server's network utility, and client network utility, and ensured that they ...
    (microsoft.public.sqlserver.setup)
  • Re: hack using xp_cmdshell
    ... I'm no security expert, so please forgive if I'm not using the right ... install SQL Server in Windows Only mode and then Switch down to Mixed mode, ... Is the SQL Server instance a default instance? ... > port 65300, which has never been open on my firewall. ...
    (microsoft.public.sqlserver.server)
  • Re: Failed connections to remote 2k SQL Server
    ... > It could be a port issue - that would be my first guess. ... you need to open up UDP 1434 for SQL Server name ... TCP Ports Needed for Communication to SQL Server ... >>server's network utility, and client network utility, and ensured that they ...
    (microsoft.public.sqlserver.setup)