Bind failed on TCP port 1433

  • I have assumed a SQL 2000 Enterprise Edition Clustered server with new Instances of SQL running. Both instances use port 1433.

    One instance: SQL server listening on 10.50.88.204: 1433.

    Second instance: SQL server listening on 10.50.88.216: 1433.

    Since assuming responsibility I have set up a standby server that is not clustered but has the same two instances on the server. However, both instances cannot use port 1433. Is there a way to configure them to both use port 1433 or do I need to have the sites change their client connect to use a different port for one of the instances?

  • You can't configure 2 SQL Servers runing on same box to use the same port 1433. One of them should use a static port.

    And from the client end, you have to either use the port number in the connection string or create client aliases.

    Thank You,

    Best Regards,

    SQLBuddy

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply