CIFS 9000 printing to a W2K domain

[enrico.nic]

Hi

I am trying to print from my HP-UX samba server to a color printer (PS, PCL enabled), where the printer queue is on a Windows 2003 (PDC) server.
We have created a user account specifically for this job.
From the hp-ux command line, I can successfully print with the command:
# /opt/samba/bin/smbspool smb://W2KDOMAIN\\dumbuser:password@printserver/lasercolor 101 Username MyFile 1 a /path/filename

(all of these parameters are to be given to the smbspool command, even if useless)

And this works until I try to set up the printer in the samba configuration file, to let the win clients print from the HP-UX queue. The added section:

[lasercolor]
printable = Yes
comment = Gestetner 7116
path = /tmp
valid users = @users
printable = Yes
print command = /opt/samba/bin/smbspool smb://W2KDOMAIN\\dumbuser:password@printserver/lasercolor 101 Username MyFile 1 a /tmp/%s; r
m /tmp/%s

does not work at all.

I know to cleaner solution would be to let the win clients print directly from the W2K queue, but some of them don't log on directly on the windows domain controller.


Has anyone an idea ?

Even a print script would be fine, I haven't found it on the samba 3 book from A. Tridgell.

Thank you

Enrico

[Micky_1]

Hi Enrico,

I think it's the "valid users =" section.
If you're locally, you don't have to deal with the security features of samba.

You haven't told if users are authorized via samba. The printshare just says, that only authorized users in the group users are allowed to print...

You should examine the samba-log to see as which unix-users the users from the clients are connected to samba.

Micky

[enrico.nic]

The group is used just to let only the users of our department print from this printer.
It is working as a share, since I can set up the printer from the win client.
The problem is during the printout: and from the samba or sys logs I don't see anything about the file copy to the server.

Thank you for any further advice

Enrico

[Micky_1]

try to put your "smbspool smb://...." into a script and execute the script from samba.
maybe you have problems with the slashes and backslashes...