The system requirements for RealSecure Desktop list the supported VPN clients.
http://documents.iss.net/literature/RealSecure/RSD_SysReqs.pdf -----Original Message----- From: [EMAIL PROTECTED] On Behalf Of Andrew Plato Sent: Monday, February 02, 2004 2:15 PM To: Hackenson, Jack E - Raleigh, NC Cc: [EMAIL PROTECTED] Subject: RE: [ISSForum] Problems with adaptive profiles for RS Desktop Really? How come this isn't documented anywhere? ___________________________________ Andrew Plato, CISSP President / Principal Consultant Anitian Enterprise Security 503-644-5656 Office 503-214-8069 Fax 503-201-0821 Mobile www.anitian.com ___________________________________ > -----Original Message----- > From: Hackenson, Jack E - Raleigh, NC > [mailto:[EMAIL PROTECTED] > Sent: Monday, February 02, 2004 9:50 AM > To: Andrew Plato > Subject: RE: [ISSForum] Problems with adaptive profiles for RS Desktop > > When we had this issue in December 03, the problem was the VPN client. > Adaptive policy for VPN, according to ISS, is only supported > for the following VPN clients: > Cisco 35. and 4.0.1 > Nortel 4.15 and 4.65 > Secure Remote (CheckPoint) NG FP3 > We verified that Cisco 4.0.1 worked. It is a registry key issue. > > Jack E. Hackenson, CISSP > USPS - Corporate Information Security Office [EMAIL PROTECTED] > (919) 501-9337 > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Andrew Plato > Sent: Saturday, January 31, 2004 4:07 PM > To: [EMAIL PROTECTED] > Subject: [ISSForum] Problems with adaptive profiles for RS Desktop > > I've been working with ISS support on this issue but they do > not have a solution yet. I have numerous furious customers so > I thought I'd see if anybody else is experincing these issues. > > I have a whole collection of customers who cannot get > Adaptive Profiles working. The problem is the VPN group. > > The documentation says to use the external IP of the VPN > concetrator/firewall for the VPN adresses for the VPN > adaptive profile. > But when we use this, it doesn't work. Agents on VPN > connections remain in default. > > So, we tried putting the Virtual IP range assigned to the VPN > clients into the VPN rules. Nothing, remains in default. > > What's weird, is that when we put the virtual range into > corpnet - the agent switches into corpnet just fine. > > Has anybody seen this behavior. Do you have ANY suggestions? > > Thanks. > > ___________________________________ > Andrew Plato, CISSP > President/Principal Consultant > Anitian Enterprise Security > > 503-644-5656 Office > 503-214-8069 Fax > 503-201-0821 Mobile > www.anitian.com > ___________________________________ > > _______________________________________________ > ISSForum mailing list > [EMAIL PROTECTED] > > TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to > https://atla-mm1.iss.net/mailman/listinfo > > _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo
