After the latest security updates from Microsoft, a connection I had to a server in my local area network no longer works. I can log onto the machine sql server itself is installed on and use SQL Server Studio with no problem. However, when I try to connect from my desktop machine, as I've been doing for months with no problem, I get the following error
An error has occurred while establishing a connection to the server. When connecting to SQL server 2005, this failure may be caused by the fact that under the default settings SQL server does not allow remote connections. Provider: SQL Network interfaces, error: 26 - Error locating Server/Instance Specified) (Microsoft SQL Server).
I notice that Microsoft Security Bulletin MS06-025 addressed a vulnerabiilty in Routing and Remote Access vis a vis KB 911280.
I don't know for sure, but the only change to my environment of which I am aware is that this security bulletin was pushed out to the server and my workstation (W2003 server and Windows XP Professional respectively) by our WSUS server. Is it known whether my problem could be caused by the security bulletin update If so, how do I work around it Hate to just assume the update from Microsoft caused the problem but that is the only thing I know of in my environment that changed.
I have checked my server and my SQL Server 2005 instance is definitely set to allow remote connections.
Thanks in advance for any advice.
Not able to connect to server from SQL Server Management Studio
scrptman
Solved the problem (till I find out what went wrong). I uninstalled the critical updates released on 06/13/2006 as follows:
KB911280, KB914389,KB916281,KB917953,KB918439
After uninstalling these, I was able once again to connect from my desktop machine to my SQL Server 2005 instance. I will do further research and find out why these critical updates prevented me from connecting even when I had specified on SQL Server that remote connections were allowed. Once I find out what the underlying problem was, I will reapply these critical updates.
But, it was definitely the updates mentioned above that caused the problem. I uninstalled KB911280 first and it warned me that the others might not function properly in the absence of KB911280 so I uninstalled them too in order to be safe.
Vorrtexx
Hi swells,
I am having the same problem and will try this. The question is, did you uninstall the updates from your desktop, or from the server.
While I get your answer, I will start by uninstalling from the Desktop.
Thanks,
Angel