similar to: Samba 3.2 PDC - Creating Zone Identifier files and not able to read/write/delete them.

Hello. Probably only Timo can help-me with this. I have a self-made plugin based on the zlib plugin that i use to cryptograph the messages at inbox. As a side-effect of the cryptography, my plugin changes the size of the message, but until 2.0.19 this works well with dovecot index and the W/S flags. But now, i'm going to upgrade to 2.1.17 and now i have these messages on log at my test

Hi How do i set up so that everyone can dial, for example *21* to forward all calls to a cellphone or another extension and how do I enable so that cals can be transferd between extentions. I use asterisk 1.6 and have my phones in unistim.conf and my extensions in extensions.conf. Regards /ralf ________________________________________________ Ralf Tr?skman, IT AdLibris AB, Odengatan 106, 113

Hi, Tim Not even one ocurrence of "wins support" on my smb.conf -----Mensagem original----- De: Tim Kelley [mailto:tpk@r00tserverz.net] Enviada em: s?bado, 18 de outubro de 2003 11:09 Para: Reinaldo Brand?o Gomes Cc: samba@samba.org Assunto: Re: [Samba] Nmbd in a infinite loop, doing nothing and sucking 99%CPU (really) On Saturday 18 October 2003 9:03 am, Reinaldo Brand?o Gomes

Forgive me if I have misundertood your words, but what I want is to prevent Samba from accepting NTLM(v1, v2, SSP, or whatever) and forwarding it, since SSSD does not support it. I am not trying to get SSSD to support any kind of NTLM. So, this would be a Samba issue, not SSSD's. Isn't that correct? Putting it in another words: what can I do (preferrably on the Samba server) to prevent

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

Hi i've read this post http://lists.digium.com/pipermail/asterisk-dev/2007-May/027666.html I just want to know if there are some upgrades... on 1.4 or 1.2. I'd like to store two records in the CDR instead of one, when a call is transferd. Is it possibile now? Thanks to all -- /*************/ nik600 https://sourceforge.net/projects/ccmanager

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

Guys. This idea has been banging my headfor days now and I feel the need to share with you. Imagine this scenario: all calls come in thru a receptionist, asterisk records all incoming calls, the receptionist's work is to transfer the calls to internal people but some of them are bosses and you know how bosses are, they don't want their calls to be recorded, so, I have been trying to

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

How can I make sure that NTLM(SSP) will never be used?? I’ve set up Samba with SSSD and everything Works fine... except for a few Windows machines which every now and then happen to send NTLM authentication flags to the Samba server, which happily forwards them. And then the authentication fails because SSSD doesn’t support NTLM. I’ve tried all sorts of parameters combination on smb.conf

Hello, My problem is that since last Sunday, 6 ultra 10, running solaris 7 stopped having samba working. Those machine are on a client site, a big mining idustry. SO, all the reports are generated over this data base, that needs to be available. The nmbd process looks like being in a loop, doing nothing and consuming 99%CPU. I have tried to create a log, using the nmbd -l /var/log/samba.log

Hi, People WE are having this problem with nmbd & smbd. The Process, once started goes by 99%CPU time and does nothing. For example, if I started nmbd with the option -l /usr/local/samba/log.nmbd, no log is created. The smb.conf was not modified over the last 8 years. The OS is solaris 7, and we have mainly windows clients. But doing one test with smbclient from another sun running

Hello. I need to know how I can get the final message file name inside a plugin like the zlib 2.0 plugin. I saw another threads about zlib plugin, but don't see no one asking about this. My interest is to use the message's file name in a specific function that will add some lines on it and, after that, calculate a md5 hash of the modified file. As the size flags will not correspond to

I had to update several gems for Bundler to accept it but now I''m stuck: bundle update rails devise knockoutjs-rails sass-rails coffee-rails devise-encryptable oojs Fetching gem metadata from https://rubygems.org/....... Fetching gem metadata from https://rubygems.org/.. Resolving dependencies... Bundler could not find compatible versions for gem "railties": In Gemfile:

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

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

How would samba forward any requests on to any other service ?       You can have sssd setup on a server if you also need to support things like ssh, sftp, and nfs but that is separate from samba's "Windows" services. Or do you mean it forwards NTLM requests to a different server ? Disabling NTLM altogether would be a useful feature if you are trying to minimize the attack

Heres is the output of truss /usr/local/samba/bin/nmbd execve("/usr/local/samba/bin/nmbd", 0xEFFFFCA0, 0xEFFFFCAC) argc = 2 open("/dev/zero", O_RDONLY) = 3 mmap(0x00000000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xEF7C0000 open("/usr/lib/libsocket.so.1", O_RDONLY) = 4 fstat(4, 0xEFFFF83C) = 0