Alan Edwardes

Vague guide to making a server

The idea dawned on me as I was bored one day: Why not setup my own server?

Well, I didnt want a permanent server, just one that I could play around a bit with, and test to see what its like to run one.

So, I went straight to google, and found the Apache server software, and tried experimenting around with it. Requirements:

A computer connected to the internet (You will need a broadband connection). Apache HTTP Server software

A direct link to the internet, or through a gateway. (Im using the NETGEAR DG834G Wireless ADSL Firewall Router)

An Internet security package. (Im using Norton Internet Security 2006)

The problem I found when I was running apache, was that my router was timing out when I asked people to try the ip address. This is because you need to setup a service on the router that tells it to point connections to a specific port at your computer's IP on the netowrk. Sounds difficuilt, huh?

If you have a router with a firewall similar to mine, you will probably have a specific IP to acess its setup. Unless you have previously altered the router's IP, the factory default should be something like "http://192.168.0.1/".

You need to find a way to direct trafic coming towards your ip to the computer running apache. (My settings were under "Firewall Rules" then "Incoming Connections".

So, when I was sure my website was accessable from outside my network I edited the dns records for Alan Unleashed as follows:

And there you have it - My very vague guide to making a server. ;)

25th of August 2006 at 1:02 AM

5 years, 9 months ago

written by Alan Edwardes.

280 words

rand: Postnatal: Kinect

next: Good fortune

prev: Youtube Music Videos

share:FacebookTwitterRedditdiggStumbleUpondeliciousHacker NewsLinkedIn

Add a Comment

© 2006 – 2012 Alan Edwardes / code on github
Top