Link to home
Start Free TrialLog in
Avatar of safeharbor
safeharbor

asked on

Microsoft VPN fails to connect clients after moving the VM from ESX 5 to a new ESX 5.5 host

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?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

How did you migrate the VMs using Veeam ?

Have any networking, IP Addresses, Mac Addresses Changed ?

Firewall Changes ?
Avatar of safeharbor
safeharbor

ASKER

Yes I did migrate using Veeam. We made no changes. Just migrated vm's to a new host.
When you powered on the VMs no questions about Move or Copied?

All services are started that should be started ?
ASKER CERTIFIED SOLUTION
Avatar of safeharbor
safeharbor

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You should *ALWAYS* use the VMXNET3 interface!

E1000 is only useful for installations of an OS!

If using PPTP, you also may want to look and investigate as to whether it's a security risk, since it's become vulnerable!
Thx for the info
This solution came as part of a VMware support call and quickly resolved the issue.