Pretty basic question, however I'm somewhat new with SQL Server. I have written some ASP.NET pages that I need to put on an external webserver, however they are coded to hit an internal SQL Server, that will be blocked by a firewall from the internal network. Currently I have the system setup so that I store a copy of the databases securely on the webserver, and they are updated once a day. I'm looking to change this so that I can hit the internal database regularly since they databases are constantly being updated. I have heard some suggestions about having a special external box that can pass through the firewall, however I'm looking for the most secure way to go about this without leaving a hole in my network security. Anyhow have any suggestions?
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Accessing Internal Database Securely
- Thread starter Clear
- Start date
You could poke a hole in the firewall, and allow ONLY your webserver to go to ONLY the database server on JUST the SQL ports. This would be pretty secure, unless someone cracks your web server. Idealy, you'd do this, and put the database server in a DMZ (half way between external and internal network), so that if someone does crack into the database server, they can't access the rest of your internal network.
This site seems decent
Think of a DMZ as a no-mans land; it isn't trusted by your internel network, yet still mostly shielded from the outside.
Oh, and since I'm at it, any servers that need to be accessed from the outside should really be in the protection of your DMZ, and not exposed directly to the internet.
Think of a DMZ as a no-mans land; it isn't trusted by your internel network, yet still mostly shielded from the outside.
Oh, and since I'm at it, any servers that need to be accessed from the outside should really be in the protection of your DMZ, and not exposed directly to the internet.