Citrix Provisioning Services TFTP Services Fails To Bind To IPv4 Stack After Reboot
Article ID: CTX696914
Updated On:
Description
The Citrix Team has found the problem occurrs during network adapter unicast address handling. The problem is expected to be resolved in future releases but has a permanent workaround in the meantime.
Environment
Disclaimer:
"Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it."
Resolution
On each PVS server we can delete the existing "adapter" GUID in the registry and restart TFTP.
Caution! Refer to the Disclaimer at the end of this article before using the Registry Editor.
1. Open Regedit and browse to: Computer> HKLM> Current Control Set> Services> BNTFTP> Parameters
2. Right click on Adapter> delete the highlight string value in the data column> Save
3. Restart the Citrix TFTP service
Alternatively setting the Citrix TFTP service to automatic delayed start has shown to preserve the service after a system reboot.
Issue/Introduction
After upgrading Provisioning Services you may find that the Target Devices fail to boot with a TFTP timeout error. The Citrix TFTP service may still be running but is no longer bound to the IPv4 stack on port 69. Netstat will show that it continues to operate on the IPv6 protocol if enabled. A restart of the Citrix TFTP service allows the service to bind as expected but after a system reboot or re-running the config wizard the service will fail again.
The Application Event Viewer will show Event 261 - Unable to bind to socket
