[Samba] Oh, that is CAN'T print -- Re: Can print when logged in as domain user

[Robert Moskowitz]

Perhaps some people were wondering from the subject what the issues were!

Obviously there is a solution to this. Either there is something NOT 
right about my PDC setup or some special tool for getting the policies 
set up right. There SEEMS to be a need for a special policy to allow 
domain users to access the local printer or to access a printer share...

I am NOT using LDAP for the PDC, all users are Linux users with their 
own /home/user directory as their Home share.

On 10/22/2010 04:50 PM, Robert Moskowitz wrote:
>
>
> On 10/22/2010 04:17 PM, Robert Moskowitz wrote:
>> On 10/22/2010 04:03 PM, Lukasz Zalewski wrote:
>>> On 22/10/2010 20:38, Robert Moskowitz wrote:
>>>> On 10/22/2010 03:22 PM, Chris Smith wrote:
>>>>> On Fri, Oct 22, 2010 at 2:43 PM, Robert 
>>>>> Moskowitz<rgm at htt-consult.com>
>>>>> wrote:
>>>>>> This is an OEM installed XP from a resaler. I would NOT be supprised
>>>>>> that
>>>>>> there are some serious limitations on the XP installed.
>>>>> No functional limitations on OEM versions, except that some were tied
>>>>> to specific manufacturers (they wouldn't install if the BIOS string
>>>>> did not identify the device as that manufacturers).
>>>>
>>>> The license is an OEM license (per system properties) registered to 
>>>> the
>>>> E-Waste Recycler I bought it from. It is an IBM SFF.
>>>>
>>>> But why no policies for allowing printing when attacked to a 
>>>> domain? Why
>>>> not connect when domain logged in.
>>> Robert,
>>> Are you using AD for group policy, samba (system policy) or local 
>>> group policy. I have noticed, that on my XP client machines not all 
>>> of the policies are present until you add appropriate templates 
>>> (don't know if its SP3 "feature"). If you right-click on 
>>> Administrative templates, there will be an option to Add/Remove 
>>> templates. The required policy is part of system.adm
>>
>> I don't know what policy I am using. I suppose whatever is installed 
>> on the system?
>>
>> Oh, NOW I see what I was doing wrong. Now I have added system.adm 
>> policy and I see printers. Here goes!
>
> Well I enabled a couple of things.
>
> I disabled: Disallow install of printers using ker-mode drv
> I enabled: Allow print spooler to accept clients
> Web-based printing
>
> I could not figure out what really to do.
>
> This has not made any change to the system behaviour :(
>
> I am off now until Saturday night. I will look for help again then!
>
>>
>>>>
>>>> I tried connecting to the server printer share from a local login, and
>>>> that got past the policy block and was asking for the printer 
>>>> driver. So
>>>> it is REALLY something tied into how a domain user acts on this 
>>>> system.
>>>>
>>>>
>>>
>>>