locked
Home Lab With RRAS RRS feed

  • Question

  • Hello everyone,

    This is my first time ever using Technet to ask for help.  I've been struggling with setting up a lab environment for the past couple of days.  I've read numerous articles and reconfigured my settings multiple times, but I'm unable to achieve the results that I want.  Here is my scenario:

    Cable Modem > Netgear Router > Private Network (10.0.0.0)(DHCP is enabled on the Netgear router)

    I have a physical server, with two NICs, running Server 2012 R2 with Hyper-V and RRAS.  The first NIC is connected to my private network.  The second NIC is configured to use a static IP of 192.168.0.1/24 with no DG and no DNS.

    I have a Hyper-V virtual machine that I've configured as a domain controller connecting to the second NIC on the physical server.  The domain controller has DNS and DHCP configured.  I have configured RRAS to use NAT and IPV4 forwarding is enabled.  I have two static routes on the RRAS, one for the first NIC (10.0.0.0) that routes to 192.168.0.0 255.255.255.0 192.168.0.1.  The second static route is for the second NIC (192.168.0.0) that routes to 10.0.0.0 255.255.255.0 10.0.0.1.

    At this time, I am unable to get a connection to the Internet, or ping my private network from my DC.  What am I doing wrong?

    Saturday, October 15, 2016 1:10 PM

Answers

  • I'd connect the VMs to the external switch and work from there. Have you ever created an active directory domain? If not then that's really another topic and should go in a new thread. This one may help with that.

    http://social.technet.microsoft.com/wiki/contents/articles/12370.windows-server-2012-set-up-your-first-domain-controller-step-by-step.aspx

     Once you have the domain setup and functional you can to move it to the internal network and create the virtual router to connect to the external network.

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Proposed as answer by John Lii Monday, October 31, 2016 6:28 AM
    • Marked as answer by Leo Han Wednesday, November 2, 2016 5:16 AM
    Sunday, October 16, 2016 9:13 PM

All replies

  • It isn't recommended to install other roles on a hyper-v host. Also never recommended to multi-home a domain controller as this will cause you no end to grief (as you've found). Better to install active directory domain services on a VM guest. Then stand up other VMs to host other applications. If you want the guests to have internet then you can connect them to an external vSwitch. You don't need RRAS for that.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Saturday, October 15, 2016 1:52 PM
  • I guess I didn't explain my setup clearly enough.  My domain controller is on a VM guest.  It's running as a VM on my Hyper-V server, the physical box.  Is that what you meant?  As for the external vSwitch, should I point that to my second NIC?  Will I be able to communicate between the two networks that way?
    Saturday, October 15, 2016 2:04 PM
  • This one might help. It is for 2008 but still applies.

    https://blogs.technet.microsoft.com/jhoward/2008/06/16/how-does-basic-networking-work-in-hyper-v/

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Saturday, October 15, 2016 2:17 PM
  • Thanks, Dave.  I read that article several times over and I'm still not clear on how the networking needs to be configured.  The end result that I'm looking for, is to have two separate networks that are able to communicate to each other.  One network will be a workgroup, the other a domain.  Right now, I have my two physical NICs on the Hyper-V server.  I have an external virtual switch that is pointed at my second physical NIC.  Here's where I am confused.  What do I set the IP address/DG/DNS on this switch to use?  I'm assuming that I will create a new adapter for each VM that will be "internal" and they will use the IP address of the virtual switch as their DG and DNS.  But, I plan to create a VM that will have DNS and DHCP installed so that it will handle all of the IP assignments for my VMs.
    Sunday, October 16, 2016 1:23 PM
  • Right now, I have my two physical NICs on the Hyper-V server.  I have an external virtual switch that is pointed at my second physical NIC.  Here's where I am confused.  What do I set the IP address/DG/DNS on this switch to use? 

    You cannot assign an IP to a physical NIC associated with an External Virtual Switch The IP protocols are no longer present on the physical adapter.

    When you check "allow management OS to share" in the Setting of a Virtual Switch (Network) - a virtual NIC is created for the management OS (the Hyper-V Server) on this Virtual Switch. This allows the management OS and VMs to share the same physical NIC.  This virtual NIC is named 'vEthernet' in the Network Adapters list. An IP address is not assigned to a virtual switch.  It's always assigned to a NIC (physical or virtual).

    Also something here may help on the routing.

    http://deploymentresearch.com/Research/Post/285/Using-a-virtual-router-for-your-lab-and-test-environment

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 1:38 PM
  • Right, I know about the physical NIC won't be configured with an IP.  However, I did not realize that the vEthernet (External Switch) should not have an IP as well.  So, how do I prevent this from getting an IP?  Do I uncheck IPv4 and IPv6 under it's properties?  Right now, it has an APIPA address, and so does my virtual internal NIC on my first VM.

    • Edited by T4RH33L Sunday, October 16, 2016 1:49 PM
    Sunday, October 16, 2016 1:48 PM
  • Sorry, a bit confusing but vEthernet is the virtual NIC for the host and would have an address. See Brian's last comment here about how hyper-v and parent OS load. The vEthernet is for the parent OS

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/b4a05b26-e4dc-4bd9-aaef-64f31d2e48ce/is-there-a-hypervisor-type-1-for-windows-2016-server-hyperv?forum=winserverhyperv#75ca5977-5c0f-4387-9f9d-6aac691ce844

     

     

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 2:02 PM
  • Okay, so do I give the switch a static IP or leave it as DHCP?
    Sunday, October 16, 2016 2:10 PM
  • Switches do not have addresses, only virtual and physical NICs can have addresses.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 2:14 PM
  • LOL, this is driving me crazy.  Let me back up again.  I have the vEthernet (external swtich) that's connected to my second NIC.  If I leave it alone after creating it, it is configured by default to "obtain an IP address automatically".  I know that this is the switch, but after the initial configuration, it looks like a NIC and therefore it gets an IP.  I can see it's address when I run ipconfig /all.  Now, did I not set this up right?
    Sunday, October 16, 2016 2:18 PM
  • vEthernet is a virtual NIC for the host OS; it is bound to your hyper-v external switch. Your external switch is probably now plugged into your internet router and is allowing vEthernet to get an address assigned via DHCP. vEthernet can be setup static or DHCP, it really just depends on your setup and topology. I myself make almost all my servers static, especially the hyer-v hosts and of course all domain controllers. I do test a lot with virtual servs so I might just leave them DHCP depending on what I'm testing with.

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 2:28 PM
  • I really do appreciate you taking the time to reply to my posts and for being patient with me while I try to understand this.  But, I feel like I'm now more confused than when I first posted.  What should I do to get a more clear picture to you so that you can point out what is causing my issues?  Because, at this point, I'm ready to concede defeat.
    Sunday, October 16, 2016 2:34 PM
  • Deploying a project cradle to grave in forums posts is difficult if not impossible to do. There's a lot of good info in TechNet knowledge base and online. Plus virtual labs here.

    https://technet.microsoft.com/en-us/virtuallabs

    Free training here.

    https://mva.microsoft.com/

     https://mva.microsoft.com/en-US/training-courses/windows-server-2012-r2-virtualization-8279?l=oMjgewWy_3804984382

    https://mva.microsoft.com/en-US/training-courses/server-virtualization-with-windows-server-hyperv-and-system-center-8268?l=fRy5r6Ky_6004984382

     I'd suggest to try in smaller tasks. Get comfortable with that and move on to next task.

    You can hook your existing VMs to external switch for now to get internet access.

     To configure windows as a router you can follow along here.

    http://www.dell.com/support/article/us/en/19/HOW10169/EN

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.



    Sunday, October 16, 2016 2:52 PM
  • That's the thing, I'm not getting Internet access when I connect them to that External switch.  I'm going to map out everything I have, with as much detail as possible and see if that will help paint a better picture.
    Sunday, October 16, 2016 7:28 PM
  • Please post an unedited ipconfig /all of the DC and problem client.

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 7:30 PM
  • Can I get an email address to send this to?  Apparently I have to "verify my account" in order to post images.
    Sunday, October 16, 2016 8:19 PM
  • Better to not post as image as it would be difficult to read. Just run below and paste resulting text in reply.

    ipconfig /all > C:\dc.txt

    ipconfig /all > C:\client.txt

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 8:22 PM
  • I had some images that I made that illustrated how I have my network currently configured.  I'll post that when my account is taken care of.  For now, here are the ipconfig results:

    Hyper-V server (Physical)

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : AWH-SRV-1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : southeast.rr.com

    Ethernet adapter vEthernet (Internal):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-15-5D-00-12-08
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d81f:7fe9:bad6:1366%42(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.19.102(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 704648541
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-91-5A-BD-00-23-7D-DC-4E-3E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter vEthernet (External):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 00-14-D1-20-93-11
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Autoconfiguration IPv4 Address. . : 169.254.21.20(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter NIC_0:

       Connection-specific DNS Suffix  . : southeast.rr.com
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
       Physical Address. . . . . . . . . : 00-23-7D-DC-4E-3E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2606:a000:1127:4110:a1c3:2262:706f:5d04(Preferred)
       Link-local IPv6 Address . . . . . : fe80::a1c3:2262:706f:5d04%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.0.0.99(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::c63d:c7ff:fe8c:ce98%12
                                           10.0.0.1
       DHCPv6 IAID . . . . . . . . . . . : 301998973
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-91-5A-BD-00-23-7D-DC-4E-3E
       DNS Servers . . . . . . . . . . . : 2001:1998:f00:1::1
                                           2001:1998:f00:2::1
                                           10.0.0.1
                                           8.8.8.8
       NetBIOS over Tcpip. . . . . . . . : Enabled
       Connection-specific DNS Suffix Search List :
                                           southeast.rr.com

    Tunnel adapter isatap.{ADBE7592-618D-468F-BE5F-3523E0919753}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : southeast.rr.com
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{392E5A97-3AAB-40BE-8840-AC2C3497BDEA}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{40C61EDA-4C16-4EB1-A41F-82337D76E084}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Domain Controller (VM)

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : AWH-SRV-1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : southeast.rr.com

    Ethernet adapter vEthernet (Internal):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-15-5D-00-12-08
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d81f:7fe9:bad6:1366%42(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.19.102(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 704648541
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-91-5A-BD-00-23-7D-DC-4E-3E
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter vEthernet (External):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 00-14-D1-20-93-11
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Autoconfiguration IPv4 Address. . : 169.254.21.20(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter NIC_0:

       Connection-specific DNS Suffix  . : southeast.rr.com
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
       Physical Address. . . . . . . . . : 00-23-7D-DC-4E-3E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2606:a000:1127:4110:a1c3:2262:706f:5d04(Preferred)
       Link-local IPv6 Address . . . . . : fe80::a1c3:2262:706f:5d04%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.0.0.99(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::c63d:c7ff:fe8c:ce98%12
                                           10.0.0.1
       DHCPv6 IAID . . . . . . . . . . . : 301998973
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-91-5A-BD-00-23-7D-DC-4E-3E
       DNS Servers . . . . . . . . . . . : 2001:1998:f00:1::1
                                           2001:1998:f00:2::1
                                           10.0.0.1
                                           8.8.8.8
       NetBIOS over Tcpip. . . . . . . . : Enabled
       Connection-specific DNS Suffix Search List :
                                           southeast.rr.com

    Tunnel adapter isatap.{ADBE7592-618D-468F-BE5F-3523E0919753}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : southeast.rr.com
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{392E5A97-3AAB-40BE-8840-AC2C3497BDEA}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{40C61EDA-4C16-4EB1-A41F-82337D76E084}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes


    • Edited by T4RH33L Sunday, October 16, 2016 8:42 PM
    Sunday, October 16, 2016 8:41 PM
  • The hyper-v host does not matter. Need the DC and problem client ipconfig /all output.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Sunday, October 16, 2016 8:44 PM
  • I thought that I had copied the contents of the DC file, but apparently I pasted the same text twice.  I cannot pull the DC.txt content and paste it here.  I think its a limitation of the VM.

    Sunday, October 16, 2016 8:48 PM
  •   I cannot pull the DC.txt content and paste it here.  I think its a limitation of the VM.

    From another desktop on the lan you can navigate to the admin share.

    \\mydcname\c$

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 8:55 PM
  • Yeah, I tried that.  The DC is in it's own separate network and I can't connect to it unless from the console on the Hyper-V server.  Which is why I've been going through all of this trouble to begin with. 
    Sunday, October 16, 2016 8:57 PM
  • I thought at last it was connected to external network. You're tearing off too big a chunk. I'd get it working via external network before moving on.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 9:00 PM
  • No, it's not.  That's what I've been trying to accomplish all along.  I'm trying to use my second physical NIC to allow my virtual machines to have external network access.
    Sunday, October 16, 2016 9:02 PM
  • You're starting at the end and working backwards. Makes things infinitely more difficult.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Sunday, October 16, 2016 9:03 PM
  • Okay, so where do I need to begin?  I have my Hyper-V server with two physical NICs.  I have a single VM running, but with no external network access.  How do I set up this environment to get that access?
    Sunday, October 16, 2016 9:07 PM
  • I'd connect the VMs to the external switch and work from there. Have you ever created an active directory domain? If not then that's really another topic and should go in a new thread. This one may help with that.

    http://social.technet.microsoft.com/wiki/contents/articles/12370.windows-server-2012-set-up-your-first-domain-controller-step-by-step.aspx

     Once you have the domain setup and functional you can to move it to the internal network and create the virtual router to connect to the external network.

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Proposed as answer by John Lii Monday, October 31, 2016 6:28 AM
    • Marked as answer by Leo Han Wednesday, November 2, 2016 5:16 AM
    Sunday, October 16, 2016 9:13 PM
  • Hi, 

    Have you manage to get your issue resolve? I seems to have the same issue like yours.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/2ec44d4c-b6e6-4407-b2eb-675699cbfe89/home-lab-with-rras-nat-and-lan-routing?forum=winserverhyperv

    Thursday, July 12, 2018 9:03 AM