SQL Connectivity issues after changing default port

  • Hi,

    I have a test server with two SQL server instances running on it. Both are SQL 2017 STD ) One is default instance and other is Named instance. The default instance was running on default port 1433, i have changed it to use another port. After restart of SQL Server services and server, the connection is timing out when trying to connect via SSMS. I changed the timeout settings from 30 secs to 120 secs, it eventually connects but is super slow and sluggish.

    • I have opened the new port in windows firewall and TCP & UDP port 1434 is also open.
    • Verified that the new port number is not being used by any other application.

     

    Any suggestions are welcome.

     

    • This topic was modified 2 months ago by  keyurinbox.
    • This topic was modified 2 months ago by  keyurinbox.
    Attachments:
    You must be logged in to view attached files.
  • 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