Error Connecting to SQL 2000 from 2005 SSMS

I can connect to all but one of my SQL 2000 SP 4 servers with SQL 2005 SP2 SSMS on my workstation. I get the following error for the one:

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: 53)

I can connect to this server with the SQL 2000 Enterprise Manager from the same workstation I'm running SQL 2005 SSMS. I've also verified that tcp and named pipes are set up on the 2000 server. Can also telnet to the box with the default port #.

I'd appreciate any help you could give..

Thanks,

Dan

check the sql server 2005 is enabled for remote connection. check for firewall

http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

Madhu

Error after installing sp1

I started getting this after installing sp1 on my workstation and trying to deploy to rtm machines. The components giving this error are the data readers in the data flow.

TITLE: Microsoft Visual Studio

Component with name "<name>" and class ID "{BF01D463-7089-41EE-8F05-0A6DC17CE633}" could not be created because an error was encountered during its upgrade to the current version.
Contact information:
Extracts data from a relational database by using a .NET provider.;Microsoft Corporation;Microsoft SqlServer v9; ? 2004 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;2

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ComponentUpgradeFailed&LinkId=20476

BUTTONS:

OK

See Component Changes - http://wiki.sqlis.com/default.aspx/SQLISWiki/SP1.html|||That's just wonderful considering I installed it on my workstation as a test and now I can't roll out a lot of my packages. Ugh, I didn't think they could make management and deployment any more of a headache but they succeeded. How about they let you write the release notes from now on :)|||As a side note, it appears that even if I edit the xml as you suggest I still cannot deploy it from my workstation or it will readd those properties.|||Maybe you are using the built in deployment utility? I'm working in a file copy style deployment so it works fine as a workaround. Failing that roll out SP1!|||

Yeah I am. I suppose it calls that upgrade method before it uploads it to the server. *sigh*

We'd like to roll out sp1 if the install would quit crashing :)