all groups > sql server connect > may 2007 >
You're in the

sql server connect

group:

SQL server can't connect to another SQL Server .


SQL server can't connect to another SQL Server . Scott Lam
5/22/2007 8:29:00 PM
sql server connect:
Hi,

I have SQL Server 2000 installed on a computer running Windows 2000 Advanced
Server.
I'm using enterprise Manager from the Windows 2000 server to try to connect
to another SQL Server 2000 installed on Windows 2003 server .
Whenever I tried to make the connection , I get the following error:
"SQL Server does not exist or access denied"

I read a lot of issues coming up when SQL 2000 is installed on windows 2003
server but i can't seem to find the solution.

All the latest patches and services packs are installed on both servers and
SQL servers.

I checked the client network utility to make sure TCP/IP and Named pipes are
enabled on both servers . Everything is identical . No aliases exists either.

I'm able to connect from my Windows XP workstation using Enterprise Manager
to the SQL Server running in Windows 2003 server , but NOT from the Windows
2000 server.

Also, i search the Microsoft Knowledge Base and I tried a lot of the
suggestions but nothing so far work.

Anyone knows what is happening here ?
Any suggestion ?

Thanks,
Hang
Re: SQL server can't connect to another SQL Server . Rick Byham, (MSFT)
5/24/2007 9:26:35 AM
This is a very general error, and lots of things could cause it. Since you
can connect to the Windows 2003 Server from the Windows XP workstation
computer, I suspect the problem is with the Windows 2000 Server. Look there
for the problem.
My first guess - the Windows 2000 Server can't resolve the computer name
properly because it has cached an old IP address.
- Can you Ping from the Windows 2000 Server to the Windows 2003 Server?
- Can you connect to the Windows 2003 Server with Enterprise Manager using
the IP address and port number, such as 123.4.5.01,1433?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view]
RE: SQL server can't connect to another SQL Server . Scott Lam
5/25/2007 1:44:00 AM
1. I can ping the server from Win2000 server
2. I tried using IPaddress,port as well .

do you have anymore suggestions ?

thanks

[quoted text, click to view]
Re: SQL server can't connect to another SQL Server . Rick Byham, (MSFT)
5/25/2007 1:39:14 PM
Sorry, I don't really have any more good suggestions. Some general ideas:

If you can connect server S from client C1 but not from client C2, then the
problem must be with client C2.
Can client C2 connect to any other SQL Server 2000 's? If not, perhaps there
is something wrong with the client network libraries on C2.

Using the Client Network Utility on C2, is TCP/IP enabled? Is it the first
protocol listed in the "Enabled protocols by order" list? (This presumes you
want to use TCP/IP.) Do the Client Network Utility values look the same as
client C1?

Firewall settings could be blocking you on either computer. For instance, on
server S, the IP Address of client C2 could be listed to be blocked. Or
client C2 could be in some untrusted sub-net. Unlikely I admit.

If the SQL Server on S1 is not listening on the default port (1433), then
you may need to adjust your connection string to some other port number.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]
AddThis Social Bookmark Button