DHCP Allocator

ICS can configure clients on the home network automatically by using DHCP. Windows CE does not support the services required to operate a full DHCP server. Windows CE does support, however, a subset of these services called the DHCP allocator. Windows CE implements the DHCP allocator as part of the ipnat component (Ipnat.dll).

To enable the DHCP Allocator

  1. Set the HKEY_LOCAL_MACHINE\Comm\ConnectionSharing\EnableDhcpAllocator registry key equal to a non-zero value.
  2. Set the HKEY_LOCAL_MACHINE\Comm\ConnectionSharing\PrivateInterface registry key to a list of private interfaces that you want to enable the DHCP allocator on. If the list contains multiple private interfaces, those interfaces all must have the same subnet value in their IP addresses.

DHCP can automatically assign addresses for the home network, including appropriate default gateway and DNS server information. This approach assumes that the DHCP allocation is performed from the gateway device, so that the gateway can advertise itself to DHCP clients as both the default gateway and the DNS server to the Internet.

The Windows CE DHCP allocator stores the addresses that the allocator hands out in the Address subkeys under the HKEY_LOCAL_MACHINE\Comm\ConnectionSharing\Addresses registry key. For more information about these registry entries, see Mapping Machine Names to IP Addresses on the Local Network and ICS Registry Keys. The allocator pseudorandomly assigns addresses, and checks the uniqueness of each address by using the same logic as Automatic IP. The allocator defends each address on the network before the assigning the address, and the allocator makes the address assignments for short, configurable periods of time to avoid collisions that arise when devices are not operating. The default period for address assignment is ten minutes.

Note   This approach works when all machines on the home network have broadcast access to the gateway. If the configuration of the home network includes multiple routed segments, then you must use true DHCP server with a database. This requirement for a true DHCP server arises because a broadcast-based defense is not an adequate means of ensuring the uniqueness of assigned addresses for multiple routed segments. A broadcast-based defense is inadequate because not all devices on the home network have broadcast access to the DHCP server. Furthermore, multiple routed segments require the configuration of multiple DHCP scopes to ensure that separate subnets are used on each segment, as well as the configuration of DHCP relay agents to relay DHCP requests to the DHCP allocator.

To change the length of time for which the DHCP allocator assigns addresses

To keep an address in the address table set permanently

For more information about DHCP, see Automatic Client Configuration.

 Last updated on Friday, April 02, 2004

© 1992-2000 Microsoft Corporation. All rights reserved.