Microsoft VPN fails to connect clients after moving the VM from ESX 5 to a new ESX 5.5 host
Posted on 2014-11-17
Over the weekend we replaced some aging hardware for a client running 6 servers on a ESX 5 host. We migrated all VMs using Veeam to a new ESX 5.5 host without issue. The only issue that has cropped up and I am scratching my head over is that the Microsoft RAS VPN service is failing to authenticate and connect VPN clients after the move.
We have made no server configuration changes. I migrated it twice two different ways and still have the same issue. I did a quick migration from host to host and I did a complete backup and restore. I even tried setting RAS up on a different server with the same affect.
If I turn the old VM on on the old host it works perfectly. Any ideas?