Hi Rowland,
Thanks for your quick response.
Yes, it's Samba+sssd+krb5+AD. So many technologies wrapped together, and I
don't know which part can go wrong. We managed to make them work together
with the full domain name format such as yu.yale.edu\zs24. But it didn't
work with short format as YALE\zs24. When I did this in a Windows computer, it
reported "We can't sign you in with this credential because your domain
isn't available." This seems a DNS issue, because it cannot convert
'YALE' to its full name 'yu.yale.edu'. But I don't know
where I should input this name resolution in this Samba server.
Unfortunately, we don't have Redhat support contract and cannot get
technical support from Redhat. Yes, we are very careful to upgrade Samba and its
version may fall behind from the latest one.
Zhongdong
-----Original Message-----
From: samba <samba-bounces at lists.samba.org> On Behalf Of Rowland Penny
via samba
Sent: Monday, May 6, 2024 4:06 PM
To: samba at lists.samba.org
Cc: Rowland Penny <rpenny at samba.org>
Subject: Re: [Samba] Samba domain name in short format
On Mon, 6 May 2024 19:50:18 +0000
"Sun, Zhongdong via samba" <samba at lists.samba.org> wrote:
> Hello everyone,
>
> We have a Samba server that experiences very strange problems. I
> wonder if anyone can provide some advice.
>
> This is a Redhat 8.4 machine with Samba 4.13.3. We setup Samba
> according to Redat document
> https://access.redhat.com/solutions/3802321 .
Sorry but that is behind a redhat wall and I cannot access it, but as it seems
to how to use Samba with sssd, I suppose it uses their 'sss'
idmap backend.
> It works well in most
> cases but has some issues. When user tries to mount a share from
> his/her PC, he/she must use the long format of domain name, such as
> yu.yale.edu\zs24. It works but most users don't like it. Instead, all
> users prefer to use the short format like YALE\zs24, but this doesn't
> work anymore. Here, YALE is a short format of yu.yale.edu. This short
> format works well in Redhat 7.4 with Samba 4.6.2. But we have to
> upgrade Redhat 7.x to 8.x.
>
> I wonder if anyone experienced similar issues or has any direction on
> what's going on here. Any advice will be appreciated.
Samba doesn't produce sssd, so doesn't have access to the code if it
needs fixing. I suggest you contact redhat to get this fixed if you want to
continue to use sssd with Samba.
If, however, you want to use Samba as Samba intended, that is by using winbind
without sssd, I am more than willing to help with this.
I suppose that I should also point out that, from the Samba of point of view,
Samba 4.13.3 is ancient.
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba