similar to: Using smbpasswd users as AD Member

On 14/05/2023 20:32, Kees van Vloten via samba wrote: > The uid + gid are the unique identifier of a user in Linux, the name is > only relevant for the translation of number (uid) to name. > > I.e. a local-user == domain-user when uid + gid are identical. > > My nsswitch.conf prefers local-users over domain-users: > > passwd:???????? files systemd winbind >

On 14-05-2023 21:39, Rowland Penny via samba wrote: > > > On 14/05/2023 20:32, Kees van Vloten via samba wrote: > >> The uid + gid are the unique identifier of a user in Linux, the name >> is only relevant for the translation of number (uid) to name. >> >> I.e. a local-user == domain-user when uid + gid are identical. >> >> My nsswitch.conf prefers

On 14/05/2023 20:47, Kees van Vloten via samba wrote: > > On 14-05-2023 21:39, Rowland Penny via samba wrote: >> >> >> On 14/05/2023 20:32, Kees van Vloten via samba wrote: >> >>> The uid + gid are the unique identifier of a user in Linux, the name >>> is only relevant for the translation of number (uid) to name. >>> >>> I.e. a

On 14-05-2023 21:58, Rowland Penny via samba wrote: > > > On 14/05/2023 20:47, Kees van Vloten via samba wrote: >> >> On 14-05-2023 21:39, Rowland Penny via samba wrote: >>> >>> >>> On 14/05/2023 20:32, Kees van Vloten via samba wrote: >>> >>>> The uid + gid are the unique identifier of a user in Linux, the >>>> name

Hi list, I have a (naive?) question about samba local users. My system: CentOS 6.6 w/Samba 3.6, connected to an AD Domain through Winbind. When creating a local user, I always first create a Unix user with passwd and then I use smbpasswd -a <unixuser> to establish the mapping between the tdbsam database and the local /etc/passwd file. I wonder if, using the tdbsam in conjunction with

On 14/05/2023 21:05, Kees van Vloten via samba wrote: > > On 14-05-2023 21:58, Rowland Penny via samba wrote: >> >> >> On 14/05/2023 20:47, Kees van Vloten via samba wrote: >>> >>> On 14-05-2023 21:39, Rowland Penny via samba wrote: >>>> >>>> >>>> On 14/05/2023 20:32, Kees van Vloten via samba wrote: >>>>

On 14-05-2023 21:21, Rowland Penny via samba wrote: > > > On 14/05/2023 17:29, Michael Tokarev via samba wrote: >> Hi! >> >> We faced another issue with not having samba (ad-dc) users in local >> /etc/password: >> this way, we can't easily have services run as users this way, since >> winbindd is >> started later than most services are (and

On 14/05/2023 17:29, Michael Tokarev via samba wrote: > Hi! > > We faced another issue with not having samba (ad-dc) users in local > /etc/password: > this way, we can't easily have services run as users this way, since > winbindd is > started later than most services are (and it requires working network). > Also, > user-defined cron @reboot jobs aren't being

Hi there, I have a Samba installation acting as a Domain Member with a disk share (the partiton is mounted with acl and user_xattr options). I am not using winbind, because I want the domain users to be mapped to Unix users. Everything works right, excepting the users in the Windows Explorer security tab. I will try to explain the situation with an example. I have username map, that maps

This is part of a larger post that was maybe too complicated for me to get the right answer, so I'm breaking it down and will do it bit by bit. Server is Samba-3 PDC, clients are NT4 & XP. I can join the domain using root credentials (so the add machine script works), but not when using 'administrator'. unixuser 'administrator' has primary unixgroup 'ntadmins'.

OK, I had this working a few days ago, but have evidently changed something that I cannot locate. Someone hit me with their 2x4. Samba 3.0.22, Fedora Core 4, ldapsam (OpenLDAP 2.3.24). smbd will not start, with the "ERROR: failed to setup guest info" error (I have "guest account = guest", which is a valid user with correct info in LDAP): ldap_connect_system: Binding to ldap

On 14/05/2023 21:15, Rowland Penny via samba wrote: > > > On 14/05/2023 21:05, Kees van Vloten via samba wrote: >> >> On 14-05-2023 21:58, Rowland Penny via samba wrote: >>> >>> >>> On 14/05/2023 20:47, Kees van Vloten via samba wrote: >>>> >>>> On 14-05-2023 21:39, Rowland Penny via samba wrote: >>>>>

I've written a fairly elaborate package (called "eoa") that relies on functions from several other packages. I've built the package into a zip file on Windows using Hadley's devtools::build(binary = T) and have sent the zip to a couple dozen people for testing. My package installs fine, but some people are having trouble loading it. After library(eoa), they get something

I've written a fairly elaborate package (called "eoa") that relies on functions from several other packages. I've built the package into a zip file on Windows using Hadley's devtools::build(binary = T) and have sent the zip to a couple dozen people for testing. My package installs fine, but some people are having trouble loading it. After library(eoa), they get something

Hi! We faced another issue with not having samba (ad-dc) users in local /etc/password: this way, we can't easily have services run as users this way, since winbindd is started later than most services are (and it requires working network). Also, user-defined cron @reboot jobs aren't being run, for the same reason: cron is stared before winbindd on most systems. This is quite difficult to

I have been having problems with username maps and security=ads. I now have a solution (or at least a work around) that is working for me. I sort of stumbled across it, as I don't recall reading any samba docs that mentions the need to have the realm name in the smbuser file. Samba server is RHEL3 with samba-3.0.20 compiled from source authenticating against a windows ADS. Here is the

Yesterday evening I upgraded my FreeBSD 5.5-RELEASE Server from Samba 3.0.22 to 3.0.23. This gave me a LOT of work today... :-( This is what I found so far: My Samba-Server is member of a large ADS-Domain. After the upgrade, file based Usermapping didn't work anymore... better: it worked TWICE. (I once opened a PR for that a few years ago :-). So, with LogLevel 3:

Hello all! We are attempting to get Samba-3.0.10 working on a new Solaris 8 machine in preparation for upgrading an existing 2.2.8 installation (both use the SMCsamba packages from SunFreeware.com). We copied over the smb.conf file and the usermap from the Samba-2 installation, and seeing some weird symptoms when Windows users try to connect to the new machine. We ran "net join" to

Hi all, I have seen many posts on the Shorewalllists dealing with H323. Although lots of them indicated that this is difficult process with kernelrecompilation etc. I just tried what seemed to be logical for me. Surprisingly it worked. Configuration: WS1 ----- FW ------ Internet ------- WS2/Shorewall WS1, FW and WS2 run Redhat9 with its standardkernel 2.4.20. FW and WS2 run Shorewall

I just created a new smbpasswd file, all users with unset passwords. Problem is, users can't set their passwords, only I can as root. Password is not set / blank, but they still get: >test> smbpasswd >Old SMB password: <enter> >New SMB password: Samba >Retype new SMB password: Samba >machine 127.0.0.1 rejected the password change: Error was : RAP86: The >specified