Routing and remote access (RRAS) not requesting / reserving DHCP leases for VPN clients (Windows server 2019)

This days implementing VPN solution is almost a daily task … I encountered a bug that has been around for some time now. If you deploy RRAS on Windows Server 2019 that is not DHCP server it does not request / reserve IP addresses from DHCP (that runs on some other server).
Everything works perfectly if you assign static range of IP addresses but I just want to manage VPN client IP addresses by using DHCP server.

In System log in Event viewer you will receive Event ID 20167 with information:
RoutingDomainID- {: No IP address is available to hand out to the dial-in client.

After a quick search I found the article on MS forums that states:

Add this registry entries to your VPN server and reboot it.

reg add “HKLM\SYSTEM\CurrentControlSet\Services\Dhcp” /v RequiredPrivileges /d “SeChangeNotifyPrivilege”\0″SeCreateGlobalPrivilege”\0″SeImpersonatePrivilege”\0 /t REG_MULTI_SZ /f

Hope it helps like it did in last five implementations I was working on recently.

2 thoughts on “Routing and remote access (RRAS) not requesting / reserving DHCP leases for VPN clients (Windows server 2019)

  1. BQ

    How about if I do not want RRAS to Assign APIPA IP? Static IP will be assigned by AD and if IP is already connected on a different Device, it should not let another connection be made it should through 720 or 13899 error on windows based client machine or any other OS.
    Currently, second connection gets APIPA IP and it is unable to browse.

    Like

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.