[QUOTE][u]Quote by: Bartron[/u][p][QUOTE][u]Quote by: airlocksniffer[/u][p]We actually got this to work. What we found is that the newer firmware cannot get an IP address while netbooting when the DHCP server is on another subnet and falls back to the internal drive. We fired up an old HP server for DHCP and put it, the lion server and client on the same subnet and it works fine. I need to test whether or not I can netboot when the client is on one subnet and the dhcp/lion server are on another. [/p][/QUOTE]
On a class b or class c?
Either way that would mean we would need something like an extra 10 tftp servers to service all locations not on the same subnet as the dhcp server.
Gives me something to test though, thanks for the info.[/p][/QUOTE]
ewww, going to scrounge up a box and try testing as well. If it does work thats not remotely scaleable for us but would be good to know that somehow when our core is handing off the DHCP traffic its dropping something that mac is expecting
Recent Comments