Database Discussion - SQL inside firewall/Web Outside

Print Page | Close Window

SQL inside firewall/Web Outside

Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: Database Discussion
Forum Description: Discussion and chat on database related topics.
URL: https://forums.webwiz.net/forum_posts.asp?TID=2642
Printed Date: 29 March 2026 at 2:25pm
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com

Topic: SQL inside firewall/Web Outside

Posted By: Thunder7
Subject: SQL inside firewall/Web Outside
Date Posted: 12 May 2003 at 12:23pm

Is it possible to access a SQL database from a web server
that sits outside a firewall?

If so, what is required. I believe we have port 1433 open
to allow any calls through, but I am not sure what else I
may need to get the SQL server to talk to the web server
out in the DMZ. If its possible.

Not a SQL person, just use it for basic stuff like this forum. So not sure how the communctions between the web server and SQL server.

Replies:

Posted By: michael
Date Posted: 12 May 2003 at 3:10pm

You need to forward the router/firewall to the pc with SQL installed.
Something like:
Inbound Port Type PrivateIP Private Port
1433 TCP 192.168.1.213 1433

It all depends on the type of router you have but should lead you in the right direction.

-------------
http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker

Posted By: Thunder7
Date Posted: 16 May 2003 at 5:54am

Well, I have verified that the firewall is allowing 1433 through it. I can get to the server on port 1433 from the Web server, but this forum softawre (6.34) gives the following error:

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNMPNTW]Specified SQL server not found.

/common.asp, line 176

Posted By: MorningZ
Date Posted: 16 May 2003 at 11:08am

if the SQL server is sitting inside a firewall and has a "non public" IP address.. ie/ 10.10.xx.xx , 192.168.xx.xx (some common ranges), and your Web server doesn't have an internal address like that, you wont be have one access the other

but i dunno, you dont provide enough info about the setup there... but typically a common setup is (this is going to be impossible to demonstrate in text, but i'll try anyways):

Outside World
       V
Router/FireWall
V                 V
Port 80         No access needed
V                 V
Web Srv        SQL srv

The web server should access the SQL server by the "internal" IP, and this protects people from the outside having ANY sort of direct access to the SQL box

IF the webserver is on the other side of the firewall (Outside World), not only do you have to open up port 1433 on the Firewall, you also need to tell (at the router/firewall) which internal IP "gets" this traffic

-------------
Contribute to the working anarchy we fondly call the Internet

Posted By: Thunder7
Date Posted: 19 May 2003 at 5:30am

MorningZ wrote:

but i dunno, you dont provide enough info about the setup there... but typically a common setup is (this is going to be impossible to demonstrate in text, but i'll try anyways):

Outside World
       V
Router/FireWall
V                 V
Port 80         No access needed
V                 V
Web Srv        SQL srv

The web server should access the SQL server by the "internal" IP, and this protects people from the outside having ANY sort of direct access to the SQL box

Thanks for the info and help.

Yes, we are using private IP addresses. There is a "translation" that is taking place that the web server does use to get to the SQL box inside the firewall. It is getting there via pings, and port 1433.

Are you saying, the problem is in the translation of the public IP to the private?

Posted By: Thunder7
Date Posted: 27 May 2003 at 5:28am

What authentication type should the database be set to in this scenario? Maybe that is part of my problem now.