I have the following setup:
A Windows Server 2019 VM, which is also the AD Domain Controller. It has a public IP. I want to set up a VPN (RRAS) where the users can connect to so they are in the local network.
I made a new private Virtual Switch for that in the Host.
So the DC has 2 Network interfaces, one with a public IP and one with a private range, where I set a static IP 10.20.30.1 with a netmask of 255.255.255.0. Then I set up a DHCP server there on the same machine. I told the DHCP Server to offer addresses in the range 10.20.30.2-254
The DHCP Server is working fine (I tested it with another VM which I plugged into the Virtual Switch, it got a lease without problem).
Now I want the RRAS to get leases from the DHCP to use for the clients. It was working fine one time (the RRAS got 10 leases, clients could connect, everything fine), but after a server reboot it is broken. It's like the RRAS can no longer talk to the DHCP. In the Remote Acces window it says that it could not get addresses for the VPN from the DHCP Server.
I am also a bit unsure about the configuration here.
I disabled the DHCP Relay Agent, because the DHCP is on the same machine - correct?
In the IPv4 Tab of the RRAS Settings where I have the choice between DHCP and static pool, I set it to DHCP. Does that automatically assume there is a DHCP up and running on the local machine? I suspect it might be asking the wrong interface - the DHCP is of course configured to only use the private Virtual Switch, so 10.20.30.1
As said - the DHCP seems to work fine, but the RRAS cannot communicate with it after the reboot.
Note: i do not want the network to route any traffic outside, so i don't want an internet connection over the VPN.
I am not even sure why it fails.