Symantec 100 VPN/Firewall NAT?

Archived from groups: comp.security.firewalls (More info?)

Hi all,

We have a Symantec 100 VPN/Firewall utilising NAT on our network. The
problem we have is that NAT is stripping the internal network address
completely out of the header of the packet, and our web based application
shows the clients IP address from behind the Symantec as the public NAT ip
address. We have tried other firewalls, e.g. Linksys, Netgear and standard
Windows XP Pro machine and they display the private IP address e.g.
192.168.0.100. Is there anything I can change on the Symantec 100? Also if I
replace the Symantec with a Cisco Pix will I still have the same problem?

Thanks in advance,

Kev

Archived from groups: comp.security.firewalls (More info?)

Kevin Howell wrote:

> Hi all,
>
> We have a Symantec 100 VPN/Firewall utilising NAT on our network. The
> problem we have is that NAT is stripping the internal network address
> completely out of the header of the packet, and our web based application
> shows the clients IP address from behind the Symantec as the public NAT ip
> address. We have tried other firewalls, e.g. Linksys, Netgear and standard
> Windows XP Pro machine and they display the private IP address e.g.
> 192.168.0.100. Is there anything I can change on the Symantec 100? Also if I
> replace the Symantec with a Cisco Pix will I still have the same problem?
>
> Thanks in advance,
>
> Kev

That is what NAT does - it strips out the internal IP and replaces it
with the public IP. ALL NAT firewalls will do that - be they symantec,
cisco, linksys, netgear, watchguard, sonicwall, firewall1, etc. etc.

The only way NOT to have that happen is to not use NAT. But then the
boxes accessing the intyernet all must have public IP's, not private IP's.