Displaying 10 results from an estimated 10 matches similar to: "debug_lookup_classname(ads/rpc): Unknown class"
2004 Mar 12
3
read and write list
Hi,
I can not find information how to configure a share to allow everyone read
access and users of specific NT group write access.
Now my smb.conf looks like:
[global]
log level = 2
syslog = 2
workgroup = AMITY
netbios name = AMITYDEVEL
guest account = nobody
security = server
password server = AMDATA
hosts allow = 10.
local
2006 Nov 08
1
BDC nmblookup and net getlocalsid not working
Hi,
After lots of struggle and rtfm I finally got most things running, except
for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but
plenty more to learn. Here's the setup in summary:
system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master,
wins server, domain master browser, no iptables;
system bdc is the BDC on subnet 192.168.2.0,
2024 Feb 27
2
Samba Kerberos Logs
Hi team,
Is there a way to grab Kerberos specific log entries?
Example:
/Auth: [Kerberos KDC,ENC-TS Pre-authentication] user.../
I have tried using the kerberos class but nothing was logged when I
specified a path.
This is what I have on my smb.conf.
/[global]
??????? log level = 1 kerberos:2@/var/log/samba/kerberos.log
auth_audit:3@/var/log/samba/audit.log
2006 Feb 09
4
idmap backend, LDAP & Windows AD
Dear all,
Since couple of weeks, I'm trying to configure Samba to get UID & GID
from Windows 2003 AD. I read samba documentation & how to, but it still
not working.
Here are the tasks I've perform:
- I installed SFU on my Windows 2003 Server
- I configure /etc/samba/smb.conf:
# Global parameters
[global]
workgroup = TOTO
netbios name = VENUS
encrypt
2024 Feb 28
1
Samba Kerberos Logs
On Tue, 2024-02-27 at 16:46 +1300, June Chong | TechnologyWise via
samba wrote:
> Hi team,
> Is there a way to grab Kerberos specific log entries?
> Example:
> /Auth: [Kerberos KDC,ENC-TS Pre-authentication] user.../
> I have tried using the kerberos class but nothing was logged when I
> specified a path.
> This is what I have on my smb.conf.
> /[global] log level =
2005 May 12
3
Sarbanes-Oxley headaches
Hi there,
With the new scrutinization by auditors on account policies and
auditing, how can Samba be SOX compliant?
Using 3.0.14a-sernet on Suse 9.1 - ldapsam
Specifically, a couple of things seem to be lacking:
1) Logon/Logoff times are not being recorded
The last logon time recorded in my ldap entries are pre-nt4 migration.
2) Do the Audit Policy values in user manager have any effect?
Are
2011 Mar 06
0
Solaris Express server name broadcast
Le 06/03/2011 00:14, "Hung-Sheng Tsao (Lao Tsao ??) Ph. D." a ?crit :
> question to solaris forum
> http://forums.oracle.com/forums/search.jspa?objID=c300&q=Solaris
Since you have been (and you alone) kind enough to try and help me, I
will give you in writing a detailed explanation on how this mess came to
be : however, as I explained, I have only known the Solaris OS, or
2024 Jan 31
0
Samba Logs
Hi team,
Hope that someone can guide me in the right direction.
This is on Samba 4.18.6; Ubuntu 23.10
I have put max log size: 512002 under smb.conf for testing. However,
this doesn't apply to log.samba. The logs for that are all capped at 5
mb before rotation happens.
This is what I have on my smb.conf.
[global]
??????? log level = 1 kerberos:2@/var/log/samba/kerberos.log
2018 Mar 09
2
Run smbd in AD user context
Hi all!
Is it possible to run smbd in an AD user's context?
If not, is it possible to have smbd to tell a third-party function to not
stray outside from logged on user's (AD user) context (home directory)?
I'm programming a VFS module[1] which will be the bridge between Windows
and iRODS[2]. iRODS depends on a configuration file,
.irods/irods_environment.json, which resides in the
2005 Dec 09
1
Ellipse ASR-Model Report Descriptor tree
Hi all
Arnaud,
Some newly purchased Ellipse ASR-model UPS find their way to my office for
a first evaluation test.
It concerns the Ellipse 1500 and Ellipse 1000 models.
As you know we are still working with hidups.
Peripheral recognition, start of NUT, mains short interruptions management,
all that work fine... as expected ;-)
But changes occured on the delayed shutdown procedure after the