Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm trying to setup a print server using Fedora Core 2. The printer is HP LaserJet 1010..... and I would like to have short and easy howto to make it able to share across the network. Samba has already running and it's running fine, just that I need to add in printing sharing, but I don't know where to start, and how to start it....
I know it is a Gentoo howto, and not a fedora howto, but the Samba3/CUPS/ClamAV howto on Gentoo's site is a pretty good guide to doing this.
What your going to want to do is skip to step 4, server configuration and then check out step 5 on the client configuration. If you don't have ClamAV, or don't care to implement auto-virus scanning, then just pay attention to the cups and samba config (and leave out the stuff in samba refering to virus scanning).
If you have any questions or are totally confused by these docs let us know and I'll try and answer any questions you might have.
All give you a fair warning, once the printer is setup in cups it is very easy to get samba to see it and broadcast the share... the tricky part is having samba automagically pass the driver to your windows clients so they can use it.
All give you a fair warning, once the printer is setup in cups it is very easy to get samba to see it and broadcast the share... the tricky part is having samba automagically pass the driver to your windows clients so they can use it.
Agreed. I'd even suggest skipping that part of the tutorial until you get the printer shared and can actually print to it.
Just a forewarning; if you can't get Windows clients to use the PS driver for CUPS, you can always make a share just for the Windows machines to print directly to, and have a share for the Linux computers to print to. That's what I do.
By the by, don't use ClamAV to do on-access scanning. It'll slow stuff down like hell. If you're worried about it, just get ClamAV and schedule it to do a scan one a day or twice a day.
Because when you set up with Samba, you automagically set up CUPS, too.
You can set CUPS to broadcast out the printers, and as long as the clients have CUPS installed, they see the printer and will communicate with it. Basically, with CUPS, the only "real" setup, if you will, is done on the server. And, you can use CUPS on the client Linux machines to admin the printer on the server. If I remember right.
That, and I've never dealt with IPP that I know of.
Ya.. that is what I ment. IPP is the protocol cups "clients" use to talk to cups "servers". They don't use samba at all to talk to each other. If you have cups set to broadcast it's printers then the cups clients on the network automatically see them and configure themselves to use it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.