Sql-server – Unable to telnet to port 1433 in SQL Server clustered instance

clusteringsql serversql-server-2008

Situation: I believe that multiple port 1433 can be implemented as long as the IP address are all unique.

I’ve created SQL Server 2008 R2 SP1 clustered virtual instance on top of my Windows Server 2008 R2 SP1 Enterprise MSCS, one instance is working fine and I can perform:

C:\telnet SQLClustername-instance1 1433

successfully

However with the other instance I cannot perform the above command and it is not accessible at all ? pinging the SQLClustername-instance2 is fine and reply back, when I do the following command:

C:\netstat –ano | find /I “1433”

I cannot see the SQLClustername-instance2 IP address with port 1433 listening ?

Any assistance would be greatly appreciated.

Thanks.

Best Answer

Does the SQL Server instance installed on the cluster resource named SQLclustername-instance2 listen on port 1433? If you installed a named instance then is very likely using dynamic ports. See Configure a Server to Listen on a Specific TCP Port.

Related Solutions

Sql-server – Clients require instance name to connect to clustered instance

From further research, it appears the issue may be a result of older SQL clients performing an "InstanceValidity" check when connecting to SQL Server (specifically sqlsvr32.dll driver). The driver passes "MSSQLServer" as the instance to verify for the InstanceValidity check. In this case, since the instance name listening on the Default port (1433) is named "Instance1", the check fails because the Instance names do not match the InstanceValidity check.

Specifying the port number or instance name explicitly in the connection string works.

Sql-server – SQL Server is started but didn’t listen on any port

What made my SQL server listen for TCP connections on port 1433 was the following...

Configuration Tools / SQL Server Configuration Manager
click the instance name in SQL Server Network Configuration
enable TCP communication
Right-click the TCP communication entry, choose Properties
Click the IP addresses tab
Enable all non-VMnet IP addresses and enter 1433 in the Port entry for "IPAll".
Restart the SQL Server on SQL Server Services tab

Check your configuration with netstat -an:

C:\>netstat -an | find "1433"
  TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
  TCP    [::]:1433              [::]:0                 LISTENING

Best Answer

Related Solutions

Sql-server – Clients require instance name to connect to clustered instance

Sql-server – SQL Server is started but didn’t listen on any port

Related Question