similar to: wbinfo -u error

Hi, We recently upgraded some AD member file servers from 4.6.7 to 4.6.11. Since then, "getent group" has been failing to return groups properly after winbind's been running for a couple of days. We have a lot of entries in log.wb-<DOMAIN> like this: [2017/12/15 11:39:47.959368,  1] ../source3/winbindd/winbindd_ads.c:1236(lookup_groupmem)   lsa_lookupsids call failed

I only have limited Samba experience, and expect this is a silly mistake, but have been unable to find a solution I have installed Samba and Winbind on my desktop Linux (Debian) machine (SPARKSTONELX), aiming to unify logins with other windows machines accessing the PDC, again samba/Debian, with tdbsam password backend. All is well, joining the domain, and getting account details using wbinfo -u,

Hi, All! I Have Samba (3.5.6) domain witch have trust relations with ADS (Named TEST) Win2008 (2008 domain mode) On PDC all working very good. I have also Domain Member server in my samba Domain. When i trying type wbinfo -u, or getent passwd on samba PDC (Named BINKLG) I see all, including ADS users. When I trying do it on Domain Member Server I don't see users from ADS Is it possible to

Hi. We add a new virtual machine with vmware server 1.0.4, centos 5.x client, we update the server with yum and receive samba 3.0.25b-1.el5_1.4, we have a PDC running Gentoo with Samba 3.0.24+ldap, all the windows clients and other Linux boxes(.3.0.10 + 3.0.23 + 3.0.24) are working very good and stable. The only problem is this new server, i read about some changes with samba 3.0.25b and

Attempting to get Winbind to authenticate against a Windows 2000 Domain, I am having one odd issue. Running: wbinfo -t returns a successful secret wbinfo -g returns the builtin groups wbinfo -u returns "Error looking up domain users" None of the documentation I've found points to anything where only -g or -u fails--its always both. Anyone have any ideas? Thanks in advance -Matt

dear samba community, we have a big problem on joining a Samba 3.5.6 PDC. Hopefully anyone has an idea/suggestion. When trying to join with a Samba 4.2.10 or 4.3.9 we got the following error on client site: Failed to pull dcerpc auth: NT_STATUS_RPC_PROTOCOL_ERROR. cli_rpc_pipe_open_schannel_with_key: rpc_pipe_bind failed with error NT_STATUS_RPC_PROTOCOL_ERROR libnet_join_ok: failed to open

Hello everyone, Samba stopped authenticating AD users after minor upgrade. Environment: - OS: CentOS 7 - Samba Version: Upgraded from samba-4.10.16-15 to samba-4.10.16-25 Problem: Clients are unable to authenticate with Active Directory credentials, receiving a "password incorrect" error. Verification: sudo net ads testjoin shows a successful join. wbinfo --ping-dc confirms

Hello, I've upgraded a classic NT4 style BDC to samba 4.2.10 (and after that to 4.2.12, but no improvement...) It was running on 4.1.17 and wbinfo -u showed a list of our users, and users of the trusted domain. running on 4.2.12 it lists only our users. on a working server: wbinfo --domain=EXAMPLE -t checking the trust secret for domain EXAMPLE via RPC calls succeeded On 4.2.12:

I recently brought up our fifth Samba domain member server with 3.0.26a-0.9-1787-SUSE-SLES9 against an NT4 domain on a new subnet. The subnet also has an NT4 BDC that is working correctly. Wbinfo and getent both work properly but users can not get to the [homes] service but can get to another share that is on the same system. If I setup a share definition in smb.conf for myself as a home

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

dear samba community, we have a big problem on joining a Samba 3.5.6 PDC. Hopefully anyone has an idea/suggestion. When trying to join with a Samba 4.2.10 or 4.3.9 we got the following error on client site: Failed to pull dcerpc auth: NT_STATUS_RPC_PROTOCOL_ERROR. cli_rpc_pipe_open_schannel_with_key: rpc_pipe_bind failed with error NT_STATUS_RPC_PROTOCOL_ERROR libnet_join_ok: failed to open

Hi, we have a problem with your Samba4 Domain Member as with Shares. when i would connect i got an Error. In Samba Logs it tells me ==> /var/log/samba/computerid349.log <== [2016/02/10 14:39:50.313835, 1] ../source3/printing/printer_list.c:226(printer_list_get_last_refresh) Failed to fetch record! [2016/02/10 14:39:50.313949, 1]

I have setup a Samba 3.024 server on Solaris. I have successfully enabled two-way trusts between my samba domain and my legacy PC Netlink domain. (PC Netlink is the solaris port of NT4 aka Advanced Server for Unix.) My Samba domain includes 2 Windows 2003 Servers (One is Windows 2003 SP1, the other is Windows 2003 R2 SP2.) The PCNL server supports Windows 2000 Servers and XP Pro clients.

Hello all, Relevant info up front: Gentoo PC, using 2.6.38 kernel and Samba 3.4.12. I'm trying to get a FreeRadius instance working for our Windows network. To do so, I need a Linux box running Samba. I've installed and configured Kerberos, Samba and FreeRadius, and can get most things to work. I can get a Kerberos key using kinit, and "sudo net ads keytab list" shows me

I'm running Samba v4.4.4 as a domain member server in security=domain mode. Our 3 domain controllers are Server 2012r2. Every 3-4 days, I see log messages from winbind saying "winbind_samlogon_retry_loop: sam_logon returned ACCESS_DENIED". Sometimes this corresponds to a trust password change, but not always. Today, new connections to Samba were failing with the error

Hello! I see where this came up on the list a few months and never really ws resolved. Someone resolved it by linking libnss_winbind ... But that's not my problem... I'm getting " Failed to join domain: failed to set machine spn: Operations error" when I do a net ads join. I've used this user account (me) to join many Samba 3.5.6 servers to the domain. Config file and

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)

Hello! i have some trouble with my samba setup (v3.4.5 or 3.3.10). the server is not responding (or very slow) for some minutes in log.winbindd-idmap i get: ---------------------------- [2010/02/03 04:14:27, 1] lib/util_tdb.c:521(tdb_wrap_log) tdb(/home/samba-server/samba/3.4.5/var/locks/mutex.tdb): tdb_lock failed on list 43 ltype=1 (Interrupted system call) [2010/02/03 04:14:27,