Using 3Com Boot Services for PXE and TFTP - when a 3Com PXE boot client performs a PXE boot from a Windows 2003 server machine running both DHCP and the 3Com Boot Services, the PXE client is registered in the Windows 2003 machine's ARP table with a static ARP entry.

If the workstation PC IP address ever changes, the Windows 2003 machine loses communication with the client workstation as the ARP table is reporting the PXE client with a static entry, pointing to an incorrect IP address. Based on review of how DHCP assigns IP addresses during simultaneous PXE-booting of several hundred workstations, imaging, and then booting 'imaged' PC up with Windows XP, the problem seems to lie with the creation of a static ARP entry vesrsus a dynamic ARP enry on the WIndows 2003 server. The quick and dirty fix is to clear the Windows 2003 ARP table. Any thoughts?

The problems caused by this are that we get cost to execute a program after imaging, this is failing the majority of the time due to this problem, the IP assigned to the machine is different to that of the oen the Ghost server thinks the machine has. When you clear the ARP cache on the server suddenly if all kicks into life and the command is executed.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

Answer this question or Comment on this question for clarity