Andrew- I had a similar problem, although luckily I caught mine in testing. I had to put both the external IP of the VPN concentrator and the Virtual IP/DHCP range that the concentrator assigns to the VPN clients in the VPN adaptive profile definition to get it to work. The only other glitch that I had was some clients who had older versions of the VPN client. Make sure that the client is up to date.
- - - - - - - - - Michael A. Vance, CISSP mailto:[EMAIL PROTECTED] >>> "Andrew Plato" <[EMAIL PROTECTED]> 01/31/2004 04:06:34 PM >>> 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 This E-Mail has been scanned for viruses. _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo
