# should I be able to set printers and folder option via group policy?

Aaron Solochek aarons-samba at aberrant.org
Sat Sep 4 14:30:56 MDT 2010

On 09/04/2010 03:59 PM, Matthieu Patou wrote:
>
>>> Don't think so, search the errors. send us the trace (if not too big).
>>>
>>> Matthieu
>>>
>>
>> Ok, after running wireshark it appears the problem is a combination of
>> the
>> create request coming from the group policy editor being this:
>>
>> Disposition: Open (if file exists open it, else fail) (1)
>> Filename:
>>
>>
>> and that file not existing by default.  I got rid of the error by
>> creating the
>> Printers\Printers.xml file manually on the file server (containing
>> nothing more
>> than<?xml version="1.0" encoding="utf-8"?>) Indeed, adding printers then
> Great news ! I'll try to have a look in a couple of days on how the
> default policy look like on w2kx server maybe this files are indeed
>> One other problem related to this is that I was unable to manually
>> create that
>> file via samba.  I opened up \\bar.com\Sysvol\...\Preferences and
>> right-clicked
>> to create the Printers folder, but I got this error:
>>
>>> Could not find item. This is no longer located in
>>> Verify
>>> the item's location and try again.
>>>
>>> Preferences Type: File Folder Date Modified: 9/1/2010 5:14 PM
>>>
> Just to be sure so when you try to open:
> you get this error message ?

No, I am able to open that path without issue.  It's only when I try to create a
new folder in that Preferences folder that I get an error.

>
>
>> Via wireshark, I see:
>>
>>> 296    13.754035    10.1.10.20    10.1.10.10    SMB2    Create
>>> Request File:
>>>
>>> folder
>>>
>>> 297    13.754471    10.1.10.10    10.1.10.20    SMB2    Create
>>> Response, Error:
>>> STATUS_OBJECT_NAME_NOT_FOUND
>>>
>>> 298    13.754913    10.1.10.20    10.1.10.10    SMB2    Create
>>> Request File:
>>>
>>> Request
>>>
>>> 299    13.755070    10.1.10.10    10.1.10.20    SMB2    Create
>>> Response File:
>>>
>>> 300    13.755078    10.1.10.10    10.1.10.20    SMB2    Notify
>>> Response, Error:
>>> STATUS_PENDING
>>>
>>> 301    13.755097    10.1.10.20    10.1.10.10    SMB2    Cancel Request
>>>
>>> 310    13.787312    10.1.10.20    10.1.10.10    SMB2    Create
>>> Request File:
>>>
>>> folder
>>>
>>> 312    13.787749    10.1.10.10    10.1.10.20    SMB2    Create
>>> Response, Error:
>>> STATUS_OBJECT_NAME_NOT_FOUND
>> So for whatever reason, when windows (7, 64bit) requests that New Folder
>> creation, samba is coming back with an unexpected error.
>>
>> I can post the actual pcap of this, if someone can give me a quick way
>> to strip
>> out information identifying the domain it comes from.
> The basic questions: with which user do you do this ?
> What are the unix rights of the folders ?

-la .

total 80K
drwxr-xr-x 16 3000009 users 4.0K 2010-09-04 14:13 ./

that UID seems to be mine, since it's also the UID that my roaming profile is
created with.  However I'm still having issues with that, so perhaps that's
actually the problem.  What is the best way to verify this?

> What are the ntfs rights of the folders ?

When I try to view those (right clicking and going to properties->security tab)
I get "The requested security information is either unavailable or can't be
displayed"

At some point I noticed that my /etc/fstab was messed up and the space between
the type and options had disappeared, resulting in a type of "ext4user_attr"
Surprisingly the system seemed fine with that, but it was causing the extended
attributes to not work.  I don't know if that could be related or not, but
thought I'd mention it.

>
> For me it looks like the Preference folder has been created by someone
> else (because it's not done by the provision) and you don't have the
> right on it.
> Can you create a folder under the User folder ?
>

Actually, I wasn't able to create folders anywhere.  I turned off SMB2 and I was
able to create folders anywhere I felt, and was able to actually see the
security information for them.  So I guess SMB2 is the source for a lot of my
issues.  Hopefully turning that off solves everything.

-Aaron

> Matthieu.
>