Displaying 20 results from an estimated 2000 matches similar to: "leaving a domain?"
2024 Jun 20
2
leaving a domain?
20.06.2024 15:03, Michael Tokarev via samba ?????:
> Hi!
>
> I joined a newly installed samba (4.20.1) server to a domain, - just testing
> things.? Now I want to remove this test server from a domain, but I can't:
>
>
> root at svdcm2:/# samba-tool domain leave -U tls\\mjt-adm
> WARNING: Using passwords on command line is insecure. Installing the setproctitle python
2024 Jun 20
1
leaving a domain?
On Thu, 20 Jun 2024 15:07:11 +0300
Michael Tokarev via samba <samba at lists.samba.org> wrote:
> 20.06.2024 15:03, Michael Tokarev via samba ?????:
> > Hi!
> >
> > I joined a newly installed samba (4.20.1) server to a domain, -
> > just testing things.? Now I want to remove this test server from a
> > domain, but I can't:
> >
> >
> >
2024 Jun 20
1
leaving a domain?
20.06.2024 15:16, Rowland Penny via samba wrote:
> On Thu, 20 Jun 2024 15:07:11 +0300
> Michael Tokarev via samba <samba at lists.samba.org> wrote:
>
>> 20.06.2024 15:03, Michael Tokarev via samba wrote:
>> Still, it'd be nice if samba-tool domain leave displayed some more
>> appropriate error message, and no insecure-password-on-command-line
>> warning
2024 Jun 20
1
leaving a domain?
20.06.2024 17:01, Ralph Boehme wrote:
> On 6/20/24 2:03 PM, Michael Tokarev via samba wrote:
>> How to remove this machine from a domain?
> net ads leave ...
Yeah, I tried that one right after `samba-tool domain leave` - it
complains there's no way to leave a domain if joined as a DC.
I *guess* this is the error `samba-tool domain leave` faces too,
just without proper error
2024 Jun 20
1
leaving a domain?
On 6/20/24 2:03 PM, Michael Tokarev via samba wrote:
> How to remove this machine from a domain?
net ads leave ...
-slow
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL:
2024 Jun 07
1
smbstatus: who opened the file?
In the smbstatus output, "Locked files" section, there's a list
of locked files (effectively opened files, since windows always locks
a file which it opens) and corresponding pid of smbd process. How to
map this information to user ID?
Thanks,
/mjt
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1
2024 Jun 07
2
DC upgraded to 4.20.1 - issues
On Fri, 7 Jun 2024 08:50:11 +0200
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
>
> on the problematic DC "systemctl status" doesn't even show
> "samba-ad-dc".
>
> Although:
>
> # systemctl status samba-ad-dc.service
> ? samba-ad-dc.service - LSB: Samba daemons for the AD DC
> Loaded: loaded
2024 Jun 07
2
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
07.06.2024 07:54, Jeremy Allison wrote:
>> msdfs is broken in 4.19.? It worked fine in 4.18.
This is not entirely true.
>> Is no one using msdfs?? I wonder why I was the first to discover this?
>
> There must not be a test for your specific use-case.
>
> MSDFS is tested in the autobuild test suite. Can
> you articulate the problem well enough we can
> build a
2024 Jun 20
1
leaving a domain?
On Thu, 20 Jun 2024 15:19:35 +0300
Michael Tokarev <mjt at tls.msk.ru> wrote:
> 20.06.2024 15:16, Rowland Penny via samba wrote:
> > On Thu, 20 Jun 2024 15:07:11 +0300
> > Michael Tokarev via samba <samba at lists.samba.org> wrote:
> >
> >> 20.06.2024 15:03, Michael Tokarev via samba wrote:
>
> >> Still, it'd be nice if samba-tool domain
2024 Jun 07
2
4.20: case (in)sensitive is broken
Hi!
This is a heads-up for now, more debugging to follow.
I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20
broke case insensitive file access entirely. Only exact case
filename works, no matter which value is set in "case sensitive"
parameter.
In 4.19, things works again.
/mjt
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key:
2024 Jul 08
2
samba-ad-dc from debian backports fails to start with /usr/sbin/samba missing
08.07.2024 17:18, Sonic wrote:
> On Mon, Jul 8, 2024 at 6:46?AM Michael Tokarev <mjt at tls.msk.ru> wrote:
> ...
>> I think the main ingredient here is to have apt-listchanges package
>> installed (which, while part of standard install, is optional).
> ...
>
> I've always installed using the netinstall.iso which does not install
> that package. Will add it
2024 Jun 06
1
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
Hi!
For quite some time I'm trying to find what's going on with MSDFS referrals.
Samba version is 4.19.6.
We've global host msdfs = yes (the default anyway), and for a share in question,
msdfs root = yes. testparam confirms the settings.
There's a symlink created in the root dir of the share, which points to the same
server but different path:
dfstest =>
2024 Jun 07
1
DC upgraded to 4.20.1 - issues
Am 07.06.24 um 08:45 schrieb Michael Tokarev:
> Please check version of samba-ad-dc package, - is it the same as other
> samba package versions?
that package isn't installed according to "apt-cache policy" !
Seems it got lost while upgrading.
> Did samba-ad-dc start at all?
seemed like, but was very fast (so did nothing, as it seems)
Did "apt install
2024 Jun 10
0
mjt debian/ubuntu samba builds update
Hi!
I just uploaded binaries of samba versions 4.19.7-1 and 4.20.1-5 for ubuntu and
debian to the usual location, http://www.corpit.ru/mjt/packages/samba/ .
There are a few changes in there.
First, I changed debian release suffix to be like:
4.20.1+dfsg-5~mjt-deb11
4.20.1+dfsg-5~mjt-ubt24
This should not change anything, just make it easier to track if neded,
hopefully.
And for 4.20
2024 Jun 07
2
DC upgraded to 4.20.1 - issues
I run 2 DCs at a site, Debian 12.5, so far samba-4.19.6 from backports.
Today I upgraded one of them, this brought samba-4.20.1
Now on this one DC stuff like "wbinfo -g" fails:
# wbinfo -g
could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain name!
failed to call wbcListGroups: WBC_ERR_WINBIND_NOT_AVAILABLE
Error looking up domain
2024 May 31
1
maximum samba AD functional level?
Hi!
In the samba wiki there's this page: https://wiki.samba.org/index.php/Raising_the_Functional_Levels
which basically says that the maximum supported functional level is 2008_R2, and
that 2012 (and 2012_R2) are included but not supported.
This page mentions maximum samba version 4.4 and has been modified in 2017 (besides some
formatting changes).
What's the current situation?
Also,
2024 Jul 08
1
samba-ad-dc from debian backports fails to start with /usr/sbin/samba missing
07.07.2024 16:05, Sonic via samba wrote:
> On Fri, Jul 5, 2024 at 3:55?AM Michael Tokarev via samba
> <samba at lists.samba.org> wrote:
> ...
>> Please don't suppress *NEWS* entries.
> ...
>
> As someone that was bitten by this change I have to admit I've never
> seen these NEWS entries, or never realized I had. My Debian servers
> are cli only (no X or
2024 Jul 30
1
4.21-rc: new symbols form appeared
I'm trying to build 4.21-rc packages for debian, and noticed
that a new form of version info symbol appeared (only tried
tdb for now). In addition to usual
TDB.1.4.11 at TDB.1_4.11
symbol, it now also adds
TDB_1_4_11 at TDB_1_4_11
(with dots replaced with underscores), but for single version
only.
It doesn't look right :)
Thanks,
/mjt
--
GPG Key transition (from rsa2048 to
2024 Aug 03
1
4.21-rc: ldb_version.h is missing
31.07.2024 08:30, Douglas Bagnall via samba ?????:
> On 30/07/24 22:20, Michael Tokarev via samba wrote:
>> When building libldb as public library, its install target does not
>> install ldb_version.h header file, which is included from ldb.h, so
>> the resulting header files are unusable.
>
> It may be that 625fb48326ec62a33ce0abdbfb0f6f3d33d7cc64 accidentally reversed
2024 Jun 07
1
4.20: case (in)sensitive is broken
On 6/7/24 9:34 AM, Michael Tokarev via samba wrote:
> I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20
> broke case insensitive file access entirely.? Only exact case
> filename works, no matter which value is set in "case sensitive"
> parameter.
hm, can't reproduce:
$ bin/smbclient -U "slow%x" //localhost/test
smb: \> ls foo
foo N