When Symantec Endpoint Protection's firewall is enabled, a VMware or MokaFive virtual machine with the network in bridged mode cannot acquire an IP address via DHCP while connected via wireless
Last Updated May 23, 2013
When Symantec Endpoint Protection (SEP) version 11 or 12.1's firewall is installed and enabled on the host computer, a VMware Player, VMware Workstation, or MokaFive guest virtual machine whose virtual network interface card (NIC) is in bridged mode cannot acquire an IP address when the machine is connected to the network using a wireless access point. When ipconfig /renew is run from the command line, the following error is returned: An error occurred while renewing interface Local Area Connection : The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
The issue does not occur if the NIC's mode is changed from bridged to NAT, if the SEP firewall is disabled or uninstalled from the host computer, or if the computer is connected to the network physically via ethernet.
Adding an Allow All rule to the SEP firewall does not resolve this issue.
Symantec has worked with VMWare and MokaFive and has determined that this is not an issue with the Symantec firewall.
Symantec has worked with VMWare and MokaFive and has determined that this is not an issue with the Symantec firewall. This issue may be worked around by making one of the following changes:
Switching the guest virtual machine's NIC from bridged to NAT mode
Connecting the host computer to the network via ethernet rather than wireless