iMac refuses to accept IP

[Siegenthaler Tina]

> 
> Indeed. This is the client identifier option of the first discover:
> 
>    Option: (t=61,l=33) Client identifier
>        Option: (61) Client identifier
>        Length: 33
>        Value: 013C075472CBC20000000000000000000000000000000000...
> 
> 
> And this the one of the second:
> 
>    Option: (t=61,l=7) Client identifier
>        Option: (61) Client identifier
>        Length: 7
>        Value: 013C075472CBC2
>        Hardware type: Ethernet
>        Client MAC address: 3c:07:54:72:cb:c2 (3c:07:54:72:cb:c2)
> 
> 
> Now that this is clear, I'll just have to find a workaround...
> 
> I'm going to try the following:
> 
> - Setting a DHCP client ID in the System Prefs (as proposed by Simon - thanks)
> - If that doesn't help, use rEFIt as the boot manager
> - If that doesn't help either.... ???
> 

Oh no, I'm sooo stupid! The reason for all this was that I forgot to set the startup volume... so the client tried to netboot at first, and only then, if that failed, used the internal HD. Argh. But still, I'm sure, that this is a quite new behavior, at least I never noticed that before (and it's not the first time that the startup disk was not defined for some reason). And I also think that the client should use the same client identifier no matter if it's trying to netboot or just "normally" asking for an IP.

BTW, as to setting a DHCP client ID, this didn't help. The first discover still used the client identifier with the many zero bytes, the second one (after booting) then used the Client ID I specified. If I don't set an ID manually, a Mac will (normally) use 01 plus its MAC address.

Thanks to everybody for helping, I wouldn't have found that out so fast without you.


Tina