We have a Juniper Netscreen SSG 140 that is connected to our ISP connection. We are using the recommended Juniper VPN client for Windows XP / Vista (it does not work on Windows 7 yet). Our offsite users need to access BOTH our Corporate office and our local office. Our remote users could connect to our corporate office via VPN OR they can connect to the local office via VPN. When they connect to the Corporate VPN, it routes the traffic to the local office. I believe the Corporate VPN is able to redirect the traffic to both 10.x (Corporate), and 192.x (US) networks. But, it does not work the other way around. Our local VPN client is not able to route the traffic to the 10.x (Corporate) network.
When people need access to both the networks, they are forced to come through the Corporate VPN, and that becomes too slow. Life would be lot easier if they could VPN into the local office and from their local VPN, utilize the fixed tunnel to the corporate network.
We do have a permanent / fixed VPN connection to our Corporate (10.x) network. This is because our Network hardware is already configured for the fixed tunnel. So, when some one is inside our local office -- connected inside the local network – they can reach the corporate network without needing any additional tool. But, when they are remote -- connecting via the VPN – they can’t reach the corporate 10.x network.
Is this a VPN client problem? OR Do we need something configured differently on our Juniper VPN gateway?
Is it possible that; the Corporate VPN client is setup to redirect both 192.x and 10.x. But, our local Juniper client is only setup to redirect 192.x and not setup to redirect 10.x…?
If this is a VPN client issue, can we use a different VPN client (instead of the Juniper client) to get over this issue?
What would be your advice for a possible solution…?