VPN Stopped Working After Changing Network Adapter on Win Server 2012 R2 Essentials
We have been using a VPN set up through Windows Server 2012 R2 Essentials for several weeks. The Essentials server (and 3 other Windows servers) run as virtual machines on VMware ESXi. Last night, we changed the virtual network adapters of our servers to try to resolve a problem with VMware crashing. Since changing the virtual adapters, everything has been working fine, except for the VPN.
The VPN shows as connected, but we are unable to ping or otherwise access internal resources. I have run the repair and reconfigured Anywhere Access using the wizard in the Essentials dashboard, but that has not resolved the issue. We can connect to Remote Web Access without problems. As I said, the VPN shows as connected and we get no error messages. All clients are Windows 8.1.
The IPv4 addresses are all the same, but the MAC address and possibly the IPv6 addresses have changed on our servers, if that makes a difference.
I’m not sure where to look or what to do at this point. Any suggestions?
The VPN shows as connected, but we are unable to ping or otherwise access internal resources. I have run the repair and reconfigured Anywhere Access using the wizard in the Essentials dashboard, but that has not resolved the issue. We can connect to Remote Web Access without problems. As I said, the VPN shows as connected and we get no error messages. All clients are Windows 8.1.
The IPv4 addresses are all the same, but the MAC address and possibly the IPv6 addresses have changed on our servers, if that makes a difference.
I’m not sure where to look or what to do at this point. Any suggestions?
Perarduaadastra
I'd delete the VPN connection and create a new one.
ASKER
I tried deleting and recreating the VPN connection, but that didn't work.
However, I have discovered the cause of the problem: it is the virtual network adapter we are using with VMware. We were using the E1000E adapter in VMware, but VMware was crashing randomly. A KB article from VMware listed this as a known problem with the E1000E adapter, and the workaround was to switch to the VMXNET 3 adapter. We did this on Monday night, and that is when the VPN stopped working. I switched back to the E1000E and the VPN worked again. Switched to VMXNET 3 again, and it stopped working.
Now I need to contact VMware to see how the heck we can get a network adapter that doesn't crash the server or cause problems with the VPN!
I'll post back once I find a solution, although if anyone out there knows of one, I would appreciate hearing from you.
However, I have discovered the cause of the problem: it is the virtual network adapter we are using with VMware. We were using the E1000E adapter in VMware, but VMware was crashing randomly. A KB article from VMware listed this as a known problem with the E1000E adapter, and the workaround was to switch to the VMXNET 3 adapter. We did this on Monday night, and that is when the VPN stopped working. I switched back to the E1000E and the VPN worked again. Switched to VMXNET 3 again, and it stopped working.
Now I need to contact VMware to see how the heck we can get a network adapter that doesn't crash the server or cause problems with the VPN!
I'll post back once I find a solution, although if anyone out there knows of one, I would appreciate hearing from you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I accepted my own solution as I wound up resolving the problem without the suggestion that was made. But I appreciate the attempt to help!