]
#62 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f]
#63 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13]
Regards,
Ruud Baart
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Configuration: Samba 2.2.8a with openLDAP 2.1.30 on a SeSE 8.2. server
When adding a user using a ldif file we give the user a given name, say Ruud Baart.
The cn and uid are the same, say 21cs12345 (a studentnumber).
After adding the user to LDAP the displayname is as expected: Ruud Baart
Made mistake in my question, sorry. Question should be:
Configuration: Samba 2.2.8a with openLDAP 2.1.30 on a SeSE 8.2. server
When adding a user using a ldif file we give the user a displayName, say Ruud
Baart. The cn and uid are the same, say 21cs12345 (a studentnumber). After
adding
We use samba 2.2.8a, openldap 2.1.12
When adding a workstation to the PDC normally a machine account is added with a
script (e.g. /usr/local/bin/smbaddmachine). The script runs with the userid root.
That is neccesary because smbpasswd requires root-id for running:
smbpasswd -m -a
Server is PII-350MHz/256 MB RAM, hardware mirrored high speed SCSI disks.
Installed is SuSE 8.2 with Samba 2.2.8a RPM, XFS filesystems and LPRng as
printservices. Server acts as PDC and WINS server.
Clients are W2K SP2 (a few with SP3). There are +/- 100 clients.
We see a server that is 100%
In our opion: use LPRng. We like cups, but we have had several time
consuming problems with cups. We also don't use the old BSD
lpr/lpd services.
We choose the combination LPRng and raw tcpip on port 9100
(jetdirect). This gives bidirectional communication between printer and
server. Very
We upgraded from 2.2.3a to 2.2.4 on a SuSE 7.2 server. We compiled Samba just
default. The new version seems to work ok with the exception of printer administration.
Printer admins are not able to see the properties of the printers (right click on
printer
gives on error). Our workstations are
