Re: Failover problems on 2 active/active SQK 2k clusters on Windows 2003

If you don't set the port numbers with SNU, the ports change each time the
non-default instance starts up. That may be where the name resolution is
getting lost.

SQLPing.exe can help diagnose connectivity issues.
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx

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




"John Wart, jr" <johnwartjr@xxxxxxxxxxxxxx> wrote in message
news:OxUseThPGHA.648@xxxxxxxxxxxxxxxxxxxxxxx
I did not do anything in particular with the Server Network Utility, but if
I open it on the nodes in question and select the instance names, then
click TCP/IP under enabled protocols and properties, it shows the correct
ports for each instance.

Do I need to configure anything more there?

Any suggestions on how I would troubleshoot the SQL Browser?

Thanks for the suggestions!

--john

"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:%23AP9wMhPGHA.3896@xxxxxxxxxxxxxxxxxxxxxxx
Possibly a name resolution error. Did you use the Server Network Utility
to lock the port numbers for the named instances? That helps keep
consistency during failover. You may also be having a problem with the
SQL Browser, the listener service on port 1434 that resolves named
instance requests to the actual port number.

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




"John Wart, jr" <johnwartjr@xxxxxxxxxxxxxx> wrote in message
news:OYRwNxgPGHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
Greetings

I recently deployed 2 new SQL clusters for our web environments.

We have a legacy cluster that runs windows 2000 server and has
active/active clustering with 2 instances of SQL Server. It works well
and has worked well for years, but we started to outgrow the hardware,
so we acquired hardware and software to build 2 clusters to replace the
original.

Our new clusters are having a strange problem though.

In both cases, we have active/active clustering with 2 instances of SQL.
The first cluster has instance names DBSERVER1 and DBSERVER2\DBSERVER2,
and the second cluster has instance names DBSERVER3 and
DBSERVER4\DBSERVER4.

The default named instances (DBSERVER1 and DBSERVER3) work just fine on
both clusters on either Win2k3 node, fail over and work seamlessly.
However, the named instances (DBSERVER2\DBSERVER2 and
DBSERVER4\DBSERVER4) have odd problems when they fail over. SQL Server
starts up perfectly on the node, I can use enterprise manager to browse
through the tables, etc, but the web apps give an error - 'SQL Server
does not exist or access denied'.

Any ideas? I've wondered if this might have something to do with
aliases, but am not certain. My experience with SQL is somewhat limited
and I followed advice from several books when I deployed these
clusters - but it's possible something was omitted in the procedure that
was important.

Thanks!

--john











.

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: Is there any way to prevent hacker trying to guess sa password?
    ... and port 1433 will not be open. ... If someone can crash SQL Server by connecting to port 1433, ... You don't need multiple security experts. ...
    (microsoft.public.sqlserver.security)