similar to: Logon via MS Remote Desktop hangs.

Hello, I have upgraded a client and a freeipa server from Fedora 24 to 25 recently. And I cannot access linux shares located on the F25 client from a windows desktop. I get these messages: [2016/12/01 11:42:19.218759, 1] ../source3/librpc/crypto/gse_krb5.c:534(fill_mem_keytab_from_dedicated_keytab) ../source3/librpc/crypto/gse_krb5.c:534: smb_krb5_open_keytab failed (Key table name

Hello Mario , what if you try these : dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, remote, winreg, srvsvc auth methods = sam, winbind, ntdomain, ntdomain:winbind !! these are only for helping in debugging and should not be used in production. !! see all the e-mails with subject : Re:

Now I have this config on the f25 desktop and restarted the smb service but I still have the same problem. # net conf list [global] workgroup = MYDOMAIN realm = MYDOMAIN netbios name = F25SERVER server string = Samba Server Version %v kerberos method = dedicated keytab dedicated keytab file = FILE:/etc/samba/samba.keytab log file = /var/log/samba/log.%m

Hello Samba team ! On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) : -> One PDC : pdc01 -> Two "slave" DC : sdc02, sdc03 I don't know why, but sometimes Samba receive the SIGTERM signal and restart even if I remove it from the logrotate configuration. On "pdc01" I see : ---------- pdc01 (log.samba) ---------- SIGTERM: killing children

On 6/4/2015 9:57 AM, Mario Pio Russo wrote: > guys sorry to take this thread onboard once more, but I still can't get > this sorted. > > I have compiled the latest tarball from samba, 4.2.2 . compilation works > fine and after that I am able to upgrade from samba 3 with the following > command: > > samba-tool domain classicupgrade --dbdir=/var/lib/samba-ccdc1/dbdir/

Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service

Hi, Just a moments ago i've sent a message to other user saying that I've a working server with CUPS authentication using AD groups. Well, that authentication is not working anymore and i've not changed anything... The thursday I was configuring the server to allow the management of cups with AD groups and was working perfect. After that i've added some printer alias to samba

We added a DNS entry to Samba via the Windows DNS Manager which apparently was invalid. Now we can't see the list of forward lookup in the Window DNS Manager because it immediately errors and we have to restart the Samba service. Running Samba 4.3.11-Ubuntu on Ubuntu 16.04 Additionally, a samba-tool dns query fails with the following error: > $ samba-tool dns query dc1.mydomain.com

>> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba receive the SIGTERM signal and >> restart even if I remove it from the logrotate configuration. On >>

Hi, I have a Samba4 File Server on Debian 10 I am not being able to assign permissions on shares to groups that already have the Unix attribute set. Groups without the Unix attribute are working OK. My two DC are Samba4 (migrated of the Windows 2008 Server) and my current File Servers are Windows 2008 Server. I followed "Setting up a Share Using Windows ACLs" tutorial (

Hello, We have a Windows 2008 DC (inview-dc1 and a samba 4.4.16 (inview-dc2) server as a backup DC. The system for the most-part works OK, but occasionally the Samba DC goes wildly out of sync (with respect to group membership), normally after a change to a large group. I have noted previously before the out-of-sync event occurs, this command always fails thus : root at inview-dc2:~#

identical issues to trying to go from 4.6.11-> 4.6.12, 4.7.4 make fails with 3631/3915] Linking default/source4/librpc/python-dcerpc-smb-acl.so [3632/3915] Linking default/source4/librpc/python-dcerpc-xattr.so [3633/3915] Linking default/source3/smbtorture3 [3634/3915] Linking default/source4/librpc/python-auth.so [3635/3915] Linking default/source4/auth/gensec/pygensec.so [3636/3915] Linking

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

Thanks Garming. We currently use a standalone bind DNS server. Will the later version of samba work without the integrated DNS backend? Cheers Chris On 21/06/18 23:41, Garming Sam wrote: > Hi, > > Many of these syncing problems were solved in Samba 4.7 (and probably a > few more in 4.8). There were a number of unresolved locking issues that > we uncovered as well as some

Hi, I'm attempting to build 3.6.25 after applying the 16-Dec-2015 and the 12-Apr-2016 patches from samba.org but I'm seeing two issues. First during autogen.sh I see: /build/samba/samba-3.6.25/source3 # ./autogen.sh ./autogen.sh: running script/mkversion.sh ./script/mkversion.sh: 'include/version.h' created for Samba("3.6.25") ./autogen.sh: running autoheader -Im4

On Samba AD DC most of these enpoint server are already running -- dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, mapiproxy Use samba-tool testparm -v first before adding them to the smb.conf I say this because I could not "join" Windows clients to Samba with these running

Hi List, I?m attempting to configure an Active Directory joined CentOS 7 host to share directories with Windows clients using Samba. The machine has been joined to the domain via: ?adcli join --stdin-password --domain-ou=?OU=Servers,DC=domain,DC=com' --login-user={{ private_ad_username }} -S dc1 DOMAIN.COM". Logging in to the host via ssh with AD user credentials works fine. I have SSSD

2016-04-01 23:36 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 30/03/16 13:35, Prunk Dump wrote: >> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba

Hallo When rejoining a dc to the domain I get the following error message: [2015/07/02 11:51:44.089786, 0] ../source4/librpc/rpc/dcerpc_util.c:729(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for

Hi folks, I'm trying to support a customer with multiple AD forests, and during my research, I've observed some odd behavior. In my lab tests, it seems like authentication works for users in all trusted forests, but only if NTLMSSP is used. When Kerberos ends up being used, authentication only seems to work for users in the local domain. Here's the test setup: - Two Active Directory