Re: Connecting to an instance in a cluster

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: 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)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)