Post reply

Unable to connect to default SQL instance using a custom TCP port

  • April 9, 2020 at 9:21 am

    #3741689

    • Server A has a default SQL instance running on TCP port 12345.
    • Server A has the SQL browser service running.
    • Server B (on the same subnet) can connect to Server A using SSMS with/without specifying the port number.
    • If Named Pipes protocol is disabled on Server A, Server B can no longer connect without specifying the port number.
    • If an Alias is created on Server A, Server B still can't connect without specifying the port number.

    Is there a way to have Named Pipes disabled and connect to Server A without specifying the port number?

    Thanks in advance.

  • April 9, 2020 at 5:37 pm

    #3741843

    Have you tried creating an alias on server B?

    Where I work, we have the SQL aliases pushed out through the logon script (VBScript) to each end user machine.  Putting an alias on Server A does not put the alias onto Server B.  Aliases are tied to the individual machines.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • April 9, 2020 at 7:59 pm

    #3741876

    If you are always having to specify the port you may want to check to make sure UDP port 1434 is open on the firewall for the browser service.

    Sue

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

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