Even "VPN Client" rules can be source-specific. Since you know the IP range for each, you can create subnets representing each and use them in the rules to separate them from each other. ..not exactly intuitive from a user standpoint, but it's how ISA 2004 was designed and actually works pretty well. BTW, I lost the SQL bitch-list you sent me before and the folks in Haifa are interested... ------------------------------------------------------- Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/Jim_Harrison/ http://isatools.org Read the help / books / articles! ------------------------------------------------------- -----Original Message----- From: Thor (Hammer of God) [mailto:thor@xxxxxxxxxxxxxxx] Sent: Friday, February 03, 2006 12:01 To: [ISAserver.org Discussion List] Subject: [isalist] Point-to-point VPN vs. Client VPN http://www.ISAserver.org Is there any super-secret way to present a point-to-point VPN connection to ISA 2004 differently than a regular client VPN connection, or are we forced to treat them both as "VPN Clients" and thus have everything on the client/end-point side all follow the same "VPN Client" rules? t ----- "I'll see your Llama and up you a Badger." John T ------------------------------------------------------ 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 ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx All mail to and from this domain is GFI-scanned.