Samba/Cups print server

[Geoff]

I've successfully mastered this and it's live in our AD based network now so if anyone is thinking about doing the same feel free to throw questions at me.

 

If you just want a 1000ft overview, I suggest you read my blog post about it.

 

http://sa-ime.blogspot.com/2007/02/implementing-linux-print-server-with.html

[ChrisH]

Rics got a guide in the works as well.

[Ric_]

The guide for installing and configuring CUPS with Samba is complete... it's just the Pykota part that isn't finished as something isn't quite right yet.

 

If anyone is desperate for the CUPS stuff, PM me and I will post it up... otherwise you may have to wait a couple of weeks until the Pykota bits are added to the document.

[SimpleSi]

@geoff

Your links just giving gibberish with me

 

regards

 

Simon

[ChrisH]

Works ok for me.

[localzuk]

All of blogspot is filtered for me...

[johngd]

I've tried this system too using Centos 5 but not using Postscript printers.

 

The nice thing about Windows as a print server is that when you connect for the first time the driver is downloaded to your PC automatically.

 

That's where I came unstuck because I had to install the driver manually when I connected. That's OK but I use a log on/off script that installs the local room's printers at log on and removes them at log off.

 

So the real question is: how do we get the U**x box to provide the Windows drivers automatically?

 

John D

Ipswich School

[Geoff]

1. Download the printer driver from the vendors homepage, and extract it somewhere on your computer.

2. Navigate to the print server in the Network Neighborhood, when prompted for username and password, use the root user that you added to samba in the previous section.

3. Enter the printers folder.

4. Right click on the printer, and click Properties.

5. When it asks if you want to copy the driver, click NO .

6. Now, go to the Advanced tab, and click New Driver... (If it's greyed out, you might have "use client driver" set to yes in /etc/samba/smb.conf.

7. Follow the guide on screen.