Parallels

Symptoms

VE is not available. VE shows no interface or address information when running the following command from the hardware node:

Cause

Some third party software is installed inside VE and has its own protocols bound on virtual network adapter.

Another possible but rare reason could be disabled vzadapter inside a Container (VE)

Resolution

Vzadapter problem

To make sure that vzadapter is enabled and running please execute the following command:



If it's stopped please open regedit, and go to the following registry key:

HKEY_LOCAL_MACHINE\vz{VEID}\MACHINE\SYSTEM\CurrentControlSet\Services\vzadapter

Please ensure that Start value is configured to 3. 

Reboot the Container (VE) after that.

Protocol problem

The problematic protocol could be almost any third-party protocol, but the most commonly observed problems are either NDISWANATALK or NDISWANBH.

To remove the problematic drivers perform the following modifications to the registry. Note that the name of the driver could be different and that in these examples VEID and GUID represent the VEs having the problem. The GUID for a given VE will look like { 00A8E642-7706-418E-8418-B7812ECA33F2}.

1 . Delete the key

HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c }\##?#Root#MS_NDISWANATALK#0000##{ad498944-762f-11d0-8dcb-00c04fc3358c }

2 . Rename value PnpInstanceID under the key



3. Change permissions and then delete the key:
 

HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Enum\Root\MS_NDISWANATALK

4. Delete the key

HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\PSched\Parameters\Adapters\NdisWanAtalk

5. Restart Container (VE).