Thanks Olaf,
Sounds promosing. We're playing with this solution right now - the only
difference I see between your and our situation is the fact that with us
both the client and the server are subject to translation. So may be we've
to create dummy interfaces on both machines.
Thanks and regards,
Jeroen
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 02, 2000 11:40 AM
To: [EMAIL PROTECTED]
Subject: [FW1] Workaround for RPC and NAT
We were faced with the same problem and that's the way my workmates created
a
workaround for this (I can't explain the whole way).
Access between the client and the RPC server is NATed two times: First on
the
firewall and second on a RadWare load balancer. On the target server (with a
private IP) we've defined a local loopback adapter with the IP address of
the
external virtual IP bound to the Firewalls external NIC for RPC access.
After
that we've told the application not to use the private IP of the server, but
to
use the official IP bound to the loopback - and what a surprise: It worked !
Cheers,
Olaf
============================================================================
====
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
================================================================================
