Cannot boot client

If a particular client will not boot, the problem may center on IP address assignment. If the DHCP server dynamically assigns an address to the client, first check /usr/adm/syslog and search for the ``No available addresses'' message. This indicates that all the addresses in the pool assigned to the client's subnet have been allocated. There are a number of actions you could take:

1. Reconfigure the address pool with more addresses, provided you have unused addresses available on the subnet. You can use the Address pools button in the Subnet Entry screen to invoke the Address Allocation Manager.

2. Review the address pool's current allocation information in the Address Allocation Manager and look for any disabled addresses. Enabling these addresses will make them available again. See ``Releasing, disabling, and re-enabling addresses''.

3. Review the allocated addresses in the address pool's current allocation information and try to identify addresses that you know are not really in use even though they are allocated. These would probably be addresses with long or infinite leases (lease duration) which were allocated to temporary network machines such as laptop PCs. (This is the result of setting a long or infinite default lease time when configuring the subnet for DHCP.) Release any allocated addresses that are not in use. See ``Releasing, disabling, and re-enabling addresses''.