lpadmin stoppning the login process

STmattiasSWE,
Any luck fixing this problem? We have encountered the same problem with our 10.5.7 PPC computers.

I believe this is a bug with 10.5.7. I'm not completely clear about what you're describing, but I can list one fix here for you.

Boot the affected client machine into single user mode using command-s at the startup chime.

Mount the system drive with the command
*mount -uw* /

Start Directory Services with the command
*/bin/launchctl load /System/Library/LaunchDaemons/com.apple.DirectoryServices.plist &*

Add the lpadmin user to the admin group with the command
*dseditgroup -o edit -p -a admin -t group _lpadmin*

Reboot the machine by typing
reboot

Hopefully that will work for you.

Message was edited by: Aaron Adams

Message was edited by: Aaron Adams

the 'dseditgroup' command as you have described prompts to 'Please enter user password'... I assume this is asking for the lpadmin user password as it does not seem to be accepting the root user password if I run as su...

Are you doing this from single user mode? If so, then you should not be prompted for a password because the underlying OS mechanisms for authentication are not active. If you're doing this from the terminal, stop and reboot into single user mode.

Add the lpadmin user to the admin group with the command
dseditgroup -o edit -p -a admin -t group _lpadmin

The above command is incorrect. It adds the user 'admin' to the group '_lpadmin'. That is not what you want to do.

It is also not necessary to boot into 'single user mode' to use ' dseditgroup'.

Open Terminal.app and do:

sudo -s

then do:

dseditgroup -o -a _lpadmin admin

Changes will be applied immediately to the local directory and can be checked by doing:

dseditgroup -o -read admin

The above command is incorrect. It adds the user 'admin' to the group '_lpadmin'. That is not what you want to do.

According to this thread, it solves the problem. It has worked for me several times, so I'm passing it along.

It is also not necessary to boot into 'single user mode' to use ' dseditgroup'.

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.

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.

10.5.8 fixed this issue but if you do not want to update to 10.5.8 follow this KB article from apple: http://support.apple.com/kb/TS2762.