similar to: Upgrade/migrate, lost workstation trusts

Hello list - I am not sure my messages are getting out to the list, so I will attempt in this message to summarize the problems I am having that have been the subject of a few other posts. I recently upgraded from a command-line Slackware installation to Debian Jessie. As part of that exercise, Samba was upgraded from 3.5.x to 4.1.17. My upgrade method was probably not idea: I recursively

Hi. I'm testing my migration from my PDC running Centos 5.x Samba3+OpenLDAP. to Centos7 Samba4 OpenLDAP 2.4.40 I had move all my settings and the server has all my users, in console I see all my info. Now, I connect a test machine that was on the same domain but I'm getting the bad message went I try to login with a domain user: 'The trust relation between this workstation and the

I have a Samba4 AD/DC running on Slackware64 14.1, Samba version 4.2.12. This computer has been serving a Domain of several Windows 7 and one Linux domain members for about 2 years without problem. On a few occasions lately I've run the following command on the AD/DC: $ ntlm_auth --username="user" --password='password' NT_STATUS_ACCESS_DENIED: Access denied (0xc0000022)

Hello all, I am doing some tests with Windows 7 and a Samba Domain, but into a working SAMBA domain, where windows XP joins without problems, when i try with 7 i recieve an error like "The trust relationship between this workstation and the primary domain failed.". I use OpenSuSE 11.3 with samba 3.5.4-5.1.2 and openldap 2.4.21-9.1. My config of samba: [global] workgroup =

On Fri, Sep 02, 2016 at 11:46:14AM -0400, Mark Foley via samba wrote: > I have a Samba4 AD/DC running on Slackware64 14.1, Samba version 4.2.12. This computer has been > serving a Domain of several Windows 7 and one Linux domain members for about 2 years without problem. > > On a few occasions lately I've run the following command on the AD/DC: > > $ ntlm_auth

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

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, everybody. I'm trying to use a Debian 8.5.0 client machine (with hostname PCSCD850, 10.100.109.5 is its IP) joining an old Samba 3.6.23 tdbsam based PDC (hostname DSSC01, SCDOM is the NetBIOS domain name, 10.200.0.5 its IP). The machine was added to the PDC using useradd (unix) and smbpasswd -a -m (samba). Because there is a group used for the machines

Hello, i'm using Samba Version : 2:3.5.5~dfsg-1~bpo50+2 from backports Patch applied : http://support.microsoft.com/kb/2171571 Key modified : [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000 "DomainCompatibilityMode"=dword:00000001

With samba 4 <-> win7 (* or win8-10) trust issues. Then you have a few things to check Start with checking if your time is in sync. Check the windows even log, for errors, look them up. If its a "bootcamp-ed" windows 7 install ( aka on a imac ), boot in apple, update bootcamp. Last, if you used an imaged windows 7, did you forgot to sysprep maybe? And correct, samba 3.x was

Hello list! I'm trying to debug a problem that surfaced after a Samba upgrade from v3.5.x to v4.1.17. The problem is that Win7 workstations appear to randomly experience domain trust issues logging in, although they can log in some times, they are unsuccessful at other times. I cannot so far predict what would result in or influence this behaviour. These are workstations on which

Howdy, I'm having one last problem with my Samba PDC with an ldap backend. When I add a machine to the domain I get the error, on my Win7 test client, that says: The following error occurred attempting to join the domain "office": A device attached to the system is not functioning. Here are some particulars: # smbd -V Version 3.5.6 (configured sernet repo to install latest

================================================================== "Your brain commands your body to "Run forward! Bend! Scoop up the ball! Peg it to the infield!" Then your body says, "Who, me?" " Joe DiMaggio ================================================================== Release Announcements ===================== This is the latest stable

================================================================== "Your brain commands your body to "Run forward! Bend! Scoop up the ball! Peg it to the infield!" Then your body says, "Who, me?" " Joe DiMaggio ================================================================== Release Announcements ===================== This is the latest stable

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== "Myths are public dreams, dreams are private myths." Joseph Campbell =============================================================== Release Announcements ===================== This is a bug fix release of the Samba 3.2 series. Major enhancements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== "Myths are public dreams, dreams are private myths." Joseph Campbell =============================================================== Release Announcements ===================== This is a bug fix release of the Samba 3.2 series. Major enhancements