Re: [FW1] Problem With NAT/Object Location

[cryptotech <cryptotech@FW1-NOSPAMgmx.de>]

I've never heard of that affecting NAT.  The indicator of Internal or External
simply refers to the objects administration (ie, the ability to push policy.)  Since
workstation objects (where firewall may be installed) would never require nat rules,
this is of no relevance.

More likely, check the ARP table setup, and the routing.

If you care to elaborate on the steps taken so far, perhaps I can be of more help.

Cheers

"Van Liere, Derek" wrote:

> For some reason, whenever I create a new Workstation object, the Location is
> grayed out and set to EXTERNAL.  The only way I can make this accessible is
> to mark that the object has an module installed, which it doesn't.
> Anyway... NAT isn't working as a result of this ( I think).  Anybody have
> any ideas??  I need to set these objects to internal.  BTW, I'm running
> FW2000 SP2 and is a new install on a test environment.
>
> Thanks!
>
> ================================================================================
>      To unsubscribe from this mailing list, please see the instructions at
>                http://www.checkpoint.com/services/mailing.html
> ================================================================================



================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================