Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a longtime user of StackOverflow, but I thought it would be more appropriate to ask this general question here.

I am a decade-plus web designer looking to get my web apps interfacing with the various systems of my clients. In one particular case I have a client who stores their data on a server rack running Microsoft Server and housing data in Dbase files, and I would essentially like to learn how to get this securely hosted to the outside world (I guess I would need to setup a static IP?) so that I may interface a web application to it.

What I'm looking for is a direction to go on the subject(s) I would need to learn in order to do things like this. Also, any books, websites or other resources you recommend me reading would be greatly appreciated. I'm a very quick self-learner, I'm just unsure of what to even look for or where to begin.

share|improve this question
up vote 2 down vote accepted

A lot of this depends on what infrastructure your client already has in place, what level of risk vs level of spend you and the client are willing to undertake, and how important the availability of these web apps are to the client's business.

Be that as it may, in order to have your web app available to the outside world, fronting for the client's MS/Dbase backend (presumably totally private), you'll need at a minimum:

  1. A link to the public Internet - yes, this should include a public IP (or a set), provided by most ISPs
  2. A router, between the client LAN and the public Internet - again often provided by the ISP
  3. A firewall: this can be done on the router, or on an additional box
    • router: pro: will most likely be bundled with the line cost, con: routers (even with GUIs) are difficult to maintain in a dynamic environment and aren't as flexible as OS-based firewalls;
    • box: pro: your choice of firewalling environment, including many additional features, con: costs in both money and time

My quick 2c regarding firewalls (as the link, router, IPs is something you'll have to do the research on around ISPs in your area):

If the customer is willing to pay, and would like to manage this themselves one day, since they already have MS infrastructure, I'd recommend Microsoft's Security Server offering - this may even be possible to run on the same MS box, so only licensing would be the cost.

If you're willing to learn and the customer doesn't want to spend anything at all other than link costs, then when doing your research see what routers/interfaces to managing your link the ISP provides and whether it offers the correct security for your purposes.

If you're willing to learn and the customer is willing to spend a bit, then a *nix-based firewall distro on a 1U box is a great way to go. There are many firewall distros to choose from (far be it for me to recommend to someone who wants to learn ;) ), and you will learn a lot, guaranteed.

In closing, in my mind based on the tone of your question (and without prior knowledge of your background and experience), I'd suggest at least a passing knowledge of the following to start you on your road to network infrastructure builder:

As usual, HTH && YMMV.


share|improve this answer
Very informative answer. Thank you! – Allen Gingrich Nov 22 '10 at 15:29

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.