gateway and subnets are correct ( /24) , using IP addresses (not relying on dns) , and I CAN ping back and forth between subnets
going to check logs next Date: Sun, 11 Jan 2015 12:10:17 -0800 Subject: Re: [NTSysADM] VPN connectivity oddity From: [email protected] To: [email protected] What are your VPN endpoints? Can you do a tcpdump from them? If so, make sure that the packets are at least transiting them. If that isn't available, you can fall back on traceroute. Also, can you ping from the target subnet to the source subnet? And, do make sure, as Charles mentioned, that the subnet masks for each machine are correct, and don't overlap. Kurt On Sun, Jan 11, 2015 at 10:53 AM, J- P <[email protected]> wrote: So on my site to site vpn to one of my clients, I'm running into a baffling issue Home lan 192.168.4.0 remote/vpn lan 192.168.0.0 I CAN remote/ping into a server A which is 2012r1 with IP 192.168.0.12, however, I CANNOT remote/ping to server B which is 2012r1 with IP 192.168.0.5 So to get to server B, I have to remote into server A and do rdp from server A to get to server B (which also shows that RDP and ports etc.. are enabled) I have checked both firewalls (all controlled by domain policy) I have even tried disabling the firewall as well with no success. Both servers are plugged into the same switch, same OS, same patch level. I'm a bit stumped on this one, even though it's not a HUGE inconvenience to RDP from one server to the other, I still want to know WHY this is occuring TIA
