similar to: unable to fetch password

Hello Samba folks, A couple years ago I installed Samba 2.2.0 on our HP9000 running hpux 10.20. I am now trying to install it on a customer's HP9000 and am getting the error "No locking available. Running Samba would be unsafe" while executing the configure command. I got that error a couple years ago and resolved it by linking /usr/bin/cc and /opt/ansic/bin/cc but that is not

I'm new to SAMBA, so I apologize up front if I ask a dumb question! We upgraded from solaris 8 (samba2.2.8a) to solaris 10 and installed samba 3.2.4. When user tried to use samba, they got "Failed to open /usr/local/samba/private/secrets.tdb". I thought maybe the file just needed to be there, so I touched the new file into existence, and then they got this error: "ERROR:

I had a machine account created in the NT domain and successfully joined the domain by running "net join MEMBER -S <PDC>". The timestamp of the secrets.tdb changed. I got the "Joined domain MYDOMAIN" response. I think there may have been some conversion to active directory but still running NT domains. When I attempt to run from Solaris "./smbclient

Since upgrading S4 DCs I am see the following message in log.samba - DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested: FFFFFFF8Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an undetected RODC? DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested:

I have setup a dedicated print server running on RH 8 with Samba 2.2.5-10 and LPRng-3.8.9-6 to service a HP9000 printer. The print queue for this HP9000 gets it print jobs from a Windows server via a script and the queue is set to HOLDALL status. The HOLDALL status is necessary because the script runs overnight to produce the print jobs which can total anywhere from 500 to 12,000 individual print

Hello again, I sent in this error a couple weeks ago and one person (eric) kindly responded and tried to help, but to no avail. Any one else have any ideas on the following: A couple years ago I installed Samba 2.2.0 on our HP9000 running HPUX 10.20. I am now trying to install it on a customer's HP9000 (also using 10.20) and executing the configure command produces the "No locking

When configuring a SunOS 5.9 box running Samba 2.2.8a with security=domain, as per http://us2.samba.org/samba/docs/using_samba/ch04.html#samba2-CHP-4-SECT-7 I get the following error "could not fetch trust account password for domain" when trying to connect to a share via 'net use * \\server\share /user:domain\username' However, 'security=user' works correctly.

I have a few errors I'm trying to chase down in an effort to get a Win7 client in my domain. WinXP works -- tested unjoining and rejoining today, and it can still join. I have the registry adds for DNSNameResolutionRequired=0 under LanmanServer&Client/Params (put it in both places in attempt to get things working), as well as a DomainCompatibilityMode=1 I've tried moving to winbind

Garming - thanks for your quick response. That link you gave me has Samba 3.x patches. I didn't notice any links to 4.x patches. Official Distro Releases are often behind the current stable release, generally. In fact, when I first installed Samba4 the Linux version was more recent than the Ubuntu version. This lag is probably due to abundance of caution and/or lack of manpower. I

Hai Tom, Im not in 4.2 yet, but maybe i can help analize your problem. ( as long its possible, big power outage in the netherlands.. ) this : https://lists.samba.org/archive/samba/2014-September/185031.html is a good example how not to setup your samba server. so before we can think with, please post (and sorry if its again) some info. Your OS? Compiles samba or os provided samba, or

> Subject: [Samba] Cant fetch on Window network due to special characters > infilename. > > Hi All, > > I am new to this group :) . Please accept my warm regards! > > While I am trying to access files on Windows share that contains special > names the smbclient fails up as shown below: > > Lets say the filename is Bryan Adams - Let's Make a Night to

On Mon, 19 Sep 2016 10:50:25 -0400 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba > wrote: > > Since upgrading S4 DCs I am see the following message in log.samba - > > The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844 > > -4736-9972-e26453333856, are we an

https://bugzilla.mindrot.org/show_bug.cgi?id=1619 Summary: unable to fetch the files from remote server Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: sftp AssignedTo: unassigned-bugs at mindrot.org

If it is that bug that you're referencing, besides obviously upgrading, you could try to patch it yourself. Whether or not you need to patch this, probably depends on whether or not your users are actually seeing issues. All that seems to happen is that it's entering a failure case when it hasn't actually failed. https://www.samba.org/samba/patches/ Cheers, Garming On 04/07/16

I am getting the following error when executing puppet agent --test from the node to force it to get its node definition [root@localhost puppet]# puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Failed to find puppetnode.localdomain via exec: Execution of ''/etc/puppet/snc_enc.py

I have installed Samba-tng as PDC. It works fine. Now I'd like to install Samba-head server on same machine as domain member and to auth users through PDC. I have joined Samba to domain with smbpasswd -j KIROV. It says Joined Ok. But users can't see any shares on samba-head server. smbd/password.c:domain_client_validate(1556) domain_client_validate: could not fetch trust account

Hi all, I am a samba rookie with a problem. I have replaced an old server with a new server, and copied over the original samba config which was for samba file but the new server has samba 3.0.5 while the old version was 2.0.7. I had problems connecting to samba, so I tried using the supplied default config file and then migrated the original settings to the new file. problems still persisted.

I am getting the following error after running the command # ./smbclient //xxxx888/tmp ... Password: session setup failed: NT_STATUS_LOGON_FAILURE >From debug level 2 domain_client_validate: could not fetch trust account password for domain XXXX I had earlier joined the domain by running the following command # ./smbpasswd -j XXXX 2003/11/13 16:27:59 :

Specifics samba-3.0.0beta1-1.i386.rpm on RedHat 9 and smbpasswd authentication, the machine is the PDC and security is set for user. The machine account was setup on the fly and it appears in passwd, shadow, and smbpasswd files as it should. However it seemed to take a very long time to join the domain, about 1-1/2 minutes. I can browse the Samba PDC machine and access the shares, etc. After

I upgraded from 4.1.23 to 4.2.12 and am now getting (lots of) messages: Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC? I found an almost identical message (titled: "Update samba4 from 4.1.17 to 4.2.1 failed") on the web from May 22, 2015 at: http://samba.2283325.n4.nabble.com/Update-samba4-from-4-1-17-to-4-2-1-failed-td4686215.html but saw no resolution other