Followup: Can't connect to anything on that machine, as long as I reference the forwarded/firewalled/external IP.
I had an idea that if I added forward lines to my firewall script that referenced eth1, like I did for eth0, that that might help, but it didn't seem to. Nerts...anyone? On Fri, 18 Jan 2002, Mike Burger wrote: > Ok...I'm at another little impasse, here. > > After moving my web/mail server from being its own firewall, to sitting behind > a dedicated firewall, I had to rework the httpd.conf file, to make it > know it was sitting on a different IP (doing name based hosting...most of > it is working, now). > > Now, however, the systems behind the firewall can't access the sites on the > server...ie, workstation at 192.168.0.3 can't access any of the sites hosted > on 192.168.0.1, because the DNS entries for those sites point them back > outside the firewall...it would seem that, while the outside world can get > through the firewall to get the sites, with no problem, the machines behind > the firewall can't go outside the firewall and then back in. > > Any ideas? > > Thanks. > > --Mike > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
