Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

making home server publicly available

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 9 posts
So installed Apache and PHP on my XP partition. I've tested some scripts and it serves everything up just fine. I'd like to be able to access it remotely (and have others access it) but I'm not sure how. I'm on DSL behind an ACTIONTEC router. Security is nice but it's second in priority to making everything work. ie I'll set this up even if it opens my computer to all [bleep]. My windows partition lays dormant most of the time anyhow.

I really don't know the first thing about how I'm supposed to direct another computer to this one. Can I just type my routers WAN address? How would that differentiate this computer from all the others on the network?

Whatever tips anyone has on just general networking would be great.

Arg! Total noob stuff;

could anyone suggest a breif tutorial/overview/howto of basic networking principles? I mean, what the deuce is a netmask for?

Edited by transkinetic, 06 May 2005 - 03:22 PM.

  • 0




    Je suis Napoléon!

  • Administrator
  • 26,039 posts
  • MVP
a netmask differentiates the parts of an ip address. in an IP such as with a netmask of the first 3 sets are the network id and the last is the host id so basically anything on 192.168.1.anything is part of the same network. this is used to differentiate hosts on networks. so with that subnetmask and are not only different machines but are on different networks and unless you have some routing going on neither of them knows the other exists.
  • 0



    Member 2k

  • Retired Staff
  • 2,678 posts
I just set this up myself in my home. Here's what you do. Go to your router's config page ( or something similar) and open TCP Port 80 to the local IP of the Web Server. Now when you type in your public IP from a remote location the router knows that incoming Port 80 (HTTP) requests go to the local ip of the web server (which you specified in the config). Now if you have a software firewall on it then you need to open that port in there also.

-=jonnyrotten=- :tazz:
  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP