similar to: Issues with FLOCK on NFS Share

Hello, I try to compile Samba 4.11.6 on an old SLES11 machine. There is an old GNUTLS installed. Since I do not have root access and I have to use a newer GNUTLS-Version, I have installed gnutls-3.6.12 in a different location and set PKG_CONFIG_PATH appropriately. The configure script has run successfully, but when I run make (with verbose option), I get this error: 17:44:33 runner

On 30/06/2020 14:55, Ralph Boehme via samba wrote: > Howdy! > > Am 6/30/20 um 2:37 PM schrieb Georg.Biberger--- via samba: >> We are using Samba 4.10.16 as a readonly file server on a linux box with SLES 12. All is working fine with our NAS NFS Shares. We are now trying to integrate new NFS Shares from an archive provider. We have some problems with samba not responding, when

Smb.conf: [global] security = ADS workgroup = MUC realm = europe.bmw.corp netbios name = EDAINT netbios aliases = edaint.muc log file = /lfs/EDA/DATA/SOFTWARE/samba/var/log/samba/%m.log log level = 10 # Default ID mapping configuration for local BUILTIN accounts # and groups on a domain member. The default (*) domain: # - must

Howdy! Am 6/30/20 um 2:37 PM schrieb Georg.Biberger--- via samba: > We are using Samba 4.10.16 as a readonly file server on a linux box with SLES 12. All is working fine with our NAS NFS Shares. We are now trying to integrate new NFS Shares from an archive provider. We have some problems with samba not responding, when accessing files on these archive NFS shares. > We have done some

> Howdy! > > Am 6/30/20 um 2:37 PM schrieb Georg.Biberger--- via samba: >> We are using Samba 4.10.16 as a readonly file server on a linux box with SLES 12. All is working fine with our NAS NFS Shares. We are now trying to integrate new NFS Shares from an archive provider. We have some problems with samba not responding, when accessing files on these archive NFS shares. >> We

Hello, We are using Samba 4.10.16 as a file server on a linux box with SLES 12. All is working fine with our NAS NFS Shares. We are now trying to integrate new NFS Shares from an archive provider, but samba gets crashed when a client tries to access files on these shares. New start of samba is required! In the smbd.log, I see these entries: [2020/06/24 17:58:23.118208, 1]

Hello, Get same output with "getent passwd qqeda11" and with "cat /etc/passwd | grep 'qqeda11'" qqeda11:x:79846:65600:Project Account for EDA:/home/qqeda11:/bin/bash When you say it is not supported, do you mean it is not supported by samba, or by what else? Georg

>Your user has the RID 1581344 and the 'rid' backend uses this along >with the low range to calculate the users Unix ID, so from the commented >line, this would be: >79846 + 1581344 = 1661190 >This is less than the high range, so would be valid. >But if you use '100001-500000000' for the range, the ID would be: >100001 + 1581344 = 1681345 >This would

Hello, When I run "cat /etc/passwd | grep 'qqeda11'", on my linux box, I get: qqeda11:x:79846:65600:Project Account for EDA:/home/qqeda11:/bin/bash When I run "wmic useraccount where (name='qqeda11' and domain='MUC') get name, sid" on my windows box, I get: Name SID qqeda11 S-1-5-21-43206524-2104247658-1151357142-1581344 so the user is an AD

On 01/07/2020 12:59, Georg.Biberger--- via samba wrote: >> The 'idmap config' lines are borked, the default domain '*' lines are >> okay, but the 'MUC' domain lines are half correct, yes you can use the >> 'rid' backend, but you must set a range. You did set a range, but it was >> incorrect and you have commented it out. The two ranges must

On 06/07/2020 08:28, Georg.Biberger--- via samba wrote: > How can i achieve that the user qqeda11 is mapped to the the unix id 79846? > Background: All NFS files are only accessible by unix user qqeda11 with unix id 79846! > > Georg Where does '79846' come from ? If you run this: cat /etc/passwd | grep 'qqeda11' Do you get something like this:

On 06/07/2020 15:30, Georg.Biberger--- via samba wrote: > Hello, > > When I run "cat /etc/passwd | grep 'qqeda11'", on my linux box, I get: > qqeda11:x:79846:65600:Project Account for EDA:/home/qqeda11:/bin/bash That makes 'qqeda11' a LOCAL Unix user > > When I run "wmic useraccount where (name='qqeda11' and domain='MUC') get name,

>The 'idmap config' lines are borked, the default domain '*' lines are >okay, but the 'MUC' domain lines are half correct, yes you can use the >'rid' backend, but you must set a range. You did set a range, but it was >incorrect and you have commented it out. The two ranges must not >overlap, but what you had before you commented it out, well,

On 7/6/20 11:00 AM, Rowland penny via samba wrote: > On 06/07/2020 16:29, Georg.Biberger--- via samba wrote: >> Hello, >> >> Get same output with "getent passwd qqeda11" and with "cat /etc/passwd | grep >> 'qqeda11'" >> qqeda11:x:79846:65600:Project Account for EDA:/home/qqeda11:/bin/bash >> When you say it is not supported, do

Hi there, We are thinking about sharing same files: - OS2/Win clients with Samba - Linux clients with NFS. So, the same files would be shared by 2 different protocols. Looking at the open.c samba code, there seems to be no check / no error (sharing violation) returned to the smb client when the file is already locked by an NFS client. - So, even if a file is opened and locked by an NFS client,

Hello, I am using Samba as file server as member of a windows domain. Kerberos is configured with kerberos method = secrets and keytab Currently some (not all) users get issues when connecting to samba shares from windows. In the corresponding samba logs I found entries: .... [2020/07/23 12:08:06.697678, 1] ../../source3/librpc/crypto/gse.c:660(gse_get_server_auth_token)

Samba 3.0.28-0.1.95-1624-SUSE-SL10.3 A strange problem (best read in a proportional font). It only happens on an x64 XP client when accessing a Samba share. The exact same program runs fine on the same x64 XP client when the share accessed is on a Windows server or when it is run on a 32-bit XP client, regardless of whether the share belongs to a Samba server or to a Windows server. I have

Attached smb.conf Georg

Hi Louis, >Try > >net ads keytab add_update_ads cifs/$(hostname -f) -U Administrator >And i hope this is not your hostname : lpeda1.muc >Because thats a domainname. > >Also make sure you check the resolving of the A and PTR records > >Greetz, > >Louis My hostname is lpeda1! hostname returns "lpeda1" hostname -f returns "lpeda1.muc". Is

On 28/02/2020 18:01, Georg.Biberger at partner.bmw.de wrote: >> SLES11 is EOL and is python3 easily available for it ? > BMW has extended support from SUSE for SLES11 until end of 2021, so no EOL. > I use phyton2 with "export PYTHON=python2" I thought the extended support was for security updates only and whilst you should be able to build Samba using python2, you need