Re: Can't get to HTTP server on LAN behind WRT54G

Dennis <nobody@xxxxxxxxxxx> writes:

I am running an Apache server on my LAN behind my WRT54G. But I cannot
get to the server from other computers on the LAN.

The firewall's workin, then. :-)

Do I have to change a setting on the WRT54G?

Yes. You'll want to forward port 80 (and perhaps 443) to your
webserver's internal IP address.

--
Todd H.
http://www.toddh.net/
.

Relevant Pages

  • Re: Kazaa Block !
    ... >> security breach, but worse, it is a blatant abuse of work computers. ... >> If this is a home LAN, and these are your children, ground them first, ... >> block KaZaA from their computers, ... > goes over port 80. ...
    (comp.security.firewalls)
  • Re: Need advice with Remote Desktop Connection
    ... Let me first review - No problem doing a Remote Desktop Computer from ... within my LAN using either the computers internal IP address or its name. ... The problem seems to be that my remote port 3389 is being blocked external ...
    (microsoft.public.windowsxp.network_web)
  • What port(s) are required to use Remote Desktop Web Connection?
    ... I want to use the Remote Desktop Web connection to access two different ... I must open port 80 to get to the TSWeb application. ... to change the listening ports on the computers on the LAN. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Cant get to HTTP server on LAN behind WRT54G
    ... comphelp@xxxxxxxxx (Todd H.) writes: ... get to the server from other computers on the LAN. ... The firewall's workin, then. ...
    (comp.dcom.modems.cable)
  • Re: pf and ftp from gateway
    ... # ephemeral port, so that the remote SIP proxy knows what session we belong ... pass in quick on $ext_if inet proto udp from any port bootps to ... pass out quick on $ext_if inet proto udp from $ext_if to any port bootps ... # allow lan requests from lan clients to exit EXT ...
    (comp.unix.bsd.openbsd.misc)