I have the VPN Client network configure for 192.168.5.130/26 (.129 thru .191)
I created access route to allow all outbound traffic from the VPN client network to the particular internal network I need them to access ( 192.168.5.0/26)
I created a second access route to allow all outbound traffic from internal network ( 192.168.5.0/26) to VPN client network ( 192.168.5.130/26) ( I found elsewhere on this site an example of someone successfully connecting both network without this second rule, I've tried with and without the second rule).
Clients (Windows 10) can connect to VPN network with no problem and gets IP 192.168.5.13x assigned as expected.
I ping FTMG server at 192.168.5.5 ( FTMG server has this specific IP address configured on that network card.)
but I can't ping the IP assigned on the Routing table for traffic going to 192.168.5.0 (see routing table below).
below is the Ipconfig readout from the client after connecting to VPN server.
Most documentation I have been able to find about VPN setup leave you with a "now just configure access rules and your are done!"...
Would it help if the VPN Client is on a totally different subnet like 192.168.10.x or even 10.0.0.x? not sure if the proximity in addresses may be causing routing issues.
any ideas on how to solve this are welcomed!
Thanks in advance.
IPCONFIG READOUT ************************************************
PPP adapter xxxxxx-VPN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : xxxxxxx-VPN
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.5.135(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.5.36
Primary WINS Server . . . . . . . : 192.168.5.36
NetBIOS over Tcpip. . . . . . . . : Enabled
*****************************************************************************
ROUTE PRINT READOUT *************************************************************************
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.124 10
66.151.243.100 255.255.255.255 192.168.1.1 192.168.1.124 11
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 169.254.80.80 261
169.254.80.80 255.255.255.255 On-link 169.254.80.80 261
169.254.255.255 255.255.255.255 On-link 169.254.80.80 261
192.168.1.0 255.255.255.0 On-link 192.168.1.124 266
192.168.1.124 255.255.255.255 On-link 192.168.1.124 266
192.168.1.255 255.255.255.255 On-link 192.168.1.124 266
192.168.5.0 255.255.255.0 192.168.5.129 192.168.5.135 11
192.168.5.135 255.255.255.255 On-link 192.168.5.135 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 169.254.80.80 261
224.0.0.0 240.0.0.0 On-link 192.168.1.124 266
224.0.0.0 240.0.0.0 On-link 192.168.5.135 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 169.254.80.80 261
255.255.255.255 255.255.255.255 On-link 192.168.1.124 266
255.255.255.255 255.255.255.255 On-link 192.168.5.135 266
===========================================================================
Persistent Routes:
None
***********************************************************************************************
Performance, Reliability and Automation!