Solution #00006727
Scope:
This solution applies to Barracuda SSL VPN Hyper-V appliance downloads
Answer:
Out of the box, the Network Connector feature may not work on a Hyper-V appliance downloaded from the Barracuda website. This is because promiscuous-mode networking is either missing or disabled by default, depending on the customers' version of the Hyper-V hypervisor, and this is a requirement for the bridged network used for Network Connector. For Hyper-V 2008 (non-R2) there is no workaround, all other features of the SSL VPN should function correclty but Network Connector is unavailable. For Hyper-V 2008R2 or Hyper-V 2012 there is a fix available from the Hyper-V Manager UI:
Hyper-V 2008 R2:
- Shut down the VM from the appliance UI on port 8000/8443
- Open Hyper-V Manager
- Open the Virtual Machine settings dialog for the SSL VPN VM
- Select the "Network Adapter" node in the tree on the left of the window
- Tick the "Enable spoofing of MAC addresses" box on the right of the window
- Click "OK" to save the changes
- Start the VM from Hyper-V Manager
Hyper-V 2012:
- Open Hyper-V Manager
- Open the Virtual Machine settings dialog for the SSL VPN VM
- Expand the "Network Adapter" node in the tree on the left of the window by clicking the plus symbol
- Select "Advanced Features"
- Tick the "Enable spoofing of MAC addresses" box on the right of the window
- Click "OK" to save the changes
Note that under Hyper-V 2012 it is not necessary to shut down the virtual machine first, this change can be made to a running VM.
Once this change has been made, Network Connector should begin to function correctly in the same way it would on a physical appliance, or virtual appliance hosted on VMWare, Xen, or Virtualbox.
Link
to This Page: