Post reply

Named instance connectivity issues

  • February 23, 2015 at 3:03 pm

    #298033

    - SQL Server 2012 (SP1) Express Edition 64-bit is installed on MYSERVER.

    - This is a named instance \SQLEXPRESS.

    - Is only Sql install on MYSERVER.

    - Listening on port 1433

    Remotely I can connect to MYSERVER in SSMS ok. I select @@servername and it returns MYSERVER\SQLEXPRESS

    I canNOT connect to the specific named instance using SSMS remotely, MYSERVER\SQLEXPRESS. Cannot find Sql error

    Sql is listening on port 1433, TCP enabled, Named Pipes is enabled. SQL Browser service is running.

    1433 opened in firewall between remote workstation and server, hence successful remote connection to just servername MYSERVER.

    Why can I not connect to instance? Need to configure as subscriber, repl tool erroring because of this problem.

    Any help much appreciated.

    Regards,

    Chris B

    Chris Becker bcsdata.net

  • February 24, 2015 at 9:40 am

    #1779643

    you actually configured it to listen on 1433?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • February 24, 2015 at 9:48 am

    #1779651

    since this is an instance, and you already conencted to a default instance on port 1433, i doubt very much the named instance is listenting on 1433 like you think.

    connect to it locally, and run this command:

    select local_tcp_port from sys.dm_exec_connections where session_id = @@spid

    select port, is_dynamic_port from sys.tcp_endpoints where is_admin_endpoint = 0

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • February 24, 2015 at 12:01 pm

    #1779695

    Thank you. Query returns:

    local_tcp_port

    1433

    port is_dynamic_port

    0 1

    It is the local firewall on db server. We turn fw off, remote connect by instance name ok. Turn it back on, failure. We have allowed 1433 & 1434

    Chris Becker bcsdata.net

  • February 24, 2015 at 12:09 pm

    #1779701

    Additional info - it looks like SQL2008 was installed at one time because tools are still available. I presume it was the default instance.

    Server admins installed named 2012 instance, probably removed 2008 default instance, and hard coded the 1433 port for SQLEXPRESS.

    This is an external facing db server, communication from intermal network protected with firewall. Shall we change SQLEXPRESS to be truly dynamic, and allow 1434 in fw? And if port dynamic, how do we config firewall if port changing?

    Thanks again

    Chris Becker bcsdata.net

Viewing 5 posts - 1 through 4 (of 4 total)

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