Netboot Client Mac OS 10.5.8


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
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

how have you got the netboot servers configured on your network?  are they providing DHCP addresses?  are they on the same subnet as the clients?

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. :)
ddblaAuthor Commented:
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.
So are either of your servers working correctly as netboot servers for your clients?  or neither?

I heard of a similar problem and it was to do with the bootpd.plist file or problems getting to the .nbi files.  Try the following as this seems to have provided resolution in a couple of incidents::

Solution: Part of the problem was the bootpd.plist file. The other part of the problem was that the Share Points got all messed up.

Move all .nbi folders out of SP0 folder on your netboot server

Go to Server Admin
Disable Netboot

select server
go to File Sharing
go to Share Points

Unshare all NetbootSP* and NetbootClients* shares.

Enable Netboot. Configure.
Modify the Protocol Options of the new shares (File Sharing).

Move all .nbi folders back into SP0 folder.

Try the netboot again after this. and let me know how it goes.

I trust you have tested the neboot image to make sure this is good?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

ddblaAuthor Commented:
Hi Roy,

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.
ddblaAuthor Commented:
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.
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
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?  
ddblaAuthor Commented:
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.


ddblaAuthor Commented:
This should have reset the permissions on the image.

I accept this as the solution.

Thanks, Roy!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Mac OS X

From novice to tech pro — start learning today.