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

FWIW; I connected to the domain on the rolled back 1703 machine. It wasn't connecting due to spelling errors on my end when setting the various keys (Damn those post 40 eye/vision things - don't get older kiddies). Base on my experiences then, if you're connected to the NT4 style domain prior to the 1803 update, then you'll stay connected. On all my 1803 machines, the domain

Hai, Yes, i get it, thats the same everywhere. And i know that problem also, but then i really suggest get people in to helpout. Believe me, you will be running into problems and get even less time the longer you wait. Base on this : > specified domain does not exist or could not be contacted error". Try \\ip it that works wait 5-15 min then try the nbtstat again. Not working,

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

Am 24. Mai 2018 05:44:04 MESZ schrieb Marco Shmerykowsky via samba <samba at lists.samba.org>: >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.

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

The issue does not seem to be connected to SMB1. It can be installed and it still won't authenticate. Something has been changed to force authentication to AD/DNS either solely or as a first step. The translation of the netbios name never happens even if the computer can resolve the name. Given that the authentication thru netbios resolution seems to get grandfathered in provided the domain

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

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

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

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

Hi all, it seems that "NT4 style domain support" in windows 10 1803 is broken by accident. Read https://social.technet.microsoft.com/Forums/en-US/59183715-0c04-44f7-b5ea-bb37da4125a5/unable-to-join-domain-with-new-windows-10-computers-build-1803?forum=win10itpronetworking These patch will bring it back again: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4458469 However

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

Hi, folks, Just ran into a problem: someone with a new laptop, running Win 10, version 1709, tried to map their home directory (served from a CentOS 6.9 box, and it fails, with Windows complaining that it no longer supports SMBv1, and if you go to their site, you can install support for that manually.... The server running samba can *not* be updated to 7 - we have a lot of stuff based off

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

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

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

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 2019 11:02:55 +0000 > > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > >> On Tue, 19 Feb 2019 22:05:12 +0000 > >> Rowland Penny via samba <samba at