Re: One more connection problem-Security Issue
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Sun, 10 Sep 2006 21:45:00 +0000 (UTC)
Curt (myemail@xxxxxxxxxxxx) writes:
My company gave me their old Windows 2000 server. I installed my
database on it and the ODBC connection works perfectly on the server.
When I go to my client machine I go the the ODBC Connections in it and
it fails. It refuses connections and will not reply to pings. It is not
a network issue, as I can telnet to the server just fine. It's strictly
a security issue. I just have no clue where to look. Any suggestions
would be appreciated. Thanks
Which version of SQL Server?
If you are using SQL 2005, you need to enable remote connections, as by
default Express and Developer Editon only accepts local connections. You
can use the Surface Area Configuration tool for this.
Also, if you are using SQL Express, make sure that SQL Broswer is running,
so that the named instance can be found.
If you are using SQL 2000, I would look in the Server Network Utility
to see which protcols that are installed.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- One more connection problem-Security Issue
- From: Curt
- One more connection problem-Security Issue
- Prev by Date: Computed Column Specification
- Next by Date: Re: Creating a dynamic Global Temp Table within a stored procedure
- Previous by thread: One more connection problem-Security Issue
- Next by thread: Computed Column Specification
- Index(es):
Relevant Pages
|
