hey there -
so here is the problem. I have a lan to lan conenction between a remote office and my office. The lan to lan works great between the two networks, illustrated below:
172.16.1.x--concentrator--isp--concentrator--172.31.x.x.
we can pign back and forth, establish connections, etc. The problem arises when trying to talk to the other networks behind the vpn connected networks illustrated below:
172.16.1.x--concentrator--isp--concentrator--172.31.x.x.
| |
router router
| |
10.0.0.x 194.232.1.x
Trying to ping from 10.0.0.x to 172.31.x.x results in a timeout and vice versa. Also, pinging from 194.232.1.x to 172.16.1.x times out as well. I think this is a routing issue (must be) however I can't seem to figure out how to fix it. I thought of nat'ing addresses from the subnets to the vpn nets, but that seemed to me to be overkill. Any advice?
so here is the problem. I have a lan to lan conenction between a remote office and my office. The lan to lan works great between the two networks, illustrated below:
172.16.1.x--concentrator--isp--concentrator--172.31.x.x.
we can pign back and forth, establish connections, etc. The problem arises when trying to talk to the other networks behind the vpn connected networks illustrated below:
172.16.1.x--concentrator--isp--concentrator--172.31.x.x.
| |
router router
| |
10.0.0.x 194.232.1.x
Trying to ping from 10.0.0.x to 172.31.x.x results in a timeout and vice versa. Also, pinging from 194.232.1.x to 172.16.1.x times out as well. I think this is a routing issue (must be) however I can't seem to figure out how to fix it. I thought of nat'ing addresses from the subnets to the vpn nets, but that seemed to me to be overkill. Any advice?