similar to: Problem getting Samba fully working

Hello, what is the cause of this error? [2013/03/21 15:22:41, 1] rpc_client/cli_pipe.c:949(cli_pipe_validate_current_pdu) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_ACCESS_DENIED received from host xxx.yyy.zzz! Thanks, Ricardo

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,

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 =

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]

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,

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

Hello, After update to 4.7.4 on my DC's I see some strange, non-critical (I think) though behaviour. I've noticed that: sometimes running command wbinfo -u doesn't list any of the users, in log i see this: *../source3/rpc_client/cli_pipe.c:568(cli_pipe_validate_current_pdu)* *../source3/rpc_client/cli_pipe.c:568: RPC fault code DCERPC_NCA_S_PROTO_ERROR received from host dc3!*

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

Hello, I saw on my member servers in winbindd.log sometimes the following message appearing: [2009/05/29 21:51:53, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(755) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from host GENOME, pipe \lsarpc, fnum 0x7101! What does this error mean and how can I fix it? PDC and meber server are running 3.3.4.

I thought I had setup winbind correctly as I can login to my ubuntu 9.04 machine with domain users, but I am trying to get ntlm working with squid, and while testing winbind I get the following error. sudo wbinfo -a MBAG\\user%passwd plaintext password authentication failed Could not authenticate user MBAG\user%passwd with plaintext password challenge/response password authentication failed error

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! 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

Hi all, After building Samba 4.1.20 for Ubuntu 14.04 x64 I encountered this issue when using shared printers: every time a client prints or changes printer settings, this message is logged in the log: dcerpc_spoolss_ReplyClosePrinter failed [NT_STATUS_RPC_PROCNUM_OUT_OF_RANGE]. Printers print fine, so it is probably harmless, but I still wonder why this happens. With log level = 3 I get

I'm testing out a new Samba setup to hopefully replace my aging Win2k domain. I've got some of it working: - My PDC (shadow) seems to be working on the CASA domain with an LDAP backend. - nss_ldap and pam_ldap are working on shadow - I can run wbinfo -u and get the user info from LDAP on shadow. - I can run wbinfo -a username%password and authenticate a user on shadow. I can run

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

Hey List- I've got 2 samba servers. PDC: FreeBSD 5.4; samba: 3.0.23 ? name: bugs member server: FreeBSD 6-stable; samba: 3.0.23 ? name: daffy note: config files are at the bottom of the email The PDC was running an older version, but I just upgraded and it didn't fix the below issue. The member server was running fine with the old smb.conf file, but I rebuilt the server and now it

>From what I can tell it does look as if I have to run winbindd on member servers, even if NIS is used, to get SID's mapping consistently across the domain. The PDC is Samba 3.025a on Solaris 10. Two member servers are Samba 3.025a on solaris 9. If i start winbindd on a memv, the "wbinfo -u" and "wbinfo -g" commands show my users and groups. However, the