Bitlocker Network Unlock and IP Helper

[#1]

Hey Community,

we try to setup Bitlocker Network Unlock with an Infoblox IP Helper. Anyone succeededm already and can confirm it should work?

If we use Bitlocker Network Unlocck in the same subnet as the WDS server it works. As soon as the IP Helper should forward the traffic it sometimes works. 

The Network Unlock feature works in this way, that after the standard DHCP requests a second BOOTP Braoadcast is done. This braodcast is replied by the WDS Server and then no PIN needs to be entered.

But with the InfoBlox Configuration for some reason it does not work stable. 

By the way is it possible to configure the infoblox to give a machine the same IP for PXE and afterwards? Right now during PXE the computer gets a different IP with a shorter lease.

Thanks a lot in advance.

Matthias

[#2]

Hello,

we found out, that the the DHCP offer from the infoblox has sometimes a 1 second delay. This delay is too much for the Windows Boot Manager. Any idea why there might be a 1 second delay (not always but for 95 % of the time). The fast replies are also coming from the same DHCP server.

Thanks

[#3]

---

@joka44u wrote:

Hello,

we found out, that the the DHCP offer from the infoblox has sometimes a 1 second delay. This delay is too much for the Windows Boot Manager. Any idea why there might be a 1 second delay (not always but for 95 % of the time). The fast replies are also coming from the same DHCP server.

Thanks

---

By default, NIOS will first attempt to verify that an IP being offered is not in use by running a ping test (1 ping with a 1 second timeout). This is set in the Advanced tab of the Grid (member) DHCP properties.

Regards,

Tony

[#4]

---

@joka44u wrote:

Hey Community,

<snip>

By the way is it possible to configure the infoblox to give a machine the same IP for PXE and afterwards? Right now during PXE the computer gets a different IP with a shorter lease.

Thanks a lot in advance.

Matthias

---

NIOS uses both the MAC address and client identifier to identify DHCP clients. If either of these values changes (such as what you might see with PXE clients), the server will consider this request to be from a different client and provide a new lease as a result. In the DHCP properties under the General -> Advanced tab is an option to customize this, with the options including "Accept Client Identifier and MAC Address", "Ignore Client Identifier", and "Ignore MAC Address". This configuration option is available at the Grid, Grid member, Network, DHCP Range and Fixed Address/Reservation levels.

Regards,

Tony