VPN routing with private IP's

[Roger Poore]

Let's get this party started....

• Windows 2012 R2
• nic1 = public IP = 142.10.100.0/24
• nic1 gateway = 142.10.100.1
• nic2 = private IP = 172.25.100.0/24
• VPN issuing the range 172.25.100.10 to 172.25.100.90
• VPN server only---no Direct Access
• Lab server = 172.25.100.100
• Our networking team has set up routes in the routing table for the private network

I am not a networking person.  Just want to get that out there.  I'm setting up a VPN server for some of our students to use in order to connect to labs remotely.   I can connect to the VPN server and I get issued 172.25.100.11.  But I can't go anywhere.  Trace route shows the next hop as 172.25.100.10 (the start of the VPN client IP range).  I can ping that but that's it.  I'm assuming that the VPN server configures that first IP in the client range as the gateway for VPN connections.  Yes/no/maybe?  That seems to be the behavior anyway. 

I've tried various static routes on the VPN server to no avail.  The networking team seems to the think it's an issue on their end having to do with VLAN tagging but I think it's an issue with the VPN server and its routing.    Either way, all I know is that it doesn't work. 

I'm going to install wireshark and see what I can see but I thought I'd just go ahead and ask here.  Plus, I get to be the first poster in the Windows Server Networking space!!

[#2]

Hi Roger,

Have you tried verify if your VPN Client are using Remote Network Gateway?

Check this link below and see if it can provide you some troubleshooting thoughts:

https://blogs.technet.microsoft.com/sbs/2014/06/11/troubleshooting-common-vpn-issues-on-windows-serv...

And great, I get to be the first responder in the Windows Server Networking space. :)

[#3]

Hi Ryen,
I don't see "MVP" near your name or my :)
Maybe I'm missing something...
Still examines the interface 

[#4]

---

@R A wrote:

Hi Ryen,
I don't see "MVP" near your name or my :)
Maybe I'm missing something...
Still examines the interface 

---

Hi Ronen,

We may just have to wait... Hopefully before it goes live to public.

[#5]

Oh man, I completely forgot about this.  Thanks for being the first responder @Ryen Tang.  Yeah, I saw that link.  We ended up using public IP's and moved on.  Thanks again for responding though.