similar to: problem listing directories with AD permissions

Displaying 20 results from an estimated 1000 matches similar to: "problem listing directories with AD permissions"

2011 Jan 20
2
idmap troubles with any version 3.30 or later
Hello list. The issue I have is that with the changes made to the idmap functionality of winbind, as regards the enumeration of rfc2307 users and groups using getent passwd and getent group, only those AD users that are not in the domains included in the "idmap config (domain)" statements (the ones in trusted domains that get their ID mappings auto-assigned by the TDB backend with
2006 Sep 06
0
authenticating using winbindd against NT4 domain fails
Since version 3.0.23b, I have been having trouble getting Windows & OSX users to access an NT domain member server running FreeBSD 5.4. It is now at 3.0.23c (installed this morning the 5th). root@aries:/usr/local/lib# net rpc user Password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_NO_LOGON_SERVERS root@aries:/usr/local/lib# net rpc user Password: Could not connect
2006 Sep 06
3
FW: authenticating using winbindd against NT4 domain fail s (URGENT)
Hi folks, Can anyone shed light on this issue? I haven't heard from you guys. Is there anything else I could do to expedite resolution of this issue? I've read the WHATSNEW.txt and reviewed the release notes. I am not sure if I've fully grasped what needs to be done. Can someone point me in the right direction? ~Doug -----Original Message----- From: Doug Sampson
2006 Aug 23
2
3.0.23b domain member not accessible
I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)
2005 Sep 16
4
getent and wbinfo not returning expected results?
Hello, For some time now have been trying to connect a Samba-3.0.14a-0.4 server running on SuSE Ent 9 linux server to our Exchange 2003 (running on Server 2003 Std w/ SP1) server which is also the AD server for our domain. I can connect to the shares using the AD as the authentication source, so the basic functionality is there but some command output does not show in the way i expect
2007 Jun 15
0
Unable to find a suitable server
Hello List I'm experienceing problems with Samba 3.0.25,1 running in a FreeBSD box. I've succesfully joined a domain, and I've configured mail with auth on W2k3 server thorugh PAM. YET If I issue mail# /usr/local/www > net rpc testjoin Unable to find a suitable server Join to domain 'DMSWARE' is not valid BUT mail# /etc > net rpc testjoin -S orion Join to
2007 Jun 18
0
problem with Samba Wins Server
Hello List I'm experienceing problems with Samba 3.0.25,1 running in a FreeBSD box. I've succesfully joined a domain, and I've configured mail with auth on W2k3 server thorugh PAM. But I have problems with wins name resolution . If I issue mail# /usr/local/www > net rpc testjoin Unable to find a suitable server Join to domain 'DMSWARE' is not valid BUT mail# /etc
2007 Jun 15
2
Problems accessing Shares
Hello List I I'm experiencing SERIOUS problems accessing Shares. I'm using Samba 3.0.25 on a FreeBSD Box I'm using samba for sharing and user authentication Everything seemed working perfectly but when I tried to share some more directories, problems poped up I can read shares ONLY if they have Read attribute for Other. and I can manipulate files ONLY if they have Write
2007 Jun 13
2
cached logons
Hi. I can't do cached logons in our new samba server. I had a dead crashed W2k server quickly replaced by samba-3. That meant create a new domain, restore backups and add all the PCs to the domain. It was impossible to ressurrect the old MS server. Anyway I'm facing a problem about cached logons. There is no way to make it work. I've been reading all the entries in the mailing list
2007 Feb 08
5
FreeBSD and Winbind
I'm hoping this is an easy question, but the way my day has gone I seriously doubt it is going to be. Today, I installed Samba 3.0.24 with winbind support on my FreeBSD 6.2 server. I am able to join my domain and get information concerning groups and passwords from the domain controller (Windows 2003) without any problem. Where I have run into a problem is using getent to get a copy of the
2017 Oct 24
2
FreeBSD Member server error WBC_ERR_DOMAIN_NOT_FOUND
yes, i have /var/db/samba4 # ls -l /usr/local/lib/ | grep nss_win -rwxr-xr-x 1 root wheel 43162 Oct 21 20:58 nss_winbind.so.1 Alexander -- Sent from: http://samba.2283325.n4.nabble.com/Samba-General-f2403709.html
2017 Oct 24
2
FreeBSD Member server error WBC_ERR_DOMAIN_NOT_FOUND
it is not only my problem. I have installed new FReebsd and build port Samba4.6.8 by hand, but library libnss_winbind.so is absent. Well and where I can find it? I have found nss_winbind.so.2 but ldconfig not see it. -- Sent from: http://samba.2283325.n4.nabble.com/Samba-General-f2403709.html
2009 Apr 06
3
nss_wins: create_builtin_users: Failed to create Users
Hi All, I am getting the following error in /var/log/messages when an XP Pro client enters the network: nss_wins[8369]: [2009/04/06 15:17:23, 0] auth/auth_util.c:create_builtin_users(810) Apr 6 15:17:23 rn1 nss_wins[8369]: create_builtin_users: Failed to create Users I have been told in the past to add "idmap uid" and "idmap gid" to my smb.conf and I have (no symptom
2006 Jul 24
0
nss_winbind does not recognize group membership
Hello, There is FreeBSD-6.1 box with gcc 3.4.4 compiler (the default). The box is a member of an ADS domain. Everything was working perfectly with samba-3.0.22. After upgrading it to samba-3.0.23_1 from FreeBSD ports collection, the following problem appeared. The system does not seem to recognize that a user is a member of some domain group, and does not grant him appropriate permissions. For
2005 Jan 26
1
dovecot Maildir issue
I'm working on switching a domain from a Cyrus+postfix+procmail to Dovecot+postfix+procmail (using Maildir). It works great, except one small problem. I cannot figure out what the permissions for my Maildir directories should be. Can anyone point me to a doc or just a few pointers on what the permissions of the Maildirs should be? The only way I seem to be able to make this config work is to
2002 Feb 15
3
Samba Team? - "ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_winbind.so.1: symbol socket: referenced symbol not foun d"
I've recompiled samba 2.2.3a and still any time I do a ls -l in a directory where there are files from a PC I get the error : ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_winbind.so.1: symbol socket: referenced symbol not found If I shut off winbind or take winbind out for my /etc/nsswitch.conf file, I can get a directory listing and it lists the users ID that winbind assigned to
2002 Jul 15
1
WINS on Solaris 7/8 - broken?
I had no problem configuring WINS lookups, via nsswitch and libnss_wins.so, under Linux. The problem I am having is on Solaris. I am working with the 2.2.5 release of Samba. Everything in the nsswitch subdirectory compiles cleanly. wbinfo, which uses winbindd, resolves WINS entries no problem. (When I am running winbindd, that is.) Solaris appears to use /usr/lib/nss_wins.so.1 rather than
2013 May 08
1
Is nss_winbind required?
Hi all, Is it a necessity to use the winbind nss module? I have run a few tests and having it enabled creates a massive bottleneck. It's not nss_winbind itself that is the bottleneck but something in the background (I'm guessing uid/rid->username code). If I disable winbind in nsswitch.conf what impact will it have? Will the system continue to work? eg: #nss_winbind enabled on
2002 Feb 15
1
"ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_ winbind.so.1: symbol socket: referenced symbol not found" - Samba Team?
Hey, I'm getting this error when ever I've written a file from my Win2k Pro machine to my samba share. Using Samba 2.2.3. Built on Solaris 8. Using winbindd. I created the sym links as suggested under /lib (really /usr/lib): nss_winbind.so.1 -> libnss_winbind.so nss_winbind.so.2 -> libnss_winbind.so Are there some other sim links I need somewhere or is this error something
2002 Feb 15
2
Samba Team? - "ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_winbind.so.1: symbol socket: referenced symbol not fou n d"
You can test if winbind is able to resolve user IDs internally with "wbinfo -u". This uses the samba tool "wbinfo" to connect directly to the running winbind daemon and list all the Windows domain users. If that fails, then you have problems with the winbind daemon itself. The authentication between winbind and the PDC can be tested with "wbinfo -t", which is usually