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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 SQL Server 2000 can't connect to another one ??

Author  Topic 

hanglam
Starting Member

7 Posts

Posted - 2007-05-23 : 14:50:04
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

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-05-23 : 15:59:56
do you maybe have windows firewall turned on on the win 2k3 server?

also make sure that port 1433 is opened.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
Go to Top of Page

hanglam
Starting Member

7 Posts

Posted - 2007-05-23 : 16:53:03
no firewall.
I'm able to connect using my XP workstations on the same network as the Windows 2000 Server.
Also, port 1433 is opened.

any more ideas, please ??

quote:
Originally posted by spirit1

do you maybe have windows firewall turned on on the win 2k3 server?

also make sure that port 1433 is opened.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-05-23 : 22:48:11
Do you use windows or sql authentication? Can you ping win2k3 server from win2k one?
Go to Top of Page

hanglam
Starting Member

7 Posts

Posted - 2007-05-24 : 00:15:19
i'm using Enterprise Manager from windows 2000 server to login to SQL2000 running in Windows 2003 . I'm using SQL aunthentication. I'll check on the ping tomorrow . but I'm able to connect from my XP workstations on the same domain and network that the Windows 2000 belongs to, and the workstations are able to make the connection to the SQL2000 running on win2003

anyone else has ran into this issue before ?

thanks,



quote:
Originally posted by rmiao

Do you use windows or sql authentication? Can you ping win2k3 server from win2k one?

Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-24 : 00:25:22
Create an alias using Client Network Utility to fix this issue. But if that doesn't work, then you need to disable your firewall on the machine where you are getting the error. Windows 2003 has it turned on by default for security reasons. I noticed that spirit1 mentioned this earlier in thread, but it doesn't appear that you answered him if it was on or off.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

hanglam
Starting Member

7 Posts

Posted - 2007-05-24 : 16:25:36
firewall is off in Windows 2003.

I tried the alias tip as well but it didn't work.

anything else that you can think of??

Thanks,
Hang

quote:
Originally posted by tkizer

Create an alias using Client Network Utility to fix this issue. But if that doesn't work, then you need to disable your firewall on the machine where you are getting the error. Windows 2003 has it turned on by default for security reasons. I noticed that spirit1 mentioned this earlier in thread, but it doesn't appear that you answered him if it was on or off.

Tara Kizer
http://weblogs.sqlteam.com/tarad/

Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-24 : 16:32:34
Please post exactly what you tried for an alias.

Also, try connecting with this in Management Studio:
tcp:ServerName\Instance,PortNumber
or
tcp:ServerName,PortNumber
or
tcp:IpAddress,PortNumber

And are you positive that SQL Server is listening on port 1433 rather than a custom port? We almost never use 1433.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

hanglam
Starting Member

7 Posts

Posted - 2007-05-25 : 03:13:47
i went to Client Network Utility and selected the Alias tab. i click on NEW button and enter the IP address of the Win2003 server , selected TCP checkbox and assign it port 1433 . i checked on the server side as well and port 1433 was being used in Win2003 .

i tried entering those connection string in Enterprise Manager to no avail ...

why is it that I can connect to that Win2003 Server using my workstations with Enterprise Manager but I can't do the same from my Win2000 server-to- Win2003 ??

hang

quote:
Originally posted by tkizer

Please post exactly what you tried for an alias.

Also, try connecting with this in Management Studio:
tcp:ServerName\Instance,PortNumber
or
tcp:ServerName,PortNumber
or
tcp:IpAddress,PortNumber

And are you positive that SQL Server is listening on port 1433 rather than a custom port? We almost never use 1433.

Tara Kizer
http://weblogs.sqlteam.com/tarad/

Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-05-25 : 10:01:35
Can you connect to any other sql servers from that win2k machine?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-25 : 11:49:39
Try those tcp things I posted in Query Analyzer. I'm not sure that they work with Enterprise Manager.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
   

- Advertisement -