Swapping ports between 2 instances - can't understand results

  • Have 2 instances on the same TestServer

    1. Default 2014 Dev edition on port 1433

    2. Named 2019 Express instance "SQLExpress2019" on port 15191

    SQLBrowser is working. TCP=1433 port is open on this TestServer.

    I swapped ports between the 2 instances  and restarted the services.

    Can't tell if UDP 1434 is open..

    UDP port 1434 (ms-sql-m service): LISTENING or FILTERED
    Sending SQL Server query to UDP port 1434...
    UDP port 1434 (ms-sql-m service): FILTERED
    portqry.exe -n TestServer -e 1434 -p UDP exits with return code 0x00000002.

    After swapping ports around when connecting remotely using SSMS I get these results.

    1. "TestServer\SQLEXPRESS2019" - Fails

    2. "TestServer\SQLEXPRESS2019,1433" - Connects to 2019

    3. "TestServer" - Connects to 2019?? 2019 is NOT the default instance

    On the TestServeritself in SSMS I get what I expect

    1. "TestServer\SQLEXPRESS2019" - Connects to 2019

    2. "TestServer\SQLEXPRESS2019,1433" - Connects to 2019

    3. "TestServer" - Connects to 2014

    How can 3 work remotely? Looks like "TestServer\SQLEXPRESS2019" is now the  default instance.

    I switched off Browser service and I get the same results




  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

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

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