W D
asked on
Windows updates KB958644/KB948109 (critical security updates) + SQL Server 2005 error 53
I am no longer to connect remotely to our SQL Server database after the important updated KB948109 and/or KB958644 were installed over the weekend. In the SQL Server Surface Area Configuration Tool, I was allowing for Remote Connections via TCP/IP. This morning, everything was working as usual, and then all of a sudden it stopped allowing remote connections to the database.
Our .NET web app couldn't connect until I increased the remote connections setting to allow both TCP/IP and Named Pipes to remotely connect. However, I still cannot connect remotely via Management Studio, from a .NET Windows application that uses a connection string to connect to the database, or from another application that uses ODBC to connect to the database. I attempted to install the patches, but the problem is still occurring. We are using SQL Server 2005 SP2, which is installed on a Windows Server 2008 SP1 box.
Any thoughts on if/how these patches are causing the issue, and what the appropriate response is to get my connections working again?
Our .NET web app couldn't connect until I increased the remote connections setting to allow both TCP/IP and Named Pipes to remotely connect. However, I still cannot connect remotely via Management Studio, from a .NET Windows application that uses a connection string to connect to the database, or from another application that uses ODBC to connect to the database. I attempted to install the patches, but the problem is still occurring. We are using SQL Server 2005 SP2, which is installed on a Windows Server 2008 SP1 box.
Any thoughts on if/how these patches are causing the issue, and what the appropriate response is to get my connections working again?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.