Post reply

Named instance running on port 1433

  • January 21, 2009 at 3:47 am

    #126783

    On our dev/dr box we have a SQL Server 2005 setup where by the development default instance runs on port 1433. If/when we have to invoke DR, the idea would be to shut down the default instance and start up a named instance configured to run on port 1433.

    This is causing us a problem as when our applications try to connect to this named instance on port 1433, we keep getting connection timeouts. If we use dynamic port allocation for this named instance, it seems to work fine, if we use static port 1533 it seems to work fine.

    Does this mean that we cannot have a named instance running on port 1433? Any help would be appreciated.

    thanks

    Parag

  • January 27, 2009 at 1:57 am

    #933047

    Parag Patwa (1/21/2009)

    On our dev/dr box we have a SQL Server 2005 setup where by the development default instance runs on port 1433. If/when we have to invoke DR, the idea would be to shut down the default instance and start up a named instance configured to run on port 1433.

    This is causing us a problem as when our applications try to connect to this named instance on port 1433, we keep getting connection timeouts. If we use dynamic port allocation for this named instance, it seems to work fine, if we use static port 1533 it seems to work fine.

    Does this mean that we cannot have a named instance running on port 1433? Any help would be appreciated.

    thanks

    Parag

    anybody have any ideas..

  • January 28, 2009 at 8:38 am

    #933870

    We are currently using servers with multiple instance installed in which all are using the same port number (not default port number) and we are not having any issues. Could you tell me if you are shutting down the SQL Browser service when you shut down the default instance? Of so, it need to be running for accessing the other instances. Also, you could leave the DR instance on the same port number as your production servers and change the development instance to a different port number (just don't forget to tell your developer of the port number change). Now if the DR is invoked, the DR instance will have the same settings as production.

    Hope this helps.

    Rudy

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

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