Try doing some SNAT on the output of the VPN server to the Win 2000 server. This will address the packets back to the VPN server rather than their true source.
Regards, Peter Monday 07 October 2002 01:27, you wrote: > Bump, anyone? > -----Original Message----- > Hi, > > I have been stuck on this for a while, any help really > appreciated! > > I have the following scenario: > > VPN Client <> Untrusted network <> Firewall (RH) <> VPN > Gateway (RH 7.3) <> Windows 2000 Server > > The default gateway for the Windows 2000 server is the > VPN Gateway, as it needs to be. The default gateway for > the VPN gateway is the firewall. Redhat 7.3 has port > forwarding enabled and reverse path filtering disabled, > as required by the Freeswan VPN product. > > When a VPN Client establishes a VPN connection and > communicates with the Win2000 Server, Redhat seems to be > telling the Win2000 server that the default gateway to > get the the VPN client is the firewall (rather than > itself!). So Windows updates it's route table and puts a > route to the VPN client with the firewall (incorrectly) > as the default gateway. I then have to manually delete > the route on the Win2000 server, and everything is fine > after that. > > How can I get Redhat to stop advertising to the Win2000 > Server that the default gateway is the firewall? It must > be Redhat telling the Win2000 server to add the firewall > as the gateway, as the Win2000 server does not refer at > all to the firewall in its tcp/ip config. > > Any help MUCH appreciated! > > Thanks, > > Alistair -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
