Having a bit of trouble accessing my newly set up apache web server...?

Very simple.

First you need to know your public IP address.

1. Go to http://manfield.com.sg/ip.php

2. Then you need to check if port 80 is opened for the public. Follow the link below where ?port=80 is your port number. http://www.utorrent.com/testport?port=80

Two possibilities to why port 80 might not be forwarded.

a. you did not forward port 80 on your router.

b. your ISP might block port 80 as your internet connection is not meant for business purpose.

If you have already successfully done port forwarding on your router then port 80 is blocked by your ISP .

No worries.

3. use another port number. a webserver dont have to be on port 80.

lets use port 2008 instead.Port forward that port on your router. Then you need to edit a file called httpd.conf.

It should be located in apache\conf\httpd.conf.

4. open httpd.conf with notepad. There are 2 lines you need to change.

do a Ctrl+F "Listen 80". change it to "Listen 2008"

do a Ctrl+F"ServerName localhost:80" Change it to ServerName localhost:2008

5. Save it. Restart apache Server.

6. open your web browser enter http://yourpublicipaddress:2008/

7. It should work, unless the settings are wrong.

What you need is your public IP. This is the IP given to you by your isp. You only have one most likely and most likely it is dynamic and changes periodically. You can pay to have it be a static ip if you want to .

If you go to http://www.whatismyip.com/ it will tell you your public ip. That is NOT the 192.168.x.x , that is your private ip. Your router uses network address translation to change your public ip into multiple private ip's. Every private network in the world pretty much uses 192,168,x,x, 172.x.x.x, or 10.x.x.x, they are class c private ip's......ramblin' on sorry :D.

You say you forwarded the port?

If you didn't, open a web browser and go to http://192.168.x.1/ . x=either 0 or 1. Log into the router, if you didn't set that up when you originally got your router set up, here is a comprehensive list of default router passwords http://www.routerpasswords.com/

Then go to (depending on your router brand) 'applications and gaming' , 'advanced routing', or 'port forwarding'.

It will ask for a range range=80 to 80(you can add more if you are going to use more virtual hosts on your server) then you need to pick the protocol either tcp or udp or both......I "believe" that tcp is all you actually need, but choose both to be safe. Then you need to put in the "private" ip of the computer that your server is located on. You can get this by opening a command prompt and typing ipconfig /all I think you are using wireless so choose the wireless adapter with the 192.168.x.x address, and put that in the port forwarding spot. You then give that port forward a name, check the 'enable' box and then save the settings on your router.

If you don't do this and you try to connect to your server from the outside your router won't know how to route that to your computer so it won't let it through. Does that make sense? Ok, say you are at a friends and you want to show him your server. You open a web browser and type in http://74.33.88.4/ (:xx = the port number you want in on, :3389 for remote desktop same port forward technique) Your router will get a request saying "hey, lemme in so I can check out what you got in all of those thousand boxes. I am gonna go and get some stuff that belongs to me" and your router will reply "Ok ......dude, but all of those boxes aren't mine, who's boxes are you gonna want to look through? I'll ask if they said anybody can look through their boxes" and your request says "Oh c'mon I wanna look at anything I want to" ......yadda yadda yadda. I think you get what I am saying. The router needs to know which computer the incoming request is for so it can "ROUTE" the package.

BTW, I apologize for my ridiculous ramblings)

After reading your post I see I could have said "yes port forwarding is supposed to take care of directing the incoming requests to the correct computer, but I instead rambled incessantly.

I hope this helps. Good luck.

Also check out dyndns for a dynamic "domain name server" host. They will set you up with a free domain name. Then you can actually give out a url for people to connect to your webserver without actually having to pay for a domain name.

Get a Mac. it quite is an Apache Server already. you in basic terms ought to designate a partition on your force and get your IP to have the DNS of your area pointed in direction of your desktops IP. you do no longer ought to have an internet site. you are able to in basic terms use your IP. that may no longer very lots relaxing and is not any longer very maintain.