Lpadmin stoppning the login process

Question

Basic facts:
10.5.6 server with 10.5.6 clients over Airport (Airport Extreme and Airport Express).
Managed clients with mobile accounts.
Services on server: DHCP, AFP, OD, NFS, SU, Netboot, DNS, iCal.
All worked fine up until one client updated itself to 10.5.7 around the same time I moved the printer from the Airport Express to the Airport Extreme.
What happens is when one try to login at this client machine it accepts the login but before anything changes a adminstration window opos up stating that lpadmin needs the administrator priviliges to do some changes. I cannot do anything with this, I cannot add the administartion login nothing.
If I try to login into the machine with the local account the same thing happens.
If I unbind the client from the OD I can login with the local account.
I have tried to update the server to 10.5.7 nothing changed.
I refomatted the client and when I bid the computer the OD same thing happens again.
So something has happend on the server, but what? And what can I do to fix this?

Answer 1

According to this thread, it solves the problem.
The thread indicated is this discussion.
This command, 'dseditgroup -o edit -p -a admin -t group _lpadmin', attempts to add a user 'admin' to a record type of 'group' named '_lpadmin'. If you do, 'dscl . -list /Groups', you will see a group '_lpadmin' already exists. If you do, 'dscl . -read /Groups/_lpadmin' it will show the local admins as members of the group. In this case, the '-t group', portion of the command is superfluous. If the user with the shortname 'admin' does not exist on the machine, then it does nothing.
More than likely the user shortname in the example, 'admin', was placed there to indicate an admin level user should be added to the '_lpadmin' group. So in order for this command, 'dseditgroup -o edit -a admin _lpadmin' to work, you would have to add all local admin users and any local users to the '_lpadmin' group.
What the dialog box is specifically asking for is admin privileges for the user '_lpadmin'. That is why this command, 'dseditgroup -o edit -a _lpadmin admin', is the correct syntax as it adds the user '_lpadmin' to the 'admin' group which satisfies the dialog box request and does not require you to add every user to the '_lpadmin' group.
Correct that dseditgroup does not require SUM, but if the user is having a login problem, any variables associated with login can be eliminated by booting into SUM.
If there are any jobs in any local printers on the machine that are not stopped, as soon as the machine boots, the jobs will start to spool. If the printers are unreachable or the problem under discussion is in effect, the machine could hang or become slow to respond. Reformatting the machine only removes the problem for local users. If a network user logs in, the spooled jobs will again start to print from the user's print spool. So the user's print jobs need to be cleared from the user's home folder on the server, also.