Why is my workstation trying to find the SQL server on the wrong port?

  • Thread starter Thread starter Jim W4
  • Start date Start date
J

Jim W4

Guest
I have an application configured through SQLExpress 2012, which is configured to listen on tcp 1433 as the default.Lately, we have desktop clients getting weird error messages trying to login to the app (Operation not allowed when the object is closed) and the one thing I've noticed about these workstations is that they are trying to connect on tcp 1434 instead of 1433. Is there a way to change the client to connect to the correct port? Or, more broadly, why does this behavior suddenly change when most workstations were doing the correct thing and attempting to connect on 1433 until some tim

Continue reading...
 
Back
Top