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 |
|
rayblair
Starting Member
2 Posts |
 Posted - 2008-04-17 : 09:04:38
|
I get this error message, the only problem is my sql server is not a 2005 version, it's 2000.I know very little about sql mgmt, so ant help needs dumbed down. Any suggestions?ThanksERROR: 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) |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-04-17 : 11:39:44
|
| Enable TCP/IP and named pipes protocol in client network utiltiy. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-04-17 : 22:14:11
|
| You sure you want to connect to sql2k? By the way, need enable tcp/ip or named pipes in server network utility on sql2k. |
|
|
|
rayblair
Starting Member
2 Posts |
Posted - 2008-04-18 : 09:51:54
|
| Issue resolved.Turns out it was caused by the developer attempting to access a SQL server behind a firewall. We have it as linked server and he failed to realize the connection string had to go through the outside server to get to the internal. |
|
|
|
|
|
|
SQL Server does not allow remote connections