Issue:
The DHCP server is running out of addresses now that PBConnex is being used. Why, and how to work around this?
Background
If using PBConnex, SecureDoc client devices will attempt to get a DHCP address at pre-Boot. For customers having a small pool of available DHCP-provided network addresses, this can be a problem.
If your DHCP server is set to provide client devices with a network address based on Device Name, since the device name is not available at Pre-Boot Logon the DHCP server will provide a lease to the client during pre-boot, and then a new (or renewed) second address lease when the device boots into the Operating System. Depending upon the DHCP lease settings you have in effect, this may drain the DHCP lease pool more rapidly than expected.
Work-Around
1 - Consider changing the DHCP address leases to be based on the network interface card's MAC address
2 - The SecureDoc client in versions AFTER V6.5 will include a command to release the IP address immediately following pre-boot, and before the OS loads. this should improve this situation.