Hi Greg, The problem with SOHO and other proprietary IPSec VPN protocols is they require pre-shared keys, which are subject to XAUTH attacks and in general sUX0rs. That's why I always get a kick when folks hammer on that the Cisco VPN is more secure. That's a load of ******. Anyhow, you can use pre-shared keys if you must, or you can use PPTP. Rainbow tables can break 14 char passwords pretty quick now. Try 16+ char plus passwords with your PPTP connections and you'll be OK for awhile. HTH, Tom www.isaserver.org/shinder Tom and Deb Shinder's Configuring ISA Server 2004 http://tinyurl.com/3xqb7 MVP -- ISA Firewalls -----Original Message----- From: Greg M. [mailto:gmcmonagle@xxxxxxxxxxxxxxx] Sent: Friday, March 04, 2005 12:34 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: (PPTP) VPN on XP Client http://www.ISAserver.org I used L2TP in the past and I wasn't able to find a personal router that would correctly support the protocol. I tested several that claimed to support it but they didn't work (Linksys, Netgear and Motorola). Do you have any recommendations? ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx