If the first ethernet connection uses a unroutable 169.x.x.x address while in WinPE, PECTagent will fail to find a nearest package server.

Products

• Deployment Solution

Issue/Introduction

If the first ethernet connection uses a unroutable 169.x.x.x address while in WinPE, PECTagent will fail to find a nearest package server, or find a package server that is not local to the client.

Cause

If an ethernet connection is first on the IPconfig list and connects to a network that is not assigned an IP address automatically (i.e. DHCP managed), it will be assigned a default 169.x.x.x address which the PECTagent will use to determine the nearest package server, then fail or assign an unexpected package server.

Example:

Resolution

This behavior has been fixed in DS 7.6 HF7 by filtering out the 169.x.x.x addresses from the list of available IP addresses to query for a package server.