NAT for VPN clients/Internet acess stops working after enabling Direct Access (Server 2019) RRS feed

  • Question

  • Hello. Server 2019 problem here:

    After enabling Direct Access, NAT for VPN users does not work anymore. Ping for Internet resource from server LAN IP also stops working (ping -S "Servers_LAN_NIC_IP").

    Can anybody comment on this "BUG" or "FEATURE"?


    This is not a topic about IPSEC, NAT-T.

    I want to have Direct access and Internet access for VPN clients without split tunneling. Server are with 2 NICS, Public IP on WAN.

    Without NAT feature I has no problem dealing with Direct access or/and VPN.

    After enabling Direct Access all NAT config are INTACT, as far as I can see it. It just stopped working.

    Wednesday, April 10, 2019 10:10 AM