Re: Unable to connect to SQL 2000 engine on other machine from SSMS



One possibility. On the client computer you can connect to the SQL Server 2000 server using Enterprise Manager. That's using the network settings of the SQL Server 2000 Client Network Utility. And I presume TCP (or your preferred protocol) is enabled.
But when you connect from the client with Management Studio, it will use the network settings from the SQL Server Native Client, and perhaps TCP (or your preferred protocol) is not enabled for your client. Using the SQL Server Configuration Manager, on the client computer, check the SQL Server 2005 Native Client Configuration \ Client Protocols, and confirm that TCP/IP (or your preferred protocol) is enabled. Try moving it up in the Order value so your preferred protocol is selected first.
At any rate, I'm guessing that Enterprise Manager and Management Studio are attempting different protocols.
The problem could also be caused by an Alias that is used by EM but not configured for SSMS.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ronald Bijlhouwer" <Ronald Bijlhouwer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D2CF40EE-0037-4B23-8EDC-5189CF851CCB@xxxxxxxxxxxxxxxx
On my machine I have installed both SQL Server 2000 as SQL Server 2005.
On another machine SQL Server 2000 is installed.
I am able to connect to my local SQL Server 2000 Engine from within both
Enterprise Manager as SSMS.
Enterprise Manger also allows me to connect to the other machine, however
when I try to connect to it from SSMS I receive an error saying it cannot
connect.
In both cases I have used SQL Server authentication.

Any help appreciated.

.



Relevant Pages

  • Hide Databases
    ... I´m sharing a SQL Server 2000 SP3a with some users. ... These users are using Enterprise Manager and Query ... Analyzer at client side. ... How can I hide Databases ...
    (microsoft.public.sqlserver.security)
  • Re: Sql Server client software question
    ... You must be talking about SQL Server Management Studio which is the successor of Enterprise Manager in SQL Server 2000. ... SSMS is a management tool and it will not be installed if you do not select it to be installed in SQL Server 2005 Setup, in the Features to Install window. ... To install Client Tools after the SQL Server 2005 Database Engine ...
    (microsoft.public.sqlserver.setup)
  • firehouse mode
    ... >displayed in SQL Server Enterprise Manager, ... >When using SEM to display the rows from a table, ... >as fast as the client can process them. ...
    (microsoft.public.sqlserver.server)
  • SQL Connection Not Established
    ... My client loges in to SQL from her local desktop via SQL Enterprise Manager ... SQL Server does not exist or access denied. ...
    (microsoft.public.sqlserver.server)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)