Hi Tim,

Thanks for your suggestions. I tryed almost all of it before I posted
but had no luck. Then I decided to reboot the linux box (firewall) and
was greeted by a pleasant surprise. The routing simply worked
strqaight away. I dont know how the reboot affected the setup but now
all routing and IPTABLES functions work fine.

I forgot to mention that I am also performing some bandwidth measuring
on the gateway machine with NTOP so I am suspecting that it could have
had some effect on the routing.

Either way, its all working now.

Thanks again for your suggestions.

Roberto



px9900i@yahoo.com (TN) wrote in message news:<52c69394.0408191835.25638a5@posting.google.c om>...
> Hi Roberto,
>
> Ah, so you have a puzzle, too, eh? I think what I would do first is
> run tcpdump on the internal LAN to see what kind of traffic is being
> generated when a local user tries to connect to the remote VPN site.
> That should provide some clues. You can then try to track things down
> by running tcpdump on the internal and external interfaces of the VPN
> server and/or the gateway machine until you find where the traffic is
> being stopped. You might also want to turn on logging for dropped
> packets on your gateway machine -- then you could see if Netfilter is
> the culprit, and what to do about it. My personal bias is always to
> suspect the Microsoft components, though ;-)
>
> Tim