ddbla
asked on
Netboot Client Mac OS 10.5.8
Hello,
I am unable to get clients to netboot to our server. I have two servers in two different offices and i've copied one image up to the second office and it doesnt seem to work. The server setup is identical but the clients can never get connected to the server. In the logs I find:
Can't open /etc/bootptab and subnets: Failed to convert 'router' : Invalid IP Address
I am unable to get clients to netboot to our server. I have two servers in two different offices and i've copied one image up to the second office and it doesnt seem to work. The server setup is identical but the clients can never get connected to the server. In the logs I find:
Can't open /etc/bootptab and subnets: Failed to convert 'router' : Invalid IP Address
ASKER
the servers do not provide DHCP for the clients. In the SF office it is supplied by a Windows Server and on LA office it is provided by our Core 4507 switch.
the clients are on the same subnet as the server.
the logs are quoted fromt the netboot log screen on the server.
Both servers are at 10.5.8, but as far as cloning they are not in that sense. the configurations are installed with the same settings.
The clients get the spinning globe but then just boot to the desktop.
the clients are on the same subnet as the server.
the logs are quoted fromt the netboot log screen on the server.
Both servers are at 10.5.8, but as far as cloning they are not in that sense. the configurations are installed with the same settings.
The clients get the spinning globe but then just boot to the desktop.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Roy,
Just one question, how do you change the protocol options?
and the image works in the LA office fine.
Just one question, how do you change the protocol options?
and the image works in the LA office fine.
in the file sharing tab / section for that server in the server admin application. It's what used to be available in the workgroup manager and is now moved to a subsection for each 10.5.x server in server admin.
ASKER
Hi Roy,
Thanks for pointing that out.
I was adjusting the permissions on the .nbi folders as it looks like the Everyone permission was not pushing all the way down to the files inside. That seems to have allowed the clients to connect to the image. Perhaps this permission fell off when transferring across our network?
2 systems are currently imaging now.
Thanks for pointing that out.
I was adjusting the permissions on the .nbi folders as it looks like the Everyone permission was not pushing all the way down to the files inside. That seems to have allowed the clients to connect to the image. Perhaps this permission fell off when transferring across our network?
2 systems are currently imaging now.
Before that can you even select the netboot image from your system preferences and boot from it? If this cannot be done there may be a problem with the image itself.
Also, have you restricted the image to specific hardware builds, which may be preventing it from booting the target machine?
Is the DHCP server on the same subnet as the netboot server?
Also, have you restricted the image to specific hardware builds, which may be preventing it from booting the target machine?
Is the DHCP server on the same subnet as the netboot server?
ASKER
hi nappy d,
it actually looked to be the permissions on the .nbi folder. After allowing the permissions to propagate the systems imaged successfully.
Yes, they were able to see the image in the system preferences. There was also no filtering enabled.
Thanks!
it actually looked to be the permissions on the .nbi folder. After allowing the permissions to propagate the systems imaged successfully.
Yes, they were able to see the image in the system preferences. There was also no filtering enabled.
Thanks!
ASKER
This should have reset the permissions on the image.
I accept this as the solution.
Thanks, Roy!
I accept this as the solution.
Thanks, Roy!
which logs are you quoting? client or server?
Is the original server working? how is this configured if it is working? the same as the second server?
Is the server the same version of OS - you say Identical, did you clone the first one to the second one or just install with the same settings?
is your DHCP server (presuming you are using a separate DHCP server) providing the netboot address to the clients?
lots of questions I know, but need a clearer picture of your environment. :)