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 |
|
Sqweebo
Starting Member
3 Posts |
 Posted - 2009-10-30 : 13:03:34
|
| Hi All, I have MSSQL Server 2005 installed on a Dell laptop. I have sucessfully installed a backup database from another MSSQL Server 2005 system and it all works fine from within SQL Server Studio. However, I cannot access the database from outside SQL Server Studio. I get the following error...[SQL Native Client]Named Pipes Provider: Could not open a connection to SQLServer [53].[SQL Native Client]Login timeout expired[SQL Native Client]An error has occurred while establishing a connection tothe server. When connecting to SQL Server 2005, this failure may be caused bythe fact that under the default settings SQL Server does not allow remoteconnections.I have followed the instuctions of 'How to configure SQL Server 2005 to allow remote connections' and checked and rechecked everything. I have added all the necessary exceptions to the firewall. I have even closed down the firewall but I still get the error message. I have tried creating a new database via SLQ Server Studio and all is OK. I tried creating a new database via a batch task and that produces the same error. I am at a loss to resolve this so any help will be much appreciated.Also, can a database created under SQL 2005 be fully used under SQL 2005 Express so long as it does not exceed the size limits?Regards,Sqweebo |
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2009-10-30 : 14:01:02
|
| change from named pipes to tcp/ip |
 |
|
|
Sqweebo
Starting Member
3 Posts |
Posted - 2009-10-30 : 15:05:06
|
| Thanks for the help.I am not sure how to do that? As I have both named pipes and tcp/ip enabled I disabled named pipes and tried again. I now get...[SQL Native Client]TCP Provider: No such host is known.[SQL Native Client]Login timeout expired[SQL Native Client]An error has occurred while establishing a connection tothe server. When connecting to SQL Server 2005, this failure may be caused bythe fact that under the default settings SQL Server does not allow remoteconnections.So I guess I am missing something else? |
|
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2009-10-30 : 16:31:22
|
| did you enable remote connections under the surface area scan |
|
|
|
Sqweebo
Starting Member
3 Posts |
Posted - 2009-10-30 : 19:28:09
|
| Yes, set to using tcp/ip only |
|
|
|
|
|
|
Yet another connection error - duh!