similar to: dual gateway with routing issues and tinc-up and host-up scripts for windows clients?

Am 02.12.2016 um 08:51 schrieb Matthias Kahle via samba: > Hi Marcel > > thx. for your fast response. I didn't manage to follow up sooner. I had already verbose logging turned on but I don't seem to find the real reason, why the domain controller searchs for a userPrincipalName instead of servicePrincipalName. > > Because I wasn't sure whether it is the nfs client

Hi Marcel thx. for your fast response. I didn't manage to follow up sooner. I had already verbose logging turned on but I don't seem to find the real reason, why the domain controller searchs for a userPrincipalName instead of servicePrincipalName. Because I wasn't sure whether it is the nfs client process or the server process that failed to get the kerberos ticket when I tried the

Hi Folks I'm trying to share user home directories hosted on a Samba-4 member server via NFSv4. Everything's working well with the Windows shares but when it comes to kerberized NFSv4 it fails. I can't even mount the home root directory via nfs on the server itself ("mount.nfsv4: access denied by server while mounting ..."). As far as I have tracked it down, it appears to

On Fri, 2 Dec 2016 11:05:50 +0100 Matthias Kahle via samba <samba at lists.samba.org> wrote: > > Does it work if you manually add > > userPrincipalName=CLIENT02.DOMAIN.TLD to your clients ldap entry > > and reexport the keytab? > > I already thought about trying that. So by now, I tried tweaking the > client's LDAP entry. > > Adding > >

On Fri, 02 Dec 2016 12:44:04 +0100 marcel at linux-ng.de wrote: > Am 2016-12-02 12:12, schrieb Rowland Penny via samba: > > On Fri, 2 Dec 2016 11:05:50 +0100 > > Matthias Kahle via samba <samba at lists.samba.org> wrote: > > > >> > Does it work if you manually add > >> > userPrincipalName=CLIENT02.DOMAIN.TLD to your clients ldap entry >

Hi Matthias, adding (or better replacing) the userPrincipalName attribute with the nfs/* one, is exactly what you need to do. For some reason the NFS client's request *only* matches the userPrincipalName attribute, while all other services I tried so far are fine when matching one of the values in servicePrincipalName attribute. NFS seems to be a very special kind of kerberos service as it

Am 2016-12-02 12:12, schrieb Rowland Penny via samba: > On Fri, 2 Dec 2016 11:05:50 +0100 > Matthias Kahle via samba <samba at lists.samba.org> wrote: > >> > Does it work if you manually add >> > userPrincipalName=CLIENT02.DOMAIN.TLD to your clients ldap entry >> > and reexport the keytab? >> >> I already thought about trying that. So by now,

> Does it work if you manually add userPrincipalName=CLIENT02.DOMAIN.TLD to your clients ldap entry and reexport the keytab? I already thought about trying that. So by now, I tried tweaking the client's LDAP entry. Adding userPrincipalName=CLIENT02.DOMAIN.TLD does not succeeed, however, after reviewing the ldap filter once again, I added userPrincipalName=nfs/client02.domain.tld at

kmemdup is introduced to duplicate a region of memory in a neat way. Rather than kmalloc/kzalloc + memset, which the programmer needs to write the size twice (sometimes lead to mistakes), kmemdup improves readability, leads to smaller code and also reduce the chances of mistakes. Suggestion to use kmemdup rather than using kmalloc/kzalloc + memset. Signed-off-by: Fuqian Huang <huangfq.daxian

On Thu, Jul 04, 2019 at 12:27:08AM +0800, Fuqian Huang wrote: > kmemdup is introduced to duplicate a region of memory in a neat way. > Rather than kmalloc/kzalloc + memcpy, which the programmer needs to > write the size twice (sometimes lead to mistakes), kmemdup improves > readability, leads to smaller code and also reduce the chances of mistakes. > Suggestion to use kmemdup rather

kmemdup is introduced to duplicate a region of memory in a neat way. Rather than kmalloc/kzalloc + memcpy, which the programmer needs to write the size twice (sometimes lead to mistakes), kmemdup improves readability, leads to smaller code and also reduce the chances of mistakes. Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy. Signed-off-by: Fuqian Huang <huangfq.daxian

kmemdup is introduced to duplicate a region of memory in a neat way. Rather than kmalloc/kzalloc + memcpy, which the programmer needs to write the size twice (sometimes lead to mistakes), kmemdup improves readability, leads to smaller code and also reduce the chances of mistakes. Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy. Signed-off-by: Fuqian Huang <huangfq.daxian

Hi , I would really appreciate some suggestions re the following issue. We have a LDAP based PDC and a member server. We're use libnss_ldap to auth the users. The LDAP PDC is setup with self signed SSL , we're trying make sure the member server connects to the PDC using SSL. Here is the PDC , smb.conf [global] workgroup = SUNTECH netbios name = SERVER01 security = USER local master =

I have promoted a samba active directory server using the --use-rfc2307 option, my question is, after doing that is it necessary to follow these instructions? https://wiki.samba.org/index.php/Using_RFC2307_on_a_Samba_DC#Extending_the_Schema_for_NIS_Extensions I ask because I am getting the following server01:/home/eduardo # samba-tool fsmo show | grep SchemaMasterRole SchemaMasterRole

Linux debian1 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u1 i686 GNU/Linux it is serving as file server for a few windows pcs in a satellite office. I am trying to join the machine to a AD Domain in our main office. tried[b] net join -U duper%5HaveLefT -d5[/b] debug results:[code]INFO: Current debug levels: all: 5 tdb: 5 printdrivers: 5 lanman: 5 smb: 5 rpc_parse: 5 rpc_srv: 5 rpc_cli: 5

We had a new server put in on our local network and I am unable to mount it's file shares - mount -t smbfs works on the old server but it doesn't work on the new one because of the SMB signing problem. However, I cannot get mount -t cifs to work on either of them. Anyone have any ideas what the problem could be? Thx vperry successful commands: 1) smbstatus calserver01 2)

On Mon, 11 Feb 2019 15:40:02 +0100 Matthias Leopold via samba <samba at lists.samba.org> wrote: > > > Am 11.02.19 um 14:22 schrieb Rowland Penny via samba: > > On Mon, 11 Feb 2019 13:46:05 +0100 > > Matthias Leopold via samba <samba at lists.samba.org> wrote: > > > >> > >> > >> Am 11.02.19 um 13:22 schrieb Rowland Penny via

Did you "hide" the share (browseable = no) Looks ok to me, what i see be low. And what i supsected. Event id 502. Do you see: Error details: “This security ID may not be assigned as the owner of this object.”. If so, or correct the rights, or set gpo. Or read throug this side, and fix your rights setup.

Hi, I'm still getting the errors below on Debian Etch with Dovecot 1.0.8-4 and Dovecot LDA. Is this something that's fixed in 1.0.9? It doesn't seem to have an effect but I'm wary of messages I don't recognise! Regards, Alex Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: 16 Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: 112

On Mon, 11 Feb 2019 13:46:05 +0100 Matthias Leopold via samba <samba at lists.samba.org> wrote: > > > Am 11.02.19 um 13:22 schrieb Rowland Penny via samba: > > On Mon, 11 Feb 2019 12:30:51 +0100 > > Matthias Leopold via samba <samba at lists.samba.org> wrote: > > > >> Hi, > >> > >> we are using a _single_ LDAP server as backend