Connection To Remote Server

I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
==================================================
"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.) (.Net
SqlClient Data Provider)"
==================================================
His server is set to allow remote connections. How do I resolve this?
Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999

> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>
|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.
|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.