- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-21-2011 10:32 AM
I have noticed that when I connect to the SSL VPN the Split tunnelling restriction I have in place doesn't seem to be working any longer. I recently upgraded from 3.1.6 to 3.1.8. I also upgraded my laptop client to NetConnect 1.3. When the VPN is connected and I go to www.whatismyip.com, I don't see my FW external interface address anymore but rather the address of my broadband card.
I seem to be able to get to some internal resources by UNC name, but any internal web servers are not available. My SSL-VPN Client configuration has a split-tunnelling access route of 0.0.0.0/0. Shouldn't that disable the split tunnelling ability of connected clients?
Thoughts?
Mike
04-21-2011 11:48 AM
I guess this is a 'nevermind" case. I removed the 0.0.0.0/0 route, committed the change, re-inserted it again, committed that change, restarted my laptop and it works again. Not sure if any of the above actually did the trick, though.....
Mike
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!