Jump to content

Archived

This topic is now archived and is closed to further replies.

davidyu8888

How can I access my Apache server through my external IP ?

Recommended Posts

I have struggled weeks to set my Apache right, so I can access it from a browser

outside of my LAN, but I can\'t.

I have asked the network administrator of my LAN to forward port 80 to my machine ( where the apache

server sits) and neither the lan or my machine have firework setup.

But I can only access my websites through

http://localhost/test/awesome.swf

http://192.168.100.3/test/awesome.swf(my LAN IP) from a machine on my LAN,

I still can\'t access my server through my external IP address: http://68.0.153.19/test/awesome.swf

 

Here are part of my http.conf, hope someone can help me figure out what\'s wrong?

 

 

#

# Listen: Allows you to bind Apache to specific IP addresses and/or

# ports, instead of the default. See also the <VirtualHost>

# directive.

#

# Change this to Listen on specific IP addresses as shown below to

# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

#

#Listen 12.34.56.78:80

 

Listen 80

#BindAddress *

 

 

 

 

### Section 2: \'Main\' server configuration

#

# The directives in this section set up the values used by the \'main\'

# server, which responds to any requests that aren\'t handled by a

# <VirtualHost> definition. These values also provide defaults for

# any <VirtualHost> containers you may define later in the file.

#

# All of these directives may appear inside <VirtualHost> containers,

# in which case these default settings will be overridden for the

# virtual host being defined.

#

 

#

# ServerAdmin: Your address, where problems with the server should be

# e-mailed. This address appears on some server-generated pages, such

# as error documents. e.g. admin@your-domain.com

#

ServerAdmin jyu1@u.arizona.edu

 

#

# ServerName gives the name and port that the server uses to identify itself.

# This can often be determined automatically, but we recommend you specify

# it explicitly to prevent problems during startup.

#

# If this is not set to valid DNS name for your host, server-generated

# redirections will not work. See also the UseCanonicalName directive.

#

# If your host doesn\'t have a registered DNS name, enter its IP address here.

# You will have to access it by its address anyway, and this will make

# redirections work in a sensible way.

#

ServerName 68.0.153.19:80

 

#

# UseCanonicalName: Determines how Apache constructs self-referencing

# URLs and the SERVER_NAME and SERVER_PORT variables.

# When set \"Off\", Apache will use the Hostname and Port supplied

# by the client. When set \"On\", Apache will use the value of the

# ServerName directive.

#

UseCanonicalName Off

 

#

# DocumentRoot: The directory out of which you will serve your

# documents. By default, all requests are taken from this directory, but

# symbolic links and aliases may be used to point to other locations.

#

DocumentRoot \"C:/Program Files/Apache Group/Apache2/htdocs\"

 

T.I.A :?: :?:

Share this post


Link to post
Share on other sites

1. are you sure the forwarding was setup correctly? make sure your computer\'s internal ip was used.

 

2. make sure your ISP does not block port 80.

 

3. double check for firewalls on your machine, or at the LAN router.

Share this post


Link to post
Share on other sites

I have setup several web servers in a similar way. I think the problem (as previosly mentioned) lies with your router. If you can access the webserver locally then it must be this. Port 80 needs to be allowed in through the firewall and the port must be forwarded to your local machine. Are you using a Netgear router? There are known problems with some models. I recommend http://www.alliedtelesyn.com

Share this post


Link to post
Share on other sites

Has anyone ever gotten a succesful trace or ping to that address? I know that I could not. ICMP may be turned off. If it is you may want to request that it is turned on while testing your server.

 

I would also reccomend dooing a traceroute out to the internet from that PC. The normal NAT or PAT setup should route in through the 68.0.153.19 as well as out.

 

A trceroute should show that as being one of the gateway address out.

 

Start here!

 

Shane J

Share this post


Link to post
Share on other sites

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.