TFTP fails with error - No transfer exists for this client
Last Updated January 24, 2012
PXE fails to transfer files for image deployment.
Error : (2064)PxeMtftp: SendUCast() building error - No transfer exists for this client
Customer followed these steps.
- Install new Site Server/PXE Server on a Virtual Environment - Apply same GPO as production servers - Install SEP agent as configured on production server - Configure IPhelper to broadcast to new PXE server VLAN
The TCPIP stack gets unstable when the server has SEP – Proactive Threat Protection Installed/Enabled.
In Case of both servers presenting the issue, the SEP Client (11.5002.333) has Network Protection and Proactive Threat Protection... In case of the server working, it only has Network Protection is enabled.
When we send the installation package with all options of SEP (NP, PP and AV) the PXE MTFTP service fails.
If we uninstall the whole client (SEP) and send the cut down version of SEP (only with Network Protection) it works!!!
"If you plan to deploy SEP client to computers running a server operating system, it is suggested that two client groups be created under your main Server Group. One for servers where an Installation Package is deployed that does not include Network Threat Protection (NTP) or Proactive Threat Protection (PTP) and another for clients that uses an Installation Package that may include these features."
SEP (Symantec Endpoint protection)
SEP - Network Protection and Proactive Threat Protection
Imported Document ID: TECH127438
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe