By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,853 Members | 941 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,853 IT Pros & Developers. It's quick & easy.

Cannot See a Newly Installed SQL Server 2000 (No Active Directory)

P: n/a
We have just installed a SQL Server 2000 (SP 3A) onto a computer that
has Windows-2003 Server on it. Now, we cannot get access to that
database server from other computers. Seem like this may be an issue
with Active Directory.

Our network consists of Windows-2000 Servers (SP 4) and Windows-2000
workstations and Windows-XP workstations. We also have SQL Server 2000
(SP2) in three Windows-2000 servers. All work fine. Recently, we get a
new server that has already had Windows-2003 Server pre-installed.
After we have installed SQL Server 2000 (SP 3A) on the new server, we
find that we cannot get access to that new database server from other
computers.

I have tried connecting to that new database server using Query
Analyzer (using both the sa account and Windows Authentication), and I
get this error message:
Unable to connect to server NEWDBSRV:
Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or access denied.

I have tried connecting to that new database server using ISQL (using
both the sa account and Windows Authentication), and I get this error
message:
DB-Library: Unable to connect: SQL Server is unavailable or does not
exist.
Unable to connect: SQL Server does not exist or network access
denied.
Net-Library error 53: ConnectionOpen (Connect()).

I have also tried to register the new database server using Enterprise
Manager (again, using both the sa account and Windows Authentication),
and I get this error message:
NEWDBSRV - SQL Server does not exist or access denied.
ConnectionOpen(Connect())

The only way that I can get access to the new database server is to
open Enterprise Manager directly on the new server.

I have compared the properties of the new database server and those of
the other existing database servers. The only differences are:
- Other database servers are running Windows-2000. The new database
server is running Windows-2003.
- The new database server is missing the "Active Directory" page-tag
when I check its properties using Enterprise Manager. We use Active
Directory in our network, and the Active Directory is being run from a
Windows-2000 server (that is currently also a database server).

According to our network administrator, he has already put the new
server into our Active Directory. He doesn't know why it is missing
the Active Directory page-tag. He believes this has something to do
with its having Windows-2003 that is different from other servers
(that have Windows-2000).

Thanks in advance for any info.

Jay Chan
Jul 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
if you can connect with Query analizer on the server but not on a client
then tcp/ip is not activated. Look for SVRNETCN.exe (normaly in
C:\Programs\Microsoft SQL Server\80\Tools\Binn) and check if
tcp/ip is activated. Since version sp3A tcp/ip is disabled per default,
if you do the installation without DISABLENETWORKPROTOCOLS=0
Read more about it in "3.7.3 MSDE 2000 Setup Parameters" on
http://support.microsoft.com/default.../SP3ReadMe.asp
hth,
Helmut
Jul 20 '05 #2

P: n/a
Thanks for the suggestion.

Our network administrator has fixed this problem. The IP address in
the DNS server didn't match the one that was actually assigned to the
new server. The story was that he let the installation program to pick
a IP address that ended up saved in the DNS server. Later on when he
assigned the actual IP address to the new server, he didn't realize
that the DNS server still had the outdated IP address. I am not
exactly sure whether I get the story right; but this sounds like the
one our network administrator told me.

Jay Chan
Jul 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.