Uh, yeah.  I'm trying to connect to my webserver and news server from my
work computer at my office.  I figured I wouldn't need to mention that,
but I guess I do.

So to be more clear, from OUTSIDE my firewall, I cannot connect to my
webserver.  Instead of the firewall forwarding the requests to the
appropriate server, the firewall's web server is what I'm getting.

Thanks,

Michael 

 -----Original Message-----
From:   [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]  On Behalf Of John
Johnson
Sent:   Tuesday, April 03, 2001 8:23 PM
To:     [EMAIL PROTECTED]
Subject:        Re: [Cooker-firewall] Config problem


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

  I think you need to be outside your firewall to test this properly.

- -John


At 08:08 PM 4/3/2001 -0500, you wrote:
>First, I had a problem a few weeks ago getting Mandrake Security to let
>me on the Internet.  It took me awhile to find the time to get back to
>this, but I was able to fix it.  I found that the problem was with my
>DNS server not resolving names to addresses correctly.  Anyway, I think
>a couple of people from Mandrake were waiting to hear back from me so
we
>could figure out if this were a bug.  Just wanted to say it's not, it
>was my error.
>
>Now for my next problem. :-)  Now that I have the firewall working, I
>enabled outside access to my web server, or at least I thought I did.
>My web server runs on a separate server (Linux/Apache of course) at ip
>address 192.168.1.2.  I set up Internet Access to allow port www and
>told it to forward to 192.168.1.2, but it does not work. When I go to
>the external IP address in a web browser, I get the webserver running
on
>the firewall instead of on 192.168.1.2.  Can I shut down httpd on the
>firewall without any problems?  I know I would need httpd-naat to use
>the NAAT tool, but what about just httpd?  Also, I set up port nntp
>forwarding to the same server, and it doesn't work either.
>
>
>Can somebody help me out with this one?  I haven't done port forwarding
>like this before, so I'm not real sure what to do in the first place.
>
>Thanks,
>
>Michael

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.1

iQA/AwUBOsp3dQfP+qzR55XlEQJspgCgyX14+dBnJXXmMvmeXkJVnqy9sVQAniLj
4sp/J5qF9fkDBokPlKGEUMMm
=BDI8
-----END PGP SIGNATURE-----


Reply via email to