I summited this same issue to KACE, but I figured I would post here as well. Any help or input is appreciated.

We are having issues with 3.5 and the new imacs/macbooks. First, I was able to successfully create a netboot image with the 3.5 media manager. I created one from our imac (thin model) and our macbook pro just to have options. They both uploaded flawlessly.

When I try to netboot the imac all I get is a white screen with a white no smoking sign type of icon. I will attach a picture below of both issues. The imac has an ip address, it can ping the K2000 and our other servers, you can see it on the K2000, and you can also see it in system preferences> startup disk.

 

When I netboot the macbook pro all goes well up until you click on the K2000 Imaging Utility. I am getting the error "Unable to determine hostname of K2000". Again, the macbook has an ip address, it can ping the K2000 and our other servers, you can see it on the K2000, and you can also see it in system preference> startup disk.

 

 I created the netboot image from the lastest Lion download from the app store. I have made it the default boot environment on the K2000 as well. I also noticed that the K2000 Imaging utility is still 3.4 Does that matter?

 

 Here are the images on the errors I'm getting - https://www.dropbox.com/sh/mqs5z31xuu1kl1x/q8fC-qPVSm

 

Thanks,

Jeremy

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1

I don't think this is a dhcp configuration issue as Jeremy is successfully netbooting.  He is only seeing this message on 2 models, other macs work fine.

Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 02/11/2013 by: cserrins
Red Belt

Please log in to comment

Answers

0

check options 66,67 and 244 on the dhcp server for that pool

We ran into a problem also on a mac when it loaded the wireless also and tried to use the wireless instead of the wired nic.

Answered 01/08/2013 by: SMal.tmcc
Red Belt

  • Thanks. The Kace is the dhcp server. The only options I see are the ip range input. The wireless is disabled also if that matters.
    • what platform is your dhcp server on?
  • We use Microsoft as our main dhcp server, but the kace is pushing out ip addresses to the subnet it's on.
    • We use MS on all our subnets, I see what you mean in kbox about limited info, we do not have on-board dhcp enabled but the "enable netboot server" under that is checked on. Not sure where to go from here, only suggestion I have is to switch to MS dhcp

      Hopefully someone else will have another idea
  • Thanks. Switched it to MS dhcp and both machines still do the same exact thing. *Finds the nearest cliff*
    • could not put picture here so see other answer for picture. Confirm that the entries are under the scope not the server in MS dhcp and if so I would also open a ticket while you wait to see if anyone else has any input.
  • I did it on the scope. I have a ticket open and I'm waiting to see what happens.

    Thanks for your help,
    Jeremy
Please log in to comment
0

Answered 01/08/2013 by: SMal.tmcc
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity