This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSLVPN not allowing single VPN subnet

I have an SSLVPN profile set up for my remote users

In the permissioned networks I have only our office supernet.

When connected to the SSLVPN I can reach other resources through our Site-to-Site IPSec VPNs. These subnets are not encompassed in our office supernet, and are not defined in our SSLVPN profile.

There is one Site-to-site IPSec VPN tunnel that I cannot reach while connected to the Client SSLVPN. When I do a packet capture I get an SSL VPN Violation.

I have a couple of questions:

1) Why is this subnet different than our other IPSec subnets? Am I missing a definition or a zone or a detail that would stop our firewall from allowing us to reach it? Any tips for a direction to start looking in would be greatly appreciated.

2) If I add this one VPN subnet to our SSLVPN Profile will all of my users have to re-download their config files again? This really isn't an option for me as I have hundreds of users.

Thanks for your time.



This thread was automatically locked due to age.