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 |
|
anchaljain
Starting Member
8 Posts |
 Posted - 2007-06-07 : 02:45:35
|
| Hi, I have SQL Server 2005 running on a machine with "Allow Remote Connections" property turned on. This server has SQL Server Authetication mode turned on.I can connect to the server locally with sa login and password but when I try connecting to the server remotely it gives me following error:TITLE: Connect to Server------------------------------Cannot connect to ServerName.------------------------------ADDITIONAL INFORMATION:A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233).Any help is appreciated. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-06-08 : 00:34:00
|
| Is sql server browser service running on sql server? |
 |
|
|
anchaljain
Starting Member
8 Posts |
Posted - 2007-06-08 : 05:30:11
|
| Ya. I have turned that also on.Hardware requirement is also meeting.I am using SQL Server 2005 Developer Edition. can that be a problem? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-06-08 : 12:56:00
|
| ensure you enabled named pipes on server, or try connect with tcp/ip. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-06-08 : 13:02:33
|
| You just need to add an alias to the client machine using SQL Server Configuration Manager or Client Network Utility.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Remote Connection