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 - SQL Server does not exist...

Author  Topic 

Pancakes
Starting Member

3 Posts

Posted - 2009-05-14 : 15:36:15
Hey everyone. I have something I'm beating my head against a wall on here. I have a weird scenario, so let me lay this all out first:

1. New server - Windows Server 2008
2. Old Server - Windows Server 2000

I had to install SQL Server 2000 on the 2008 server (apps are running against the databases that do not support SQL 2005 or SQL 2008). I ignored the compatibility warnings for SQL 2000 on the 2008 server as I was installing. I detached the databases from th old server and attached to the new server. While on the new server, I can open Enterprise Manager and Query Analyzer and browse the databases (both objects and data) without issue.

When I go to ANY other machine, I cannot connect to the new SQL server (on the 2008 server). I get the "SQL server does not exist or access denied" error while trying to connect through both Enterprise Manager and Querly Analyzer. Port 1433 seems to be open everywhere because I can still connect to the old server. I've tried referencing the server both by name and by ip - both without any luck.

One other thing, the SQL 2000 server install has not been service patched. The person I'm trying to find out can't find and of the SP discs. I'm in the middle of DL'ing SP2 right now.

Do you think this is a SQL 2000 / Windows Server 2008 compatibility issue? Do you think dropping SP2 on the SQL server install will do it? Do you think I should find a new career? :)

Thanks for the help.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-05-14 : 16:14:58
Try connecting with ServerName,PortNumber. If you still get an error with that, then you need to verify that you are using the correct port number (1433 is just the default, but it could be different). If you get an error after you've verified the port, then you've got some network config issue such as a firewall issue.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

Pancakes
Starting Member

3 Posts

Posted - 2009-05-18 : 21:20:25
Well, here's a little update. I service packed everything and was able to sucesfully connect to the new server from another server.

HOWEVER...I still have a user running Enterprise Manager that cannot connect to the new server. She can connect to the old server. Any ideas?

It seems to me that if we can connect to the new server from another server, we should be able to connect to it from any workstation, right? There is only one domain, she can ping the server (and get the correct address back) and can remote onto the server from her workstation.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-05-18 : 23:40:57
So did she try ServerName,PortNumber?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

Pancakes
Starting Member

3 Posts

Posted - 2009-05-19 : 09:03:59
quote:
Originally posted by tkizer

So did she try ServerName,PortNumber?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."



Yes. It's a default install. Everything is on port 1433 - no luck there.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-05-19 : 14:05:42
If hostname,1433 doesn't work for her, then she also needs to try telnetting to it.

Go to Start..Run..cmd. Type "telnet hostname 1433" where hostname is the name of the database server. If she gets an error, then she needs to contact the network administrator.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page
   

- Advertisement -