magarner
asked on
Permissions Problem printing to a HP Jet Direct Attached Printer
We are running Solaris 9 and have several printers both serial and network. The problem we are experiencing is we can print to all the printers fine if we are logged in as root. We cannot print to the jet direct printers logged in as any user other than root. We just went live on a v240 from a 3500, everything worked fine on the 3500. The points are so high because none of the laser jet printers work until we get this resolved.
ASKER
I added the printers from scratch using hppi.
I treid your command on the 3500 and received the following
find: -perm: Bad permission string
find: path-list predicate-list
I treid your command on the 3500 and received the following
find: -perm: Bad permission string
find: path-list predicate-list
Oops, should be "-perm -4000". However, if you've installed the hppi software & created the printers from scratch, that may not be the problem.
Some thoughts on debugging printing:
What happens when the users try to use `lp` from the command line? An error message, or does the request just disappear? Is there anything in /var/lp/logs? Can users run `lpstat` to see the printer queues?
Check command ownership/permissions:
-r-s--x--x 1 root lp 22956 Jul 12 2002 /usr/bin/lp
-r-s--x--x 1 root lp 22460 Jul 12 2002 /usr/bin/lpstat
-r-s--x--x 1 root bin 19700 Jul 12 2002 /usr/lib/lp/bin/netpr
Check /dev/null is writable by user "lp"
Some thoughts on debugging printing:
What happens when the users try to use `lp` from the command line? An error message, or does the request just disappear? Is there anything in /var/lp/logs? Can users run `lpstat` to see the printer queues?
Check command ownership/permissions:
-r-s--x--x 1 root lp 22956 Jul 12 2002 /usr/bin/lp
-r-s--x--x 1 root lp 22460 Jul 12 2002 /usr/bin/lpstat
-r-s--x--x 1 root bin 19700 Jul 12 2002 /usr/lib/lp/bin/netpr
Check /dev/null is writable by user "lp"
I never have to use 3rd part software for *nix printer installations.(there might be a bug in
the package, or miss configured for the 3rd part software!)
I normally use command line or Solaris (GUI) admintool to install printers. I think it is
easy to run "admintool" to install your printers:
1) If you try to setup a Solaris Printer server, you don't need any third party software, all
you need to do is to connet the printer to the Sunbox then run the GUI tool:
admintool &
to add a local printer.
see http:Q_20607008.html for more details
In this case, the printer server IP is the IP of this Sunbox !
2) If you want to access to a network printer, the printer server IP is the machine's IP which
the printer direct connted to, Or if the printer has a NIC card, the IP of the printer card is
the printer server IP.
to access to the printer, you need to run "admintool" and add a remote printer.
see http:Q_20268256.html for more details.
the package, or miss configured for the 3rd part software!)
I normally use command line or Solaris (GUI) admintool to install printers. I think it is
easy to run "admintool" to install your printers:
1) If you try to setup a Solaris Printer server, you don't need any third party software, all
you need to do is to connet the printer to the Sunbox then run the GUI tool:
admintool &
to add a local printer.
see http:Q_20607008.html for more details
In this case, the printer server IP is the IP of this Sunbox !
2) If you want to access to a network printer, the printer server IP is the machine's IP which
the printer direct connted to, Or if the printer has a NIC card, the IP of the printer card is
the printer server IP.
to access to the printer, you need to run "admintool" and add a remote printer.
see http:Q_20268256.html for more details.
ASKER
I have removed and readded the printers - I have compared everything file that I am aware of for permissions. Still root is the only user that can print. The response by yuzh is not the same as my environment - these printers are not part of any windows environment they are exclusively used by the Solaris box. I found a doc on HP's site that describes my problem but the fix did not work.
Any other suggestions.
Any other suggestions.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Congratulations! But I'm burning with curiosity, please tell me which step in that document actually solved the problem - Permissions on /var/tmp or the ~/.jpiu (which I've _never_ seen before...)???
AFAIK, yuzh's solution will work for "networked" OR "remote" printers; My only concern is that using the admintool & netstandard driver won't use the more advanced features of a printer, e.g. Landscape. Bu that's a long running dabate between Greg and me, so you don't want to get involved ;-)
Greg, can you PAQ and refund the points on this question or does magarner need to post a request in Community Support?
AFAIK, yuzh's solution will work for "networked" OR "remote" printers; My only concern is that using the admintool & netstandard driver won't use the more advanced features of a printer, e.g. Landscape. Bu that's a long running dabate between Greg and me, so you don't want to get involved ;-)
Greg, can you PAQ and refund the points on this question or does magarner need to post a request in Community Support?
Have you tried adding a printer from scratch?
Do you still have the 3500 up and running? If so, try `find /etc /var /usr -perm +4000 -exec ls -ld {} \;` to list files that have SUID bit set.
And if you can't solve the problem quickly, you could use the 3500 as a print server temporarily ;-)