1. July 2015 23:18
I have several DirectAccess configurations at my customers where they use both DirectAccess and VPN on the same server.
I have often seen that when I have changed the DirectAccess configuration on a server with both DirectAccess and VPN installed then I was not able to start the DirectAccess console afterwards.
After changing the DirectAccess configuration and when starting the DirectAccess console the following error message is shown:
"Settings for server <Server Name> cannot be retrieved. VPN is configured to allocate IP addresses using a static address pool, but no IP address ranges are configure"
It seams that DirectAccess configuration faulty will set the VPN configuration to using a static address pool without a pool beeing defined.
I searched the Internet and found the solution here.
Just run this command in an elevated powershell prompt on the DirectAccess server:
Set-VpnIPAddressAssignment -IPAssignmentMethod ‘DHCP’
That will configure the VPN back to using a DHCP server to assing IP addresses to the clients.
After that it is again possible to open the DirectAccess console without any errors.
I hope it helps.