Connect to shared network printer on WinXP machine for all users (Slackware)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Connect to shared network printer on WinXP machine for all users (Slackware)
Hello,
I am new to Linux and I am not sure how to do this. I have a WinXP machine that has a shared printer. How do I configure Linux to find and then allow all users to use this resource?
per the reading, make sure LPrng package is removed, remove the printer, then add the printer again. i'm posting my /etc/printcap, and, my /etc/cups/printers.conf for you to look at. i connect to my windows printer via cups by way of samba so i hope this helps.
/etc/printcap
# This file was automatically generated by cupsd(8) from the
# /etc/cups/printers.conf file. All changes to this file
# will be lost.
hppsc2110|hppsc2110:rm=peacedog:rp=hppsc2110:
/etc/cups/printers.conf
# Printer configuration file for CUPS v1.1.19
# Written by cupsd on Sat Apr 3 10:02:35 2004
<DefaultPrinter hppsc2110>
Info HP PSC 2110, hpijs
Location
DeviceURI smb://usernameassword@WORKGROUP/SERVERNAME/hppsc2110
State Idle
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
AllowUser peacedog
AllowUser root
</Printer>
hope that gets you going, post any success/failure.
good luck.
/etc/cups/printers.conf
# Printer configuration file for CUPS v1.1.19
# Written by cupsd on Sat May 1 18:06:55 2004
<DefaultPrinter AddiePrinter>
Info Addie Printer
Location Addie
DeviceURI smb://Addie/HPPSC950
State Stopped
StateMessage
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
</Printer>
I realized I forgot to mention that the WinXP computer is part of a domain (flecks.us), but it is in the same intranet range 192.168.0.X as the linux. I do not know how to add the Linux machine to the domain (the settings necessary on the Linux box), if that is needed.
Yeah that is what I also get when I try that command. No suggestions other than try what has been suggested to/tried by me already. I am still trying to get it to work.
1. Are the Samba daemons running at the time that you're trying to add the printers? Neither of you with the problem has named your distribution, and all distributions do not necessarily set up Samba to run at boot without the user intervening. The Samba daemons are called smbd and nmbd, and are likely found in /usr/sbin (you can do a whereis smbd/nmbd to find or confirm their exact location). You can run the 'top' command in a terminal to see if they are running, or use the System Monitor of your DE to see the currently running processes. If not, you should start the daemons by opening a terminal, using the 'su' command to switch to a root terminal, and then run the daemons. If everything else is properly configured, the printer may now be able to be added and work properly. If you've had to start them manually, check your distribution's documentation for how to add them to the default runlevel so they start automatically.
2. Stupid question, but you both are trying to add these printers as root, right? Only root has the right to manage hardware.
Configuration issues:
1. Look at /etc/samba/smb.conf. Is the workgroup/domain set to the same as the Windows workgroup/domain that shares the printer? The default Samba workgroup is usually wrong, and if it is, you won't be able to connect to the printer, as you are not a member of the authorized group to use it.
2. In my experience (HP printer directly connected to a Win2K machine via a workgroup and not a domain), the only command that successfully adds the printer in a working state is smb://username:password@ip_of_the_windows_box_(but you can maybe use the hostname instead)/share_name_of_the_printer.
There are a couple of caveats with this command; the user/pass must be known to the Windows box(meaning the user must be added to the list of known users by the Windows Administrator), and the user must have administrative privileges on that box. Otherwise, apparently CUPS won't have access to some file that it needs to add the printer. This may also be a fluke of my particular printer or setup with Win2K; certainly this is not an issue with Win98 (which doesn't even have administrative rights), and it may be possible to work around this with a finer-grained user security policy (or by having an "extra" box used exclusively as a print server, which wouldn't have anything that might be in danger of being hacked in the first place).
If necessary, it's very unfortunate, though, as the "smb:\\blah_blah_blah" command is sent in cleartext. But there seems to be nothing to be done except to make a junk admin who doesn't have access to any other shared files on the network, and to make sure your firewall is protecting you from unauthorized outside access so that this data won't get hacked.
3. As for the "lpadmin: add-printer (set model) failed: client-error-not-found" error that a1flecke and bbo report, this Samba+CUPS HOW-TO (which both a1flecke and bbo should read, it seems quite comprehensive) indicates that:
Quote:
If you received "error: client-not-possible" then chances are there is a typo
in your URI, or your link to smbspool is missing or pointing to the wrong place.
So that's pretty clear. I think that whatever is not covered by my post is covered by the document linked above, so I hope that this information helps to solve the problems that both of you are encountering. Good luck.
FYI: This is not a dead thread, I am working on this in my spare time. I have made some progress. lpadmin is now working without error. It was a combination of samba not starting when it should and have an incorrect link. Now the problem is that the printer keeps stopping right after I start it. Possibly a result of uninstalling LPRNG. Looks like lpr and other commands are incorrectly refering to the LPRNG package and not CUPS. If that is the case, what in CUPS do I redirect them to?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.