Network unresponsiveness on the NIC, which is not used for the Provisioning Services

If the Provisioning Services network stack Citrix Network Stack is bound to NIC, which is not used for the Provisioning Services, in rare cases this causes Network unresponsiveness on the NIC. For example, it is not possible to receive the network packet since Citrix Network Stack conflicts with another network intermediate driver.

Resolution

If you encounter the network unresponsiveness on the NIC which is not used for the Provisioning Services, unbind the Provisioning Services network stack to the NIC using bindcfg.exe.

  • Start the target device with Private Image Mode.
  • Run bindcfg.exe, which is located in the installation directory.
  • Choose only the NIC used for the Provisioning Services and deselect the other NICs:

  • Shutdown the target device and change vDisk to Standard Image Mode.

After the update, check the property of each NIC if Citrix Network Stack is not selected on the NIC, which is not used for the Provisioning Services.

More Information

If the target device, which has multiple NICs is running on the Virtual Machine in XenServer, the Provisioning Services network stack, Citrix Network Stack is bound to first 9 NICs by default.

Prior to Provisioning Services 6.0, Citrix Network Stack exists in all the target devices. Provisioning Services 6.0 or later, it exists only in the target devices in both Windows XP and Windows 2003.

You can read the full article here on the knowledgebase.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.