similar to: cli_rpc_pipe_open_schannel_with_creds: rpc_pipe_bind failed with error NT_STATUS_RPC_PROTOCOL_ERROR

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 I actually have troubles to join a samba4 machine into an old samba3 domain. I know I know most of you will yell reading this, but i have to deal with a customer's very old environment :) They're thinking about migrating fully in samba4, but it will take some times so for now let's focus on the situation we have Configuration: - Samba3 PDC :3.5.18-28 - Samba4 client Debian 8.7

Em 05-05-2016 00:14, Jones Syue escreveu: > > How about add 'server signing = auto', > for example: > > [global] > server signing = auto Hi, Made no difference if set on the member I want to add to domain, but when set to the server I got this on member: mic-158 samba # net rpc join -S PDC -U domadminuser No realm has been specified! Do you really want to join an

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:

On 22/05/2019 15:02, Julien TEHERY via samba wrote: > Hi > > I actually have troubles to join a samba4 machine into an old samba3 > domain. > I know I know most of you will yell reading this, but i have to deal > with a customer's very old environment :) > They're thinking about migrating fully in samba4, but it will take > some times so for now let's focus

Hi all, Seems we're in much more trouble now... Yesterday I lowered the dn stombstone lifetime from 180 to 60, to reduce the size of DC=DomainDnsZones, and ever since, things have become terrible... The situation now: I have separate fileserver, and three DC3's, all on the same subnet, kvm virtual machines, all running sernet-samba. (4.1.7 and 4.1.9) == on DC3 == DNS queries for my

Em 28-04-2016 12:14, Rowland penny escreveu: > On 28/04/16 15:16, MI wrote: >> I have a Samba 4 NT4 PDC (Version 4.1.17-Debian) with openLDAP. >> >> I would like to add another server, and have it authenticate users >> against openLDAP. I thought I had to add the new server to the domain >> with "net rpc join", but that seems to think I want to join an

I've got a couple of Samba4 DCs running as VMs for testing. The primary AD DC went smoothly. The second VM joined properly and all but it's only when I get to the replication tests that I see errors. This is following the wiki When I run the command "samba-tool drs kcc -Uadministrator windowsdc.mycrap.cnpapers.dom" I get an error indicating that

Greetings, I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723, 'NT_STATUS_RPC_PROTOCOL_ERROR')" error when I try to run the samba-tool drs showrepl command.

Hi , I 've been trying to get my 2 Samba DCs to replicate between each other but it fails DC1: Freebsd-9.1-Release, Samba 4.02, hostname ldap1, objectGUID: a2454bb4-9f94-4879-a5ff-c1a40537cb5e DC2: Freebsd-9.1-Release, Samba 4.02, hostname ldap2, objectGUID: 0103c98e-0b54-4ca4-a4e5-2259fa6b0563 ===the output showrepl command========== [root at ldap1 ~]# samba-tool drs showrepl

Hi folks, sorry for the re-post, I need some help to solve this problem. Since my previous e-mail, we made a set-up: there is a Clear Pass device (Aruba), which controlls the network access for users. Between the CP and these two DC's there is a load balancer. But, when we stopped the DC1, which was set up first, and the DC2 works continously, then the authentication of users is stopped

On Thu, Apr 16, 2015 at 02:33:20PM +0000, Donaldson Jeff wrote: > My apologies, went to paste and accidentally sent the message...see below for rest of detail. > > > Greetings, > > > I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is

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

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 =

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

Hi, We've got a few layers of firewall between our DCs and a domain guest providing winbind services. What I've noticed is that on first run winbind tries to use the high ports to set up part of the communication. During that process, the winbindd process runs at 100% CPU, and it takes about two minutes to time out. After that time things settle down and winbind works perfectly. For

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

Hi list, We use samba 4.1.17 (debian's version) on several DCs. I just realized that one of them is desynced and cannot get it to resync. The long story: we got 5 DCs splitted over several sites. Recently we had to replace one of them (let's call him DC5). Since both had to run in parallel for data recovery/users work we decided to join a brand new DC (DC6) and latter demote the

Debian "testing" recently released a large version jump update to Samba (3.6.6 to 3.6.15). After the upgrade, winbind no longer works which, according to the information in the bug report, is due to authentication again a Windows 2000 DC. https://bugzilla.samba.org/show_bug.cgi?id=9615 Are there any plans to patch this bug, or is winbind against a W2K DC forever a nonviable