Displaying 20 results from an estimated 100 matches similar to: "Cannot delete trust"
2025 Feb 16
0
SegFault verifying external trust
I think it's best that I don't put this into the bug system. I'm too removed from the development process, and I don't have the time to build a debug version. Not sure how helpful this will be.
Got the following segfault.
There are two domains: domain.brandlilaw.com and domain.brandli.com. There is an external trust between them. There were, at one time, 2-4 domain
2025 Feb 10
1
FW: Problems after DC upgrade
Update:
I had resolv.conf pointing to my dns servers on different machines, which serve other domains including brandli.com and have entries for the name servers of the ADS domain (domain.brandli.com). I change the pointer in resolv.conf to the local IP address, i.e. the samba internal dns. Now it resolves fully qualified names but not short names. I gather it does not look at the
2025 Feb 10
3
Problems after DC upgrade
It was systemd-resolved. I disabled that. Now samba is binding to the port.
But I'm still getting the dnsupdate failure.
And, I can't ping anything. I get the "unknown host or service" error. So names are not getting resolved on the machine. I have to admit to complete ignorance about how this part of linux works. When running systemd-networkd, what normally does name
2025 Feb 17
1
FW: Cannot access domain member from trusted domain user
More: users on the BRANDLILAW domain can access the share, but it's incredibly slow. In addition, smbd logs these errors repeatedly:
Feb 16 18:49:06 roberts smbd[136]: check_account: Failed to convert SID S-1-5-21-2136821272-1111453333-1140905514-1601 to a UID (dom_user[BRANDLILAW\admin-fh$])
Feb 16 18:49:06 roberts smbd[136]: [2025/02/16 18:49:06.365450, 0]
2025 Feb 17
2
Cannot access domain member from trusted domain user
I'm not able to access a samba file server that I recently created and joined to a domain. I have two domains with an external trust: BRANDLILAW and BRANDLI. The server is joined to BRANDLILAW. I am trying to access it from a user on the BRANDLI domain. This worked with the prior server that the new server is replacing. All domain controllers and the server are Debian backports (21.3).
2025 Feb 10
1
Problems after DC upgrade
You need to remove the symlink /etc/resolv.conf (probably points to
/run/systemd/resolved/stub-resolv.conf) and create a new /etc/resolv.conf
that has your DC as nameserver.
Den m?n 10 feb. 2025 15:57Stephen Brandli via samba <samba at lists.samba.org>
skrev:
> It was systemd-resolved. I disabled that. Now samba is binding to the
> port.
>
> But I'm still getting the
2025 Feb 10
1
Problems after DC upgrade
On Mon, 10 Feb 2025 02:24:31 +0000
Stephen Brandli via samba <samba at lists.samba.org> wrote:
> Well, it almost went okay.
>
> Thumbnail: I had two DCs, running the latest in buster. I created a
> new one running bookworm and 4.21.3. I joined the new machine as a
> DC. I then transferred the FSMO roles from one of the old ones and
> demoted that one. My plan is to
2025 Feb 17
1
FW: Cannot access domain member from trusted domain user
On Mon, 17 Feb 2025 03:09:45 +0000
Stephen Brandli via samba <samba at lists.samba.org> wrote:
> More: users on the BRANDLILAW domain can access the share, but it's
> incredibly slow. In addition, smbd logs these errors repeatedly:
>
> Feb 16 18:49:06 roberts smbd[136]: check_account: Failed to convert
> SID S-1-5-21-2136821272-1111453333-1140905514-1601 to a UID
>
2025 Feb 10
1
Problems after DC upgrade
Well, it almost went okay.
Thumbnail: I had two DCs, running the latest in buster. I created a new one running bookworm and 4.21.3. I joined the new machine as a DC. I then transferred the FSMO roles from one of the old ones and demoted that one. My plan is to create a fourth new one and demote the other old one. But, two problems:
1. The dns on the new DC is not responding. It did
2025 Feb 12
1
DNS Update problems
Roland, thanks for the reply.
>I think I can explain that, does /etc/hosts contain a line similar to
>this:
>x.x.x.x member.samdom.example.com member
Yes. /etc/hosts:
127.0.0.1 localhost
10.65.187.15 tower.domain.brandli.com tower
::1 localhost ip6-localhost ip6-loopback
Ff02::1 ip6-allnodes
Ff02::2 ip6-allrouters
Where .15 is tower's ip address, and domain.brandli.com is the
2025 Feb 12
1
DNS Update problems
Still having problems with DNS Update:
I have two brand-new dc's running 4.21.3. The first of these was newly installed and joined a 4.9.5 domain. Then, the old dc's were retired. All seems well with the dc's. Replication, samba_dnsupdate checkout, and they both respond to DNS inquiries. Samba-tool dbcheck also finds no errors.
Installed a new 4.21.3 member server and joined it.
2025 Feb 14
1
DNS Update problems
On Wed, 12 Feb 2025 11:40:19 +0000
Stephen Brandli <steve at brandli.com> wrote:
> Roland, thanks for the reply.
>
> >I think I can explain that, does /etc/hosts contain a line similar to
> >this:
> >x.x.x.x member.samdom.example.com member
>
> Yes. /etc/hosts:
>
> 127.0.0.1 localhost
> 10.65.187.15 tower.domain.brandli.com tower
> ::1 localhost
2025 Feb 10
1
Problems after DC upgrade
I appreciate your help! I'm using, and have used, the internal dns.
Okay, I changed resolv.conf per the below. It is now:
nameserver 10.65.187.8
options edns0 trust-ad
search domain.brandli.com
where the IP address is that of this server, and domain.brandli.com is my ads domain. Now, I can ping other hosts on the domain with short names, but not on any other domain (as you would expect
2025 Feb 10
1
Problems after DC upgrade
On Mon, 10 Feb 2025 14:56:02 +0000
Stephen Brandli <steve at brandli.com> wrote:
> It was systemd-resolved. I disabled that. Now samba is binding to
> the port.
>
> But I'm still getting the dnsupdate failure.
>
> And, I can't ping anything. I get the "unknown host or service"
> error. So names are not getting resolved on the machine. I have to
2025 Feb 07
1
Upgrading Samba AD without upgrading any DC
On Fri, 7 Feb 2025 18:35:29 +0000
Stephen Brandli <steve at brandli.com> wrote:
> Roland,
>
> Thank you for your answers.
>
> To be clear, everything will be Bookworm when I'm done.
>
> My question about upgrading a new DC rather than upgrading old ones
> is the "Upgrade a DC and join it to the domain again" process here:
>
2025 Feb 17
0
Agent Forwarding and (Crypto-Tunnel-Interrupting) Proxies / Jump Hosts
Hello, today our remote access to a platform got switched from direct
SSH over to an "audit capable" proxy (read: supposedly decrypts and
re-encrypts the data passing through), which makes it necessary that we
always forward the agent so that the proxy -> target SSH connection can
get authenticated as well. I noticed two side effects and would like to
ask whether there are
2025 Feb 17
1
Weird usershares attempted use
Okay, I added that and the errors stopped. I was hoping that this was a symptom of my bigger problems, but it wasn't.
Steve
-----Original Message-----
From: samba <samba-bounces at lists.samba.org> On Behalf Of Rowland Penny via samba
Sent: Monday, February 17, 2025 1:08 AM
To: samba at lists.samba.org
Cc: Rowland Penny <rpenny at samba.org>
Subject: Re: [Samba] Weird
2025 Feb 17
1
Output from 'make distcheck-light' and documentation question
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20250217/3315079a/attachment.htm>
2025 Feb 07
1
Upgrading Samba AD without upgrading any DC
Roland,
Thank you for your answers.
To be clear, everything will be Bookworm when I'm done.
My question about upgrading a new DC rather than upgrading old ones is the "Upgrade a DC and join it to the domain again" process here: https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC, right? You said it "raises the RID pools." I don't know what that means. But,
2025 Feb 17
1
Weird usershares attempted use
On Mon, 17 Feb 2025 03:14:46 +0000
Stephen Brandli via samba <samba at lists.samba.org> wrote:
> Another issue I don't understand:
>
> On two different samba servers, smbd logs errors like this:
>
> Feb 16 18:36:29 roberts smbd[136]: process_usershare_file: stat of
> /var/lib/samba/usershares/business failed. Permission denied
>
> Neither machine have