similar to: strange permission problem with sharing over NFS

Hi Everyone, This is a follow-up question on Samba. After doing rpm to reinstall the dependencies on libcups.so.2 and libssl.so.2. Samba went on fine. My question is regarding Client machines Win98 could not log on to the samba server. This gave me an error message --> The share name was not found. Be sure you typed it correctly. As far as I can remember I did the following on my samba box.

?Bump. Can someone from dovecot dev team please respond something to my problem ? I've provided all the possible information, and if not please tell me. Or do you only provide support for your own FTS solution bundled with the paid version of dovecot-pro ? If so, you should clearly state it in the wiki. Thanks Le 19/04/2018 ? 10:30, kadafax at gmail.com a ?crit?: > I think I'm

Le 21/05/2018 ? 11:46, Aki Tuomi a ?crit?: > That message is coming from the temporary raw user, not from the actual > user. > > How did you verify that the FTS indexes are not created or updated > automatically? I send an email containing a specific strings ('thahB8ea' in that case) and search agains it: # doveadm search -u username mailbox INBOX body thahB8ea --> No

can you try turning on pluign { fts_enforced = yes } and repeat your test? Aki On 21.05.2018 13:31, kadafax at gmail.com wrote: > Le 21/05/2018 ? 11:46, Aki Tuomi a ?crit?: >> That message is coming from the temporary raw user, not from the actual >> user. >> >> How did you verify that the FTS indexes are not created or updated >> automatically? > I send an

I think I'm progressing: if I create a brand new user, send her an email, it will not be indexed right away. I need to doveadm rescan / index the Inbox before. At the end of this email, a dovecot's debug log snipset (grep'ed on this user). In it I can read: "Debug: fts: Indexes disabled for namespace '' Can this be a problem ? Thanks doveconf -n output: # 2.2.34

That message is coming from the temporary raw user, not from the actual user. How did you verify that the FTS indexes are not created or updated automatically? Aki On 04.05.2018 12:47, kadafax at gmail.com wrote: > ?Bump. Can someone from dovecot dev team please respond something to my > problem ? I've provided all the possible information, and if not please > tell me. > Or do

Help! I have been using dovecot for some years with great success. A little while ago, I changed my mail server from Fedora to CentOS linux. I reinstalled dovecot, and *almost* everything seems to be working, but one thing. There's *one* user I can't get it to work on without a workaround. The user is "newuser" and the uid is 1111 (actual name and number changed to protect

I have two instances of an openldap-2.4.39 server running with syncrepl in a master-master replication setup. These are Centos 7.1 test servers which have been running for over 2 months now with no problems. Partly the good behavior of the LDAP servers is due to very little exercise. Yesterday I decided to try and see exactly how well replication was working. With server-2 up and running I

I am running Samba version 3.0.9-1.3E.2 on a server that is joined to a windows server 2003 domain using ADS security. The samba server hosts a share called 'files'. I am having problems mounting this share using a new account I set up. getent passwd shows the information for the new account as does wbinfo -u. Mounting the share with the new users account using the net use command

After upgrading to 3.4.0, I can no longer add new users. Any users that were added beforehand work fine. Any users that I attempt to create cannot login (error: NT_STATUS_LOGON_FAILURE). I was able to get one new user account to work (see below), but I cannot add any new users. The server is Ubuntu 9.10 running Samba 3.4.0. I am using: security = user pam password change = yes Updating

Dear all, on CentOs7 based linux w. different versions of Samba (4.6.x from CentOS repos, but also Sernet-Samba-4.7.4 and also compiled from source), "wbinfo -i user at domain.tld" returns different results before the first successful authentication of the user. Server joined as member to Active Directory, idmapping via tdb2. On first attempt, the result returns

Thank you very much, Rowland! Very helpful. But do you say that the change in the output of „wbinfo -i“ is expected after the user has logged in? Should the use of „domain.realm“ vs „NTDOMAIN“ not be consistent, no matter if the user has logged in or not? Many regards, Heiner Von meinem iPhone gesendet > Am 11.03.2018 um 16:09 schrieb Rowland Penny <rpenny at samba.org>: > >

def dispfriends @myfriend=[] @myfriendlogin = [] i=0 @currentgroup = Group.find_by_id(params[:groupid]) puts @currentgroup.id @currentfriends= GroupFriend.find_all_by_user_id_and_group_id(current_user.id, @currentgroup.id) for n in @currentfriends @myfriend=n.friend_id @myusers = User.find_by_id(@myfriend) @myfriendlogin[i]=@myusers.login puts @myfriendlogin[i] i=i+1 respond_to do

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here is a description of what I am trying to do (with Samba 3.0.2a & openldap 2.1.27): I have all my users populated into the LDAP with all the applicable attributes; Users can map drives to a server using LDAP as the authentication backend without issue. Where I am running into problems is bringing up a PDC using Samba w/LDAP. * I added

On 21/10/15 17:37, Ole Traupe wrote: > I think I finally managed to understand the [homes] part of the man > pages, and what my problem is: > https://www.samba.org/samba/docs/man/manpages/smb.conf.5.html > > The misunderstanding comes from my practice I learned on Windows to > just share the "\\server\home" directory and to create per-user > sub-folders

Well, I do. That is not the problem. The problem was that I wasn't used to have user homes to be shares themselves. And when I share \\server\home and want to have the folder \\server\home\newuser to be auto-created, but I actually connect to the share [home] (\\server\home), this section in the smb.conf is always found and so the special [homes] section is never executed (cloned).

Hello, I have a samba server (old - running FC6, samba 3.0.24-11.fc6) that authenticates against AD. This is all configured and has been working fine until this week. A new user has been added to AD, but cannot access the samba drives. All other users can still access samba as normal. net ads testjoin reports OK. wbinfo -a newuser%pass and wbinfo -K newuser%pass both succeed. wbinfo -r

Rowland, what are [homes] shares on a Unix machine? What you describe seems to be mostly correct. However, in my eyes there is no such thing as a collection of [homes] shares. This section gets invoked whenever a non-existing share is requested. Thats what the man pages say (with many complicated words) and what I just confirmed here. It even works, if you put \\servername\%username% as home

Hi! Running OpenSolaris snv_134 with Samba 3.0.37. Samba is successfully joined to AD domain. AD user "user1" is member in 17 AD groups including "group1", but he cannot access Samba share which have read permissions for "group1". If user account is modified and "group1" becomes users primary group, then he can access shares. If user is member of only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I migrated a samba3 with openLDAP to Samba 4 (sernet package 4.13). I can see all migrated users on all DCs and fileservers with "wbinfo -u" and "getent passwd" and all informations for a single user with "getent passwd <username>" and "wbinfo -i <username>". Now, after migration, if I