Displaying 20 results from an estimated 20000 matches similar to: "Samba 4 -> Group Policy Drive Map -> Access Denied"
2019 Jan 21
4
Samba 4 -> Group Policy Drive Map -> Access Denied
<?xml version="1.0" encoding="utf-8"?>
<Drives clsid="{8FDDCC1A-0C3C-43cd-A6B4-71A6DF20DA8C}"><Drive
clsid="{935D1B74-9CB8-4e3c-9914-7DD559B7A417}" name="W:" status="W:"
image="2" changed="2019-01-21 18:36:07"
uid="{6524E6E3-E107-48CC-9973-406E16B5F34D}" userContext="1"
2019 Jan 21
2
Samba 4 -> Group Policy Drive Map -> Access Denied
user configuration -> Preferences -> Windows Settings -> Drive Maps
Item Level Targeting -> Security Group, Domain Users
On 1/21/2019 11:09 AM, Luke Barone via samba wrote:
> Where is the policy targeting - the user or the computer?
>
>
> On Mon, Jan 21, 2019 at 7:51 AM Marco Shmerykowsky PE via samba <
> samba at lists.samba.org> wrote:
>
>> I seem
2019 Jan 22
1
Samba 4 -> Group Policy Drive Map -> Access Denied
Hai,
If you dont mind to share the OS and Samba version you are using?
Because we dont see this much:
> Thanks. Just ran "samba-tool ntacl sysvolrest" and that seems
> to have fixed the issue.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Marco Shmerykowsky PE via samba
> Verzonden: maandag
2019 Jan 21
0
Samba 4 -> Group Policy Drive Map -> Access Denied
OK, the preference is set correctly. Have you run a "samba-tool ntacl
sysvolcheck" on your first domain controller? That will check the
permissions. If you have additional domain controllers, ensure you're
connecting to the one holding the PDC Emulator role (typically your first
DC) in your GPMC.
If the sysvolcheck says everything is fine, and you only have one domain
controller,
2019 Jan 21
0
Samba 4 -> Group Policy Drive Map -> Access Denied
OK, remove the Item Level Targeting - that should hit all Domain Users
anyways.
Can you extract the .XML file that is made from that policy? Go to your
SYSVOL\<domain>\Policies\<GUID for Policy>\User\Preferences\Drives, and
open up "Drives.xml". Copy and paste the contents of that file into the
mailing list.
On Mon, Jan 21, 2019 at 10:23 AM Marco Shmerykowsky PE via samba
2018 Dec 05
4
Samba4 Kerberos Authentication Error
On Wed, 5 Dec 2018 10:56:48 -0500
Marco Shmerykowsky PE via samba <samba at lists.samba.org> wrote:
>
> On 12/5/2018 10:37 AM, Marco Shmerykowsky via samba wrote:
> > On Wed, December 5, 2018 9:52 am, Rowland Penny via samba wrote:
> >> On Wed, 5 Dec 2018 09:41:13 -0500
> >> Marco Shmerykowsky via samba <samba at lists.samba.org> wrote:
> >>
2018 May 24
3
Windows 10 Client - Samba 3 Server - NT4 Style PDC
I suggest reading this:
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
Imo, the longer you wait with samba AD the harder it gets to get things running.
You could better spend you time on settting up and migrating to AD the keep putting time in a dying product.
But thats my optinion.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
>
2018 Dec 28
5
Samba 4.9, RSAT, Windows 10 - "Cannot Manage the operating System..."
I'm trying to get an Samba AD setup. I thought I had RSAT working, but
when I launch the server manager I get the error message:
"Error - Cannot manage the operating system of the target computer"
I can ping the computer and the internal DNS seems to be working.
I can manually create shares & I can browse netlogon and sysvol
of the AD server.
Am I missing something or is this
2018 Dec 28
1
Samba 4.9, Group Policy, Drive Map
I'm trying to create drive maps via group policy.
I've created a new group policy object which is linked to the
internal location (ie internal.company.com) and has
Security Filtering of "Authenticated Users"
I edit the policy and go to the following:
User Config -> Preferences -> Win Settings -> Drive Maps
Action: Update
Location: \\AD-server\test-share
Label as:
2018 May 24
3
Windows 10 Client - Samba 3 Server - NT4 Style PDC
I have an old setup that serves my purposes, but which I'll move over
to a more modern Samba4 setup at some point. I know it's old,
deprecated etc.
In any case, at the moment I'm having a problem with two Windows 10
machines connecting to the domain I set up.
The network is a mix of XP, Windows 7 and Windows 10 machines.
Four (4) windows 10 machines connect to the domain after the
2019 Feb 17
2
SAmba 4.9 and Win XP Clients
I tried the NTLM setting. No change.
When I try to browse the network, I get the following error:
"internal is not accessible. You might not have permission to
use this network resource. The list of servers for this workgroup
is not currently available."
Here is the smb.conf from the AD machine.
[global]
netbios name = MACHINE251
realm = INTERNAL.DOMAIN.COM
2019 Feb 19
3
Computer Management - Share Security - No Read Access
I suggest you start with :
1770 /server (+ creator owner )
3770 /server/programs ( + creator owner + creator group. )
Then check again with getfacl
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Marco Shmerykowsky via samba
> Verzonden: dinsdag 19 februari 2019 23:13
> Aan: Rowland Penny
> CC: samba at
2019 Feb 18
2
Computer Management - Share Security - No Read Access
No. If it was mentioned in any of the samba docs consulted, then I missed it.
On February 17, 2019 9:43:18 PM EST, Luke Barone via samba <samba at lists.samba.org> wrote:
>Did you add the seSecurityPrivilege permission for Domain Admins as
>well?
>
>On Sun, Feb 17, 2019 at 3:13 PM Marco Shmerykowsky via samba <
>samba at lists.samba.org> wrote:
>
>> Can't
2018 Dec 05
2
Samba4 Kerberos Authentication Error
On 12/5/2018 12:28 PM, Rowland Penny via samba wrote:
> On Wed, 5 Dec 2018 12:19:39 -0500
> Marco Shmerykowsky PE <marco at sce-engineers.com> wrote:
>
>>
>>
>> --
>>
>> Marco J. Shmerykowsky, PE, F.ASCE
>> marco at sce-engineers.com
>>
>> -----------------------------------------
>> Shmerykowsky Consulting Engineers
2019 Jan 22
1
Password change log/que ir?
Hi! There are some way to see who change a password?
El lun., 21 ene. 2019 15:28, Luke Barone via samba <samba at lists.samba.org>
escribió:
> OK, remove the Item Level Targeting - that should hit all Domain Users
> anyways.
>
> Can you extract the .XML file that is made from that policy? Go to your
> SYSVOL\<domain>\Policies\<GUID for
2019 Jan 03
1
Samba 4.9, RSAT, Windows 10 - "Cannot Manage the operating System..."
On 1/2/2019 11:59 AM, Rowland Penny via samba wrote:
> On Wed, 2 Jan 2019 10:43:32 -0500
> Marco Shmerykowsky PE <marco at sce-engineers.com> wrote:
>
>>> /etc/hostname
>>
>> machine123
>>
>>> /etc/hosts
>>
>> 127.0.0.1 localhost
>> 127.0.1.1 machine123.company-internal.company.com machine123
>
> The
2019 Feb 17
2
SAmba 4.9 and Win XP Clients
Thanks. Will check.
I should have added that everything was working fine on the old winNT style samba domain setup. Its something related to the new samba AD setup
On February 17, 2019 8:17:03 AM EST, Rowland Penny via samba <samba at lists.samba.org> wrote:
>On Sun, 17 Feb 2019 07:51:24 -0500
>Marco Shmerykowsky via samba <samba at lists.samba.org> wrote:
>
>> In
2019 Feb 26
2
Samba AD Internal DNS, Postfix & Email Relay
That parameter isn't defined in my main.cf file.
Is I add it and leave it blank. It still doesn't work.
On 2/25/2019 11:41 PM, Reindl Harald wrote:
>
>
> Am 25.02.19 um 22:39 schrieb Marco Shmerykowsky PE via samba:
>> On 2/25/2019 3:36 AM, L.P.H. van Belle via samba wrote:
>>> Hai Marco,
>>>
>>> For you own domains, dont point postfix to your
2019 Feb 25
2
Samba AD Internal DNS, Postfix & Email Relay
On 2/25/2019 3:36 AM, L.P.H. van Belle via samba wrote:
> Hai Marco,
>
> For you own domains, dont point postfix to your internal DNS only,
> if done wrong you might miss dns info on the wan side and thats mostlikely your error .
Likely. Here is the error (ignore the ip's - messed them
up for this response):
Feb 25 16:22:10 sce252 postfix/smtp[3114]: 0D1E86E3A6D:
to=<marco
2019 Aug 01
5
Samba 4 & Thunderbird Mail Client
I'm running Samba 4 and I've created a share on a
member server to hold the message files for the
Thunderbird email client.
Over time I seem to get corruption of the message
files to the point where the folder file needs
to be reconstructed outside of Thunderbird.
In other cases, the file corruption in combination
with folder compaction results in deletion of
the messages in the folder.