Sharing a Windows 2K Printer WITHOUT Buying Server Hardware?
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Rep:
Sharing a Windows 2K Printer WITHOUT Buying Server Hardware?
I'm trying to share my Windows 2000 printer with the rest of my network, but I'm having trouble accessing it with my Linux machines. I've tried every possible solution I found here and elsewhere, and while all indications seem to show that it SHOULD work, I can't print from my RH7.3 box to my Windows-based printer. The only other solution I've seen is to buy a print server, and I'm trying to avoid this if possible.
Can you suggest a way to share the printer, and also an absolute way to test the connection?
Thank you.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Quote:
Originally posted by DavidPhillips what have you tried, and what were the results?
I've downloaded, installed, and configured Webmin (which seems like a pretty nice tool) to recognize my W2K printer. Everything seems very nice from there, and all the options seem ok, don't even get any errors back when I select the "test whether server is up" option on the print settings. I've also added the printer using printconf-gui in KDE; from there, I've sent countless test pages that all return the result popup: "sent US Letter PostScript Testpage to "EPSON880". But the page never shows up and I don't see anything in the Win2K print queue.
One other thing I did in accordance with a post I found on this site: added an entry to /etc/printcap.local, but this did nothing but add a "CATASHTROPHIC" error returned during boot so I've removed it.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
I can easily print to the W2K-shared printer from the WinXP client, but not from Linux.
This is the addition to /etc/printcap that was apparently made by Webmin, as I haven't touched the file myself:
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Quote:
Originally posted by DavidPhillips What's the /var/spool/lpd/EPSON880/.config file look like?
Perhaps this is part of the problem... this file does not exist! There are, however, 15 files in the directory, including an empty file control.pr and an interesting file called VOLATILE, which contains the following:
Code:
This directory was created by printconf for a printconf spool.
If printconf-backend does a spool rebuild, and finds volatile
directories that do not currently have valid configurations,
it will DELETE THEM!
printconf-backend detects volatility by the presence of this file.
If you have custom spool directories made in some other manor, they
will be safe from printconf-backend's deletion as long as they do
NOT have a file in them named 'VOLATILE'.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Thanks David. I created a new file and inserted these values only, with no other parameters.
Then I tried to print a file via lpr command, and it returned nothing, no error or job number. Here's the result of lpq:
Code:
[root@hatbox EPSON880]# lpq -P EPSON880
Printer: lp@hatbox (originally EPSON880) 'EPSON880 on deestos'
Queue: no printable jobs in queue
Server: no server active
Status: job 'root@hatbox+684' removed at 09:46:31.316
Rank Owner/ID Class Job Files Size Time
done root@hatbox+324 A 324 README 7005 13:29:59
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
After reading "man smbclient", I entered the following command successfully: smbclient -L <remoteHostName> -U <userName>%<passWord>
The command returned all available shares, including the printer:
Code:
Sharename Type Comment
--------- ---- -------
EPSON880 Printer EPSON Stylus COLOR 880
I believe this is the expected result, but shouldn't it then be working? Or do I now need to somehow store the username/password combination so that each time the client tries to print, it relays that information to the server?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.