similar to: Upgrade from 3.6.9 to 3.6.23 - Lost authentication

Hello, thanks in advance for the support! My samba server is samba-3.6.23-45.el6_9.x86_64, on Scientific Linux 6. Using a Mac it is possible to associate a color label to a file (suppose a word document). This can be done on the samba share too, but if I edit the file and save the changes the color label is lost (like if it is reset to empty). When the file is local or it is in shared volume

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----- >

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

On 2019-02-17 10:54 am, Rowland Penny via samba wrote: > On Sun, 17 Feb 2019 10:37:48 -0500 > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > > >> >> Seems I can map a drive from the command line. (Didn't check that >> - it was 2:00am and I was tired with fighting this stuff) > > Time you went to bed ;-) > > its 15:45 Sun here. >

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: > >>

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

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

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

--- Marco J. Shmerykowsky, P.E. marco at sce-engineers.com -------------------------------------------- Shmerykowsky Consulting Engineers Structural Analysis & Design 102 West 38th Street, 2nd Floor New York, New York 10018 Tel. (212)719-9700 Fax. (212)719-4822 http://www.sce-engineers.com -------------------------------------------- On 2019-02-19 4:22

On 2019-02-19 3:47 pm, Rowland Penny via samba wrote: > On Tue, 19 Feb 2019 15:25:51 -0500 >> What exactly does "START AGAIN" imply? Just chmod? > > 'ls' shows the correct ownership and Unix permissions: > > drwxrwx---+ 4 root domain admins 4096 Feb 17 19:13 programs > > But 'getfacl' show something different: > > getfacl:

On Thu, 21 Feb 2019 11:12:05 -0500 Marco Shmerykowsky <marco at sce-engineers.com> wrote: > > On 2019-02-21 10:57 am, Rowland Penny via samba wrote: > > On Thu, 21 Feb 2019 10:39:47 -0500 > > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > > > >> > >> On 2019-02-20 7:12 am, Rowland Penny wrote: > >> > On Wed, 20 Feb

Hi, thanks for all the feedback and topics. May be I can/should draw a better picture of my settings and question. We "still" use samba 3.6.9-167 from Red Hat with an openldap backend. I tried from an older posting somewhere: socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536 But there was no noticeable impact. The log level = 2. Thats all I changed

On 2019-02-17 10:17 am, Rowland Penny via samba wrote: > On Sun, 17 Feb 2019 09:53:56 -0500 > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > >> 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

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

<?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"

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

Following the "User Home Folders" page on the wiki using Group Policy https://wiki.samba.org/index.php/User_Home_Folders I see this page was last updated in March 2017. Not sure if anything has changed. Although I can access the shares, the %LogonUser% directory does not seem to be automatically generating. Thoughts? Share definition: [users] path = /server/users read only = no

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

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

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