similar to: Van Belle Packages & Samba 4.15

On 15/02/2023 21:02, Marco Shmerykowsky wrote: > > On 2023-02-15 2:13 pm, Rowland Penny via samba wrote: >> On 15/02/2023 19:05, Marco Shmerykowsky via samba wrote: >>> I ran an 'apt-get update' and a 'apt-get upgrade' >>> samba with the packages referencing Van Belle >>> site for debian bister samba 415. >>> >>> After

Previously, I needed to downgrade Louis samba packages to Buster's defaults, which would then be upgraded to 4.13 by the dist-upgrade to Bullseye. This was on a Domain Member, so didn't touch my DC's or have to worry about DB format stepping (I hope). apt install samba=2:4.9.5+dfsg-5+deb10u3 python-samba samba-common=2:4.9.5+dfsg-5+deb10u3 samba-common-bin=2:4.9.5+dfsg-5+deb10u3

On 2/22/2023 10:42 AM, Rowland Penny via samba wrote: > > > On 22/02/2023 15:33, Marco Shmerykowsky PE via samba wrote: >> Understood on the behavior of the backports.? The intent of the >> question was does every component installed when configuring >> samba need to be from backports (ie? apt-get install acl attr samba >> samba-dsdb-modules samba-vfs-modules

o22.02.2023 20:35, Marco Shmerykowsky PE via samba ?????: > Makes sense.? However, the question started about doing > upgrades & not new installs.? It was advised to get to Bullseye > (which will essentially take samba backwards in version) and then upgrade using the backports. Once again, this is unnecessary and this is not what will happen if you just upgrade your distribution to

On 2/23/2023 12:46 PM, Michael Tokarev wrote: > o22.02.2023 20:35, Marco Shmerykowsky PE via samba ?????: >> Makes sense.? However, the question started about doing >> upgrades & not new installs.? It was advised to get to Bullseye >> (which will essentially take samba backwards in version) and then >> upgrade using the backports. > > Once again, this is

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

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