Configure clients to access all networks
Posted: Sat May 14, 2011 8:02 am
Hi! Need some help getting VPN clients to access all resources on my domain.
I have three Cisco ASA gateways.
196.196.196.21 255.255.255.0
172.16.0.2 255.255.254.0
172.16.0.3 255.255.254.0
My OpenVPN server is installed on CentOS 5.5 and has an IP 172.16.0.248 255.255.254.0 which clients connect through the 172.16.0.3 gateway.
196.196.196.21 is a remote datacenter that has site-to-site connectivity with 172.16.0.2.
When my clients connect, they can access all resources on 172.16.0.x but cannot access anything on the 196.196.196.x network. In order for clients to connect to the second network, they first have to remote into their work PC, and from there remote into the second network.
My goal is to skip that step and give clients the ability to access the second network directly from their home computer. If they ping a host server on the second network from their home PC, DNS will resolve an IP address but does not get a reply. So it looks like I'm supposed to put a static route somewhere that points connected clients to the 172.16.0.2 gateway instead of the gateway they came through so that it routes properly but not sure how and where I go about to configuring this.
I'm only a Jr. Systems Admin who's just getting his feet wet. Help?
I have three Cisco ASA gateways.
196.196.196.21 255.255.255.0
172.16.0.2 255.255.254.0
172.16.0.3 255.255.254.0
My OpenVPN server is installed on CentOS 5.5 and has an IP 172.16.0.248 255.255.254.0 which clients connect through the 172.16.0.3 gateway.
196.196.196.21 is a remote datacenter that has site-to-site connectivity with 172.16.0.2.
When my clients connect, they can access all resources on 172.16.0.x but cannot access anything on the 196.196.196.x network. In order for clients to connect to the second network, they first have to remote into their work PC, and from there remote into the second network.
My goal is to skip that step and give clients the ability to access the second network directly from their home computer. If they ping a host server on the second network from their home PC, DNS will resolve an IP address but does not get a reply. So it looks like I'm supposed to put a static route somewhere that points connected clients to the 172.16.0.2 gateway instead of the gateway they came through so that it routes properly but not sure how and where I go about to configuring this.
I'm only a Jr. Systems Admin who's just getting his feet wet. Help?