• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 44727
  • Last Modified:

No connection could be made because the target machine actively refused it

I have a SQL Server 2005 Express installed on my Intranet server that resides in my DMZ.

I have access from my LAN to my DMZ open.

I have the SQL Server configured to allow remote connections to the server.

When I attempt to access the Database services from my "Microsot SQL Server Management Studio" I get the following error:

An error has occurred while establishing a connection to the server.  When connecting to SQL Server
2005, this failure may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because
the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)


When I attempt to establisg a connection through ODBC. I get the following error:

Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

Could an expert please give me some clues at what may be wrong.

Regards

Jim

0
jsulliva1957
Asked:
jsulliva1957
1 Solution
 
imitchieCommented:
you need to allow on remote connections on the SS2005Express installation
0
 
imitchieCommented:
From Start->Programs,Microsoft Sql Server 2005, Configuration Tools, SQL Server Surface Area Configuration
near the bottom, click on Surface Area Configuration for Services and Connections
on the tree at the top left, expand to SQLExpress, Database Engine, Remote Connections.
on the right, click on Local and remote connections, Using both TCP/IP and named pipes.
Apply and click OK.
close all windows opened
0
 
YveauCommented:
imitchie is right.
... and don't forget to restart the SQL service !

Hope this helps ...
0
 
jsulliva1957Author Commented:
Thanks imitchie,

This is EXACTLY the solution.

Regards

Jim
0
 
Jerryuk007Commented:
imitchie solutions are the most likely cause of the problem...

Also if that doesn't work, please check this:
Is your SQL Server in the same Network Domain as your Client ?
-- If not check the Domain Trust...

Check your user name and password you're using to open your connection.

Also I had a similar problem using OLEDB Connection though a VC++ box to connect to a SQL Server when that application run on Citrix (it worked fine on a normal networked workstation !)... The way arund was to use an ODBC Connection (DSN) but I suspect the problem might have been with an old DLL on the Citrix Server.

Check that the SQL Server accept the type of connection you're trying to use (TCP/IP for both is generally better than Named Pipes especially with "Trusted Auth")...

Hope this helps !

Jerry
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now