Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
NeilG
Aged Yak Warrior
530 Posts |
 Posted - 2008-08-21 : 04:49:27
|
Crisis has hit me this morning for some reason, and hoping that you guys can help, I have a default SQL Server 2K5 on a local network machine running Windows Server 2003 For some reason when I now try and log on the the default SQL Server it is giving me the 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)Tis error has only just appeared today and the install has been on the computer for over ten weeks so I can’t understand why all of a sudden it decided to start this having worked perrfect since install.I have tried the usually, changing the protocol in Surface area config to allow remote connectons which did work last time, but appear to do nothing now, I have even tried restarting the service with Named Pipes disabled and enabled but with know joy Can anyone help as having look through google the only fix that seems to appear is the one for changing the remote properties in surface area config which I have already done  ***************************Life is for having Fun, and then a little work |
|
|
NeilG
Aged Yak Warrior
530 Posts |
Posted - 2008-08-21 : 05:38:21
|
| anyone anyone***************************Life is for having Fun, and then a little work |
 |
|
|
|
|
|
Connection problem appeared weeks after install