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

Access MS SQL through ISA Server 2004

Hi experts, I'd appreciate any assistance with the following please!

I have a server that has ISA Server 2004 set up on it, and also MS SQL 2000.  When creating an ODBC connection on the server to MS SQL it connects fine, however any internal computers cannot connect to SQL Server - I just 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.

So far I have done the following to try and get this working:

1) Followed the steps highlighted in http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/publishingsql.mspx 

2) Logged all traffic in ISA Server, and it picks up that the client's trying to connect to SQL Server, but nothing is coming up as "Denied"

3) SQL Server is setup to allow "SQL Server and Windows" authentication

4) In SQL Server properties, "TCP/IP" is in the "Enabled Protocols" list set to port 1433

5) When creating an ODBC connection I have tried connecting with Windows Authentication and the System Administrator login details

6) Also when creating the ODBC connection I have unselected the "Dynamically determine port" option and set the port to 1433.

What obvious thing am I doing wrong?

Many thanks!

  • 3
  • 2
1 Solution
Keith AlabasterCommented:
What are you trying to achieve? Publish the sql server to the outside or use it for your internal users?
What ports have you forwarded from your external firewall/router to the ISA server external interface? (If its to the outside world)
Have you allowed traffic from the internal to local host and back? (if its for the internal users)

Need some details please
danielgalloAuthor Commented:
Hi, thanks for the reply.

I'm trying to publish the SQL Server to internal users only.  

I have setup a rule in ISA Server following the guide on the Microsoft site (http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/publishingsql.mspx):

Protocol: TCP Inbound, Port 1433
From / Listener: Internal, Local Host
To: (Internal IP address of server)

When I monitor the connections in the "Logging" section of ISA Server, the connection pops up and it matches the rule name that was created for SQL Server.  There's several items that are displayed which match this rule, one for "Initiated Connection" and another for "Closed Connection".  There's about 36 of these logged for each time an ODBC connection has tried to be setup on an internal computer.

Everything else works fine for the client computers, i.e. they can access the net, e-mail etc, it's just I can't seem to get this SQL problem sorted.

Hope this info helps.
Keith AlabasterCommented:

You don't need to publish the sql server then as 'publishing' is for outside users coming in.
If the SQL service is running on the ISA server, all you need to do is create a new access rule allowing internal & local host (in the from box) to internal & local host (in the to box).
In the protocol box, you can either set it for all protocols or just for the MS sql server protocol.
danielgalloAuthor Commented:
So simple!  Thanks very much for that!
Keith AlabasterCommented:
More than welcome :)


Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

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