Article ID: 1661, created on Oct 6, 2008, last review on May 11, 2014

  • Applies to:
  • Virtuozzo containers for Windows


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

vzctl exec VEID ipconfig /all


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)


Vzadapter problem

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

vzctl exec CTID sc query vzadapter

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


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

HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Control\Network\{ 4D36E972-E325-11CE-BFC1-08002BE10318}\{ 00A8E642-7706-418E-8418-B7812ECA33F2}\Connection from ROOT\MS_NDISWANATALK\0000 to ROOT\VZNET\0000

3. Change permissions and then delete the key:

4. Delete the key


5. Restart Container (VE).

965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF