Cable Forum - View Single Post

Trident · 27-03-2010, 16:02

@ Rob

I don’t think it’s an internal IP routing issue as I can’t even establish the VPN. Also as you can see from the tracert A's internal IP range is 10.13.x.x/16 and B's internal IP range is 192.168.20.x/24, so there is no conflict there.

@ Jon T

Yes both A and B's WAN IP's can be pinged from the TalkTalk connection. Just not between each other. I have got another site, Connection C, and this has a two separate VPN's. One to A and one to B. So I can actually route between A and B but only through C. Unfortunately this is not a workable solution!

On a separate note I do have IPSec enabled on both A and B's LANs for all internal network traffic but this shouldn’t be a problem, but I think it is still worth mentioning. (C also has IPSec enabled and it can establish a VPN to both A and B.)

27-03-2010, 16:02	#8
Trident Inactive Join Date: Mar 2010 Posts: 11	Re: VPN Between two VM Connections @ Rob I don’t think it’s an internal IP routing issue as I can’t even establish the VPN. Also as you can see from the tracert A's internal IP range is 10.13.x.x/16 and B's internal IP range is 192.168.20.x/24, so there is no conflict there. @ Jon T Yes both A and B's WAN IP's can be pinged from the TalkTalk connection. Just not between each other. I have got another site, Connection C, and this has a two separate VPN's. One to A and one to B. So I can actually route between A and B but only through C. Unfortunately this is not a workable solution! On a separate note I do have IPSec enabled on both A and B's LANs for all internal network traffic but this shouldn’t be a problem, but I think it is still worth mentioning. (C also has IPSec enabled and it can establish a VPN to both A and B.)