There is a scope option that might need to be created in some cases to allow KBE to find the K2000 appliance. During the boot process, KBE looks at two places for the IP address of the K2000 appliance. To do this, the process runs kgetdhcp 66 and kgetdhcp 244. If either of these returns the IP address the Y: driver is mapped using that IP.
If you are using non-Microsoft DHCP, you might find that the probe for options 66 may return no data. In other instances, the system my return bogus data. This means that the test succeeded because a null value was not returned. There are two ways to repair this.
The first is to make sure that you have both options 66 and 244 created, even if you are using a Microsoft DHCP server. If you are not using a Microsoft DHCP, you can also add both next-server, bootfile, and a static option=244 to your system.
There are also times in which some systems require BootP to be set to the IP address of the K2000 or RSA.
Here is how to create option 244 in Microsoft DHCP:
Note: When adding option 244 to the scope, the value of the option will be the K2000 or RSA's IP address.
The second way is to use the KBE Manipulator to set the KBE to point to the static IP address of the K2000 or RSA.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center