Nick Couchman wrote:
I'm attempting to configure Samba with CUPS as a centralized print server. I've done this in the past -
my current production server is running Samba 3.2.14. On my current production server, I have several
users set up as either "admin users" or "print admin" users so that they can manage
the drivers, etc., on the Samba server. In setting up my new server, I'm running into some issues with
this. The main problem is that, no matter what options I change for the printers and print$ shares, and
no matter what users I add in as either admin users or printer admin users, when I go to the properties
of either a printer or the entire server, everything is read-only. I cannot add/upload drivers to the
server, etc. I've even manually gone to the \\<servername>\print$ share and verified that I have
write access to that folder. But, for some reason, I cannot add drivers, change settings, etc., on the
new server. Differences are:
- Old Server: Gentoo; New Server: openSuSE 11.2
- Old Server: Samba 3.2.14; New Server: Samba 3.5.3
- Old Server: NT4 Domain Member; New Server: ADS Member
As far as the differences go, I've already verified that the same behavior
occurs when the new server is part of the NT4 domain instead of the AD domain.
So, I'm really down to either something having changed in Samba versions
sometime after 3.2, or something about how the packages are compiled. Perhaps
someone can help me figure out what I'm missing that's causing this behavior?
Find my smb.conf file below...
Thanks - Nick
Have you looked at granting rights like:
net -U"ADuser" rpc rights grant "ADdomaingroup" SePrintOperatorPrivilege
There are several different privileges that can be granted in this manner.
--
Mike Rambo
NOTE: In order to control energy costs the light at the end
of the tunnel has been shut off until further notice...
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
