NAT not working after enabling DirectAccess

direct-accessnat;vpnwindows-server-2012

following test setup is given:

server1 – 1 network card connected to internal network (10.0.0.2/24) + gateway 10.0.0.1

server2 – 2 network cards (1. connected to internal network (10.0.0.1/24) / 2. connected to the internet with static ip address + default gateway is set)

Both servers can ping each other, server2 can ping addresses in the internet.

I installed the "Remote Access" role on server2 with the "Routing" option. Enabled NAT in the RRAS Manager and selected network card 2 as internet access card.

-> server1 can now ping addresses in the internet via NAT on server2.

But as soon as i run the DirectAccess configuration manager an enable DirectAccess+VPN on server2 NAT stops working. The configuration in the RRAS Manager still exists.

Any idea why?

The goal is to have an internal network where each server can access the internet via NAT and one server acts as VPN/DirectAccess server+NAT Router.

Best Answer

Just had this same issue on a 2012 server for a client. Originally had NAT setup, and then later setup VPN. VPN worked, but NAT stopped working. Fixed it by disabling/removing remote access from the "remote access management console" and then going back to "routing and remote access" via the server manager > tools screen, and re-setting up from there via the wizard. (I selected VPN and NAT as the features I wanted to enable.) When done together like this, it worked.

Related Topic