similar to: could not fetch trust account password for domain

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

Help! I have two computers, both running HP-UX 11.0, both running 3.0 alpha23 (the second computer's samba trees were copied from the first, so they are identical). Mapping a drive from an XP SP1 computer has NO problems on the first HP server. On the second one, it displays the message "Configuration information could not be read from the domain controller, either because the machine

Good day oh technical ones . I was running Samba 4 (client only, not using it as a DC so effectively running Samba 3 code from the Samba 4 tree) and, other than a little "Gotcha!" regarding decoding Kerberos PACs, it was all working perfectly. Then recently I had to upgrade, to "4.2.0pre1-GIT-b505111" (I had to upgrade the OS on the server

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

Hi Dear Samba Gurus, We're planing to migrate the old samba server to a new samba server. But the person who maintain old samba server have left, so we need to figure out the configuration steps from the old config file. Now the things that confused me now is the setting with "security=domain", the old samba server config global sections are: log level = 3 netbios

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

can you try : smbclient //SERVER.DOMAIN.TLD/netlogon -k bet that works.. Louis >-----Oorspronkelijk bericht----- >Van: heinz.hoelzl at gvcc.net >[mailto:samba-bounces at lists.samba.org] Namens Heinz H?lzl >Verzonden: dinsdag 14 april 2015 10:55 >Aan: samba at lists.samba.org >CC: pug at felsing.net; schnaggy at schnaggy.de >Onderwerp: Re: [Samba] samba 4.2 RDP

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to set up a Linux/Samba box to authenticate users (on Windows 2000 and XP boxes) against a Windows NT4 Primary domain controller but failed with what I tried so far. - - both machines are on the same local network (192.168.17.X) - - the windows box runs NT4. I havn't set up this and I don't know much about it either but I have

hi Louis, same result: NT_STATUS_LOGON_FAILURE heinz Am Dienstag, 14. April 2015 11:20 CEST, L.P.H. van Belle <belle at bazuin.nl> schrieb: > can you try : > > smbclient //SERVER.DOMAIN.TLD/netlogon -k > > bet that works.. > > Louis > > > >-----Oorspronkelijk bericht----- > >Van: heinz.hoelzl at gvcc.net > >[mailto:samba-bounces

Hello, I'm running redhat 3 enterprise server as. I installed samba during the install, and it's been running for about a week now. I looked in the LogWatch, and noticed this bit: --------------------- samba Begin ------------------------ **Unmatched Entries** auth/auth_domain.c:check_ntdomain_security(289) check_ntdomain_security: could not fetch trust account password for domain

hi, now i did some tests with the "auth methods" option. "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest" -> RDP works -> smbclient -k does not work "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest, samba4" -> RDP hangs an the welcome-scrren -> smbclient -k works fine

I am trying to establish 2 way trust relationship between samba domain and Win2008 AD domain. The trust relationship is established and even verified by both side, but when I try to access samba resources from win2008 domain, it prompts for username and password. However, I can access the win2008 resources from the samba domain without the prompting of username and password. My win2008 is

Question: I want to setup a Samba server as a domain member, allowing Windows PC to map unix server directories, but having the authentication performed by our Windows Domain Controller(s). I'm basically following this example from the Samba docs: http://us1.samba.org/samba/docs/man/Samba3-HOWTO/domain-member.html#id2538809 It appears to me that I must "net join" the domain from

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

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

I'm having some troubles with the winbindd. When trying to access a samba share, I receive the above error in the MACHINE_NAME.log file. I've ran the command smbpasswd -j MY_DOMAIN -r PDC -U Administrator, and it worked fine. wbinfo -u returns "Error looking up domain users", but I'm not sure if this is related to my 1st problem. I'm going to dump in my config files,

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.

Hey All, I'm having problems with a Trust relationship between our Win 2002 PDC and our Samba PDC. Here are the details: (names have been changed to protect the innocent...!) Win 2002 PDC: WINPDC, IP 1.2.3.4 Client in Windows Domain: CLIENT Samba PDC in Domain TEST: SMBPDC I use Start -> Run -> \\SMBPDC on a machine in our Windows 2000 Domain and got an error saying "\\SMBPDC, A

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