ClearFoundation

Running ClearOS Community 6.3.0 beta.

I have Windows Networking and Print Server installed.

I've installed the cups-pdf package like this:



Under: Server | File | Advanced Print Server | Go to Print Server Management Tool

I created a Class and added the Cups-PDF printer to the class.
Under Maintenance I printed a Test Page and this Test Page appeared under root's directory so I know the printer is working.

Under the Administration Tab I selected:


So now I want to use this printer from some of my Windows XP domain clients.

Samba is set as PDC and the XP clients can join the domain just fine.

In one of the XP clients in a Command Prompt window I ran:


This gave me the mapped drives from ClearOS machine but no printer was listed.

I then added root to smbpasswd:


So then adding the cups-windows drivers:


But still no luck.


How do I get this Cups-PDF printer to be visible and usable by the XP clients?

.

hi there,

I am having a similiar problem to you with CUPS and i was wondering if you had managed to get any further with resolving your issue.

I get to the point where I am running the make command and get the following error


Any ideas as to what I am doing wrong? Cups-PDF is showing up in the advanced printer manager, i can see it on my Windows 7 machine, I just can't install the driver for it in Windows.

Nope, I gave up.

.

Those steps seem odd to me.

Please see this thread.

Regards,

Georger

EDIT: It's also worth saying there's NO NEED to change any parameter in Samba nor in CUPS. All you need to do is copy the PostScript drivers from a Windows PC to /usr/share/cups/drivers (that's for 32-bit), restart Samba, and run the commands as described in the thread I pointed earlier.

Hi georger,

I've currently got my driver files in /usr/share/cups/drivers and when running the command


Everything seems to run properly the driver files are getting copied to /var/samba/drivers/W32X86, i get the Printer Driver PDF successfully installed and then immediately afterwards i get an NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86, which i would assume is because it just finished being created.

Any ideas as to what I could be doing wrong?

Gerry, in regards to the issue you posted about did you add a samba password for root since you are using it in the cpsaddsmd command?

arobinson wrote:
Hi georger,

I've currently got my driver files in /usr/share/cups/drivers and when running the command

Code:

cupsaddsmb -H localhost -U root -v -a

Everything seems to run properly the driver files are getting copied to /var/samba/drivers/W32X86, i get the Printer Driver PDF successfully installed and then immediately afterwards i get an NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86, which i would assume is because it just finished being created.

Any ideas as to what I could be doing wrong?
Did cupsaddsmb terminate, even after outputting NT_STATUS_OBJECT_NAME_COLLISION making remote directory \x64? If it did, I believe it worked just fine, because it happened to me as well. It's not an error.

I just installed COS 5.2 on a VM and did this from scratch:

1) Configured COS as a Samba PDC (configured Printing to "Point and Click")
2) Installed CUPS-PDF (showed up in the CUPS web GUI after installing from the command line)
3) Installed a network printer (an old Kyocera I named LAB-KM2810)
4) Created /usr/share/cups/drivers and /usr/share/cups/drivers/x64, and copied the appropriate drivers to each directory
5) Restarted Samba so that the newly created CUPS print queues would show up
6) ran and got the following output:



This is exactly what I did on my production servers. You should be able to install the printers in your Windows clients just by double clicking the shared printer in Windows Explorer. It's that simple.

Gerry, in regards to the issue you posted about did you add a samba password for root since you are using it in the cpsaddsmd command?

Why do this? Just use winadmin.

Georger

Can't check right now. I'm at a different location from where that machine is installed.

Won't be back there for a couple weeks.

.

Hi georger,

When I try to add the printer in Windows 7, i can see it, i double click on the icon, windows trys to download the driver, says its checking windows update, but comes back with a no driver found error. i am able to browse to \clearos\print$ and see the list of drivers that are avaliable.

Also one other thing I noticed was that when it copies all of the files into the W32X86 directory it also creates a new directory named "3" and copies all of the driver files into this folder as well.

My print$ section of my smb.conf file looks like this


And my printers section is

arobinson wrote:
Hi georger,

When I try to add the printer in Windows 7, i can see it, i double click on the icon, windows trys to download the driver, says its checking windows update, but comes back with a no driver found error. i am able to browse to \clearos\print$ and see the list of drivers that are avaliable.

Also one other thing I noticed was that when it copies all of the files into the W32X86 directory it also creates a new directory named "3" and copies all of the driver files into this folder as well.

My print$ section of my smb.conf file looks like this

Code:

[print$] comment = Printer Drivers path = /var/samba/drivers read only = No browseable = Yes available = Yes guest ok = Yes

And my printers section is

Code:

[printers] comment = Print Spool path = /var/spool/samba printing = cups use client driver = No printable = Yes read only = No browseable = No available = Yes

Did you copy the appropriate files to each directory? For 32-bit Windows clients, you should copy the following files to /usr/share/cups/drivers:

Some of these are to be found at the CUPS SVN repository, and some of the others are found in a working Windows client. I got mine from a 32-bit Windows 7 Professional computer. Works fine on the 32-bit versions of 7, Vista and XP.

For 64-bit Windows clients, you should copy the following files to /usr/share/cups/drivers/x64:

Like before, some of these are to be found at the CUPS SVN repository, and some of the others are found in a working Windows client. I got mine from a 64-bit Windows 7 Professional computer. Works fine on the 64-bit versions of 7 and Vista.

There's a catch! As per this article, the 64-bit version of cups6.inf should be "decorated" to look like this (vanilla cups6.inf from the CUPS SVN repository won't work):


Finally, I can't really comment on your smb.conf since I haven't tried v6 yet, but I can tell you that it looks A LOT like what I have on v5:

From what I can see, you haven't configured a domain, but you have Samba setting Printing configured as "Point and Click". I believe that it should be able to work that way.

Regards,

Georger

Hi Georger,

It looks like the only thing I didn't have in place was a copy of the drivers in the /usr/share/cups/drivers/x64. After placing a copy of the drivers there and re-running


but I am still getting the same error where when double clicking on the printer it tells me that it can not find the driver.