You could try SSH sentinel (http://www.ssh.com) - there is a free download of the evaluation edition. That definitely supports NAT-T.
If your NAT is 1-1 then you can get away with without using NAT-T. Mark > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-l2tpd-devel@;l2tpd.org]On > Behalf Of Cressatti, Dominique > Sent: 13 November 2002 17:39 > To: [EMAIL PROTECTED] > Cc: Samag Alvarado > Subject: RE: client behind NAT > > > I've just read something and it said that what am trying to > do is NAT traversal (NAT-T) and in Windows camp only the > windows 2000 or XP as client support it. Windows 2000 server > doesn't. > > Basically they haven't implemented the latest version of IPSec > which support NAT-T while the current version of Freeswan does. > > Dom > > -----Original Message----- > From: Samag Alvarado [mailto:salvasa@;tiagris.net] > Sent: 13 November 2002 16:53 > To: [EMAIL PROTECTED] > Subject: RE: client behind NAT > > > Hi Dominic. > > Is NAT 1-to-1? If so, you shouldn't have any problem, else have a port 500 > udp forward to your internal Machine, and also protocol 50 and 51. > > > I haven't tried this, but I think should work. > > Regards > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-l2tpd-devel@;l2tpd.org]On > Behalf Of Cressatti, Dominique > Sent: Wednesday, November 13, 2002 8:44 AM > To: [EMAIL PROTECTED] > Subject: client behind NAT > > > Hi folks, > > as anyone got L2TP (with or without IPSEC) working behind > NAT? > > In more details my Windows client is behind a NAT box and > attempt to establish an L2TP tunnel to a Linux box. > > Dom > > > > > >
