× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Tue, 27 Nov 2001, Richard Bryant wrote:

> The ip is 192.168.2.2 and mac 45:00:00:00:02:00 for the virtual and
> 192.168.2.1 for the firewall. I have come up with a workaround from Symantec
> which is to change the severity of the message in the level.cf file to info.
> I still would like to know how other shops are dealing with the problem.

Well what we are doing probably doesn't help you since we aren't using
Symantec.  I don't know if you require that Symantec be your firewall.  We
use a linux box as the firewall and have a DMZ network and a private
network.  The firewall is pretty nice with linux 2.4 since it is now a
stateful firewall.  On the private network we do IP masquerade.  We could
use DHCP but since we don't have many machines we haven't found it
necessary.

I don't know if that addresses the problem you asked about or if you are
only looking for responses involving Symantec firewalls.  As for the NT
host I can't see any reason why the configuration I mentioned above would
complain about it.

James Rich
james@eaerich.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.