I had a similar issue which was resolved by using Windows Connection Manger to customize the client routing tables(installed via Add/Remove Programs | Windows Components |).
To troubleshoot, I would suggest looking at the routing table on the client before and after the VPN connection.
Do this w/ the "route print" command.
Secondly, try adding some manual routes to your other subnets. Once you have an idea of what routes you need, add them to the route table on the connection manager.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.