SQL Connectivity issues after changing default port

• keyurinbox

  Old Hand

  Points: 300

  More actions

  October 16, 2024 at 6:04 pm

  #4469284

  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 5 months, 2 weeks ago by  keyurinbox.
  • This topic was modified 5 months, 2 weeks ago by  keyurinbox.

  Attachments:

  You must be logged in to view attached files.

• Site Owners

  SSC Guru

  Points: 80342

  More actions

  October 17, 2024 at 6:10 pm

  #4469673

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

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