Displaying 3 results from an estimated 3 matches for "nss_status_notfound".
2001 Nov 27
2
winbind trouble, maybe PDC too.
A quick preamble. SAMBA 2.2.2, Redhat 6.2, Mandrake 8.1 Windows NT4.0sp6a
PDC
Here is an excerpt from my winbind log.
Sending a packet of len 50 to (192.168.1.255) on port 137
Received a packet of len 62 from (192.168.1.20) port 137
nmb packet from 192.168.1.20(137) header: id=5433 opcode=Query(0)
response=Yes
header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
header:
2011 Feb 05
3
wbinfo ok, but getent nothing
...sswd: files winbind
#passwd: compat
#passwd_compat: winbind
shells: files
services: files
protocols: files
rpc: files
getend passwd returns:
Code:
# getent passwd
[22522]: endpwent
[22522]: endpwent returns NSS_STATUS_SUCCESS (1)
... list of local users
[22522]: getpwent
[22522]: getpwent returns NSS_STATUS_NOTFOUND (0)
[22522]: setpwent
[22522]: setpwent returns NSS_STATUS_SUCCESS (1)
That is shows the debug information leads me to believe that
nss_winbind is properly called.
Code:
# net ads info
LDAP server: 192.168.0.3
LDAP server name: ad.domain.com
Realm: MEL.DOMAIN.COM
Bind Path: dc=MEL,dc=DOMAIN,dc=C...
2004 Oct 07
2
Samba with winbindd AD Group access limit problem
I'm running Samba 3.0.2 on Solaris using winbindd to allow me to security
tailor access to subdirectories on a Samba share. We assign the
subdirectories within a Samba share to an Active Directory group name. This
generally works fine but I am having user access issues from the Win2K / Win
XP workstations that have mapped the share. The problem seems to be related
to the number of groups /