RRAS DHCP Not working on VM

[ITGURU]

I'm migrating RRAS from 2016 to 2019. 2016 install had no issues at all , can VPN with DHCP selected on the settings.

However, after setting up the 2019 virtual server and setting up in exactly the same way, clients that try to connect to the server fail, as they don't get a DHCP address.

If within RRAS settings i configure a static pool of 3 addresses, then try connecting, the VPN client connect successfully.

It seems that the Virtual server wont get addresses from DHCP?

Yet, if i spin up a new VM on the same host, the NIC will obtain a static address, so i know DHCP is working and get to Virtual Servers, just not the RRAS one?

Can anyone advise with this strange issue?

TIA.

[ITGURU]

Just discovered its definitely a bug! https://social.technet.microsoft.com/Forums/en-US/0270d377-be3a-4b63-82a0-9df076c5e3b3/upgrade-from-2016-to-2019-breaks-dhcp-relay-agent-when-using-rras?forum=ws2019

 

Whether a new install or upgrade - DHCP part doesnt work as shows a red X against it in services. Tested on new clean install multiple 2019 servers.

 

If install 2016 on another server, works fine.

[ITGURU]

No fix for this still....can't upgrade my remote servers to 2019 yet.

[snagrat]

No fix for this still....can't upgrade my remote servers to 2019 yet.

 

Have you a fix for this yet?

[ITGURU]

Have you a fix for this yet?

 

Nope! I keep installing the latest cumulative updates on another 2019 VM and testing but still not fixed!