SQL server connection problem

just installed SQL server 2000 and using my client , i can't locate
the server. I used SQL query analyzer to search but no servers were
found. Error message is as below


Server : Msg17,level 16, state1
[Microsoft][ODBC SQL server driver][DBnetlib] SQL server does no
t exist

or denied access.


Regards
Daniel

Am 13 Nov 2005 08:14:32 -0800 schrieb Danieltbt05@gmail.com:

>  just installed SQL server 2000 and using my client , i can't locate
> the server. I used SQL query analyzer to search but no servers were
> found. Error message is as below
>
>
> Server : Msg17,level 16, state1
> [Microsoft][ODBC SQL server driver][DBnetlib] SQL server does 
not exist
>
> or denied access.
>
>
> Regards
> Daniel

Check your SQL-Server client configuration on the server, if TCP is
enabled. If you did not specify it when installing SQL Server, then TCP is
disabled for security reasons!
You should find this tool in your program list, if not, search for
"SVRNETCN.exe" (should be in  C:\Programs\Microsof
t SQL
 Server\80\Tools\Binn
\)

bye,
helmut

(Danieltbt05@gmail.com)  writes:
>  just installed SQL server 2000 and using my client , i can't locate
> the server. I used SQL query analyzer to search but no servers were
> found. Error message is as below
>
>
> Server : Msg17,level 16, state1
> [Microsoft][ODBC SQL server driver][DBnetlib] SQL server does 
not exist
>
> or denied access.

Which means that ODBC cannot find the SQL Server. There are a number
of possible reasons. The most trivial is that SQL Server is not running.

For other possible reasons check
http://support.microsoft.com/defaul...;EN-US;q328306.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Hi, just want to verify that I can login to the SQL server from the
server itself. So does it mean it is really a port or protocol problem
? I'll check the configuration when i'm at home. Thanks

Regards
Daniel


helmut woess  wrote:
> Am 13 Nov 2005 08:14:32 -0800 schrieb Danieltbt05@gmail.com:
> 
>
> Check your SQL-Server client configuration on the server, if TCP is
> enabled. If you did not specify it when installing SQL Server, then TCP is
> disabled for security reasons!
> You should find this tool in your program list, if not, search for
> "SVRNETCN.exe" (should be in  C:\Programs\Microsof
t SQL
>  Server\80\Tools\Binn
\)
>
> bye,
> helmut

Hi, does ODBC indicates database driver or protocol issue from your
knowledges ? Thanks

Regards
Daniel

(Danieltbt05@gmail.com)  writes:
> Hi, does ODBC indicates database driver or protocol issue from your
> knowledges ? Thanks

As I said, the message means that the SQL Server could not be found. Which
could be because it is not running, because it does not listening on
the protocol you are trying to use etc. Please refer to the KB article
I gave you a link to.

If you cannot work it out, you will need to provide more details, as
connection problems can have so many reasons, that it's not meaningful
to give a guess without access to the environment.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Hi, i managed to make it connected by specifying alias in the server.
I'm not sure why ? but after connected i still can't login , another
error came out

Server : Msg17,level 16, state1
[Microsoft][ODBC SQL server driver][TCP/IP sockets] SQL server
does not exist or denied access.


Regards
Daniel

(Danieltbt05@gmail.com)  writes:
> Hi, i managed to make it connected by specifying alias in the server.
> I'm not sure why ? but after connected i still can't login , another
> error came out
>
> Server : Msg17,level 16, state1
>          [Microsoft][ODBC SQL server driver][TCP/IP sockets] S
QL server
> does not exist or denied access.

That's the same message as in you original post, save for the last
bracket. You still fail connect.

For further assistance, please anser these questions:

Have you verified that SQL Server is running?

Is SQL Server on the same machine you try to connect from?

Which protocols are SQL Server configured for? (You can view this
in the Server Network Utility).

If you changed which protocols SQL Servers uses, did you restart SQL Server
after this?

Is there a firewall on the SQL Server machine?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Yes I've check in my server the SQL service is running. No i tried to
connect from another machine. Server is Win2003 standard server and
client is Win2000 prof. Both netlib uses TCP/IP and port 1433. I
configure both named pipe to be the same. Each can ping each other
either by IP or host name. I never change any protocol, uses the
default TCP/IP. As far as i know there is no firewall between them,
unless there is the windows internal firewall security ? is it
possible? . Btw what is alias for ? by using alias i can find the
server host name but not IP . Thanks

Regards
Daniel

(Danieltbt05@gmail.com)  writes:
> Yes I've check in my server the SQL service is running. No i tried to
> connect from another machine. Server is Win2003 standard server and
> client is Win2000 prof. Both netlib uses TCP/IP and port 1433. I
> configure both named pipe to be the same. Each can ping each other
> either by IP or host name. I never change any protocol, uses the
> default TCP/IP. As far as i know there is no firewall between them,
> unless there is the windows internal firewall security ? is it
> possible? .

I Windows Firewall is running on the machine with SQL Server, you will need
to configure the firewall to permit connections to SQL Server.

> Btw what is alias for ? by using alias i can find the
> server host name but not IP . Thanks

Aliases are good when connection by name does not work, and you don't want
to use IP-address and port number all the time.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx