similar to: dovecot weird bug

I use Squirrelmail to filter messages, and it's doing this: raw log in: A009 UID SEARCH CHARSET ISO-8859-1 ALL Header X-Spam-Level {4} **** A010 LIST "" "spam" raw log out: * SEARCH A009 OK Search completed. * BAD Error in IMAP command : Unknown command. * LIST (\NoInferiors \Marked) "/" "spam" A010 OK List completed. it goes on like that in the

> Dear admins > > I have a similar problem. > When I use smbldap-passwd from command line, the > sambaPwdMustChange field are setted correctly. But when I try > from the Windows workstation, appears a negative value! > Please see it: > > # pdbedit -Lv someuser > (......) > Logon time: 0 > Logoff time: Tue, 19 Jan 2038 00:14:07 BRT >

Dear admins I have a similar problem. When I use smbldap-passwd from command line, the sambaPwdMustChange field are setted correctly. But when I try from the Windows workstation, appears a negative value! Please see it: # pdbedit -Lv someuser (......) Logon time: 0 Logoff time: Tue, 19 Jan 2038 00:14:07 BRT Kickoff time: 0 Password last set: Fri, 23 Dec 2005

Hi. It looks like the gpg signatures of the RC2 and RC3 tarballs are bogus... I've tested the .bz2 and .tar.gz files downloaded from the us1 and us4 mirrors. To confirm that it's not a local problem, I've tested the signature of the Samba_CA.crt file (http://us4.samba.org/samba/ftp/) and it's ok. Can someone else please confirm it? Thanks. - Ademar $ gpg --verify

Hello! I have new xen-3.3.0 installed and working on latest Ubuntu Hardy, with Linux 2.6.18-xen from xen.org. When I run "xm new" I got this error: root@hyper02:~# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 512 1 r----- 1869.9 vsrv65 4 1024 1

This issue right here told me exactly what I needed to understand this authentication process:https://pagure.io/SSSD/sssd/issue/3228 - The client talks to the DC to try and get a cifs ticket for my samba server's princpal name;- In case the client can't get the ticket for any reason, it falls back to NTLM <- windows client decision, nothing can be done about it by Samba/SSSD; Once I

There are roughly 20 DC's, spread across multiple different physical locations. It is indeed a replication issue. All of them are windows and we can get authenticated by any of them, randomly. Don't ask me why... they're managed by the "windows' guys"... I've already tried all sorts of possible combinations for the various NTLM-related parameters and it always fail

How is your sssd settup (sssd.conf) configured? When someone connects via samba, the underlying linux/unix file system routines need to have some what of understanding the windows users and groups.   This isn't for authentication  but is instead to make sure that the file permissions can be managed and enforced. My experience - at least when I had classic domain Samba controllers-  was

On Mon, 23 Jan 2017 18:59:47 -0200 "Carlos A. P. Cunha via samba" <samba at lists.samba.org> wrote: > Hello! > > Comando is: > > samba-tool drs showrepl > > Debug 5 out of one of DC with problems ... > > array: struct drsuapi_DsReplicaNeighbour > naming_context_dn : * >

I'm working across the statistical literature to find methods for calculating prediction intervals for GLM, BRT (boosted regression tree) models and MARS (multivariate adaptive regression spline) models, but unfortunately my statistical background is too weak to understand most of the stuff I read. I would by satisfied by knowing how to code this in R (and accept the methods as black

Hello !! Yes, I noticed this (and it called me too), but as it has about 10 Dc and with some it is talking the data in it are integral, but for some DCs is generating me this error ..... UPDATE: I updated the DC that has this error for several to version 4.5.4, but problem still persists .... Em 23-01-2017 19:30, Rowland Penny escreveu: > On Mon, 23 Jan 2017 18:59:47 -0200 >

Hi, When i put the command pdbedit plus any user name show the message user not found. Only user root is exibited. Why the others not show? the service smbd winb nmbd slapd is running without problem. Example *root at AbramisSRV smbldap-tools]# pdbedit -Lv teste* Username not found! *[root at AbramisSRV smbldap-tools]# pdbedit -Lv root* Unix username: root NT username: root

Hi, all! I have the following environment here: - A Windows 2000 domain, with one server running Windows 2003 Server - A kerberos realm, using MIT Kerberos - A samba server, with security=ads The Windows 2003 server have a trust relationship with the MIT kerberos realm. Users logs on that kerberos realm on their Windows workstations, and are supposed to have access to the shares at samba

I must be missing something- Are these Windows clients?  Or are these Linux clients authenticating against Samba ? if they were linux clients then yes I could see sssd or other authentication components besides winbind coming into play. And in that case yes you would have sssd work with winbind to enable caching of credentials. Is the event log entry below from the server ?   Is it from

Hi list, I have a Samba-3.0.25a PDC running on FreeBSD 6.2-STABLE using OpenLDAP 2.3.34 (nss_ldap-1.255) as backend. Everything work's great, the only problem that I fighting is with an M$ ISA Server 2000, that do ntlm authentications on my domain. At some times (each 4 hours) the ISA Server lost the connection with the domain and does not authenticate users until the connection be

The domain controler is Windows. The file Server is Linux/Samba. The clients are Windows. I've tested the access on a dozen different windows machines. Three of them used NTLM and failed. All the others used kerberos and succeeded. They're all in the same network, same domain. Maybe it's the windows version? But they're all Window 8 or 10, not a great deal of a difference between

On Tue, 5 Sep 2017 11:17:56 -0300 (BRT) Dante Colo via samba <samba at lists.samba.org> wrote: > Hello > > Is there anyway to restrict a user to logon on domain or connect to a > Samba AD server only from some specific client machines ? > > Regards > Dante > > Read in 'man smb.conf' about 'hosts deny' and 'hosts allow' Rowland

Single DC? If a single DC then there should not be any replication issues - that would only be between domain controllers and the event logs would indicate that.   I have 2 Windows DC's with a mix of Samba member servers. As far as I know, the domain member does not need client NTLM auth to be enabled to talk to the DC but I am not 100% sure.  You may want to try reenabling it and

Whenever a client uses kerberos as authentication, it succeeds. Whenever a client uses NTLM as authentication, it fails (logs bellow) since SSSD can't support NTLM. Thus my question: what can I do to prevent NTLM from being used?? [2018/10/09 17:49:29.507046,  2] ../source3/auth/auth.c:332(auth_check_ntlm_password)  check_ntlm_password:  Authentication for user [MYUSER] -> [MYUSER] FAILED

Dear R-friends, How do you test the goodness of prediction of a model, when you predict on a set of data DIFFERENT from the training set? I explain myself: you train your model M (e.g. glm,gam,regression tree, brt) on a set of data A with a response variable Y. You then predict the value of that same response variable Y on a different set of data B (e.g. predict.glm, predict.gam and so on).