similar to: Change in behaviour for the "%U" substitution in 4.10.8?

Hai, Yes, the repo does not allow different versionnumbers, but i do have all my versions in backup. I made a few tar.gz for you so you can test again with 4.10.7 on a local repo. You can find them here. http://downloads.van-belle.nl/samba4/ The 4.10.7 for Stretch Buster and Bionic source and deb's are there to get. Greetz, Louis > -----Oorspronkelijk bericht----- > Van:

Hai, ? Well, i did go throught the bug reports, and i could only find one simular thing but in the printing functions. https://bugzilla.samba.org/show_bug.cgi?id=13745? ? Can you run this debug script for me, that give me all i need to know about you system and setup. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh ? Then set debug level 10 and try again. if

I found the same bug, and discounted it as irrelevant...I can't see the details of the bug related to the CVE which was the only 4.10.8 change, but I can't imagine that would have anything useful either. Just to be clear, do you want information and logs from the working 4.10.7, the broken 4.10.8, or both? Thanks 17 Sep 2019, 14:58 by samba at lists.samba.org: > Hai, > ? >

This is unfortunately still happening - anyone else have any other ideas? As a reminder/summary of the information from earlier in the thread; - My [homes] share is "path = /shares/DOMAIN/%U" - I am logging into a Windows 7 client as "DOMAIN\username" - My log.smbd shows "canonicalize_connect_path failed for service username, path /shares/DOMAIN/domain_username"

Ok so for [homes] is correct now. ? > I'm tempted to try and blow the smb.conf away, Thats not needed in my opinion, at least not yet. ? > However the other share that uses the "%U" substitution in its path still does not work because it's looking for the wrong path on the server.? Have you tried to replace?%U in the path off?the?not working share with ?%u? ? ? ? ?

Before i want level 10 logs.. Can you try this for [homes] [homes] readonly = no That it, nothing more, nothing less.. Thanks Rowland for this part. It might help to understand a few things better, at least it helped me. :-) In theory %S, %u and %U should all be the same, the users name. If you check what they mean, you will find this: %S : the name of the current service, if

Have you tried running net cache flush after you have removed the SERVER lines from you config? Regards Am 06.09.19 um 12:33 schrieb gac via samba: > I've now changed the ownership to root, as you suggest. > > I've removed the ACLs from /shares/DOMAIN - they don't need to be there as anyone can enter this directory already so there's no need for them. > > The

I've now changed the ownership to root, as you suggest. I've removed the ACLs from /shares/DOMAIN - they don't need to be there as anyone can enter this directory already so there's no need for them. The ACLs on my individual home directory: root at server:/shares# getfacl /shares/DOMAIN/username getfacl: Removing leading '/' from absolute path names # file:

I opted for 'remove the SERVER lines' (since I don't remember why they are in there) - but this hasn't changed the behaviour. The log file contains a different error message, but still refers to the incorrect path --- [2019/09/06 09:43:14.955067,? 0] ../../source3/smbd/service.c:784(make_connection_snum) ? make_connection_snum: canonicalize_connect_path failed for service

No problem -?https://pastebin.com/G8pa3bdE <https://pastebin.com/G8pa3bdE> 6 Sep 2019, 10:28 by samba at lists.samba.org: > On 06/09/2019 09:47, gac wrote: > >> I opted for 'remove the SERVER lines' (since I don't remember why they are in there) - but this hasn't changed the behaviour. The log file contains a different error message, but still refers to the

No problem - I've pastebin'ed it rather than include it, I don't know what this list's preferences are for config files.?https://pastebin.com/70vTmWyL <https://pastebin.com/70vTmWyL> Note that there's a lot of lines in there - the config has been ported between several boxes and upgrades over at least the 6 years I've been with this company. The thing to remember is

Hai, Before we can say its a bug. Can you show the complete smb.conf Anonimized where needed offcourse. Yesterdays subject "Samba, Time Machine, and ADS" Replied that if working now for him, so whats the the difference here. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens gac via samba > Verzonden:

Hi knowledgable Samba folks, I have a Samba server (Ubuntu 18.04, with the packages from apt.van-belle.nl so that I can run recent versions of Samba with Time Machine). This box is configured to use Active Directory authentication as a domain member. Happy to share relevant parts of configuration if necessary, feel free to just ask. I have two shares that are configured to use %U username

I have now - the 'net view' output is now sensible, and reports "Time Machine for gac" (which is the expected comment). But in log.smbd, it is now looking for a folder called "/backups/timemachine/DOMAIN\username" so access to the share itself is still not working 18 Sep 2019, 11:54 by samba at lists.samba.org: > Have you tried to replace?%U in the path

Re: macOS, I was wondering that too, particularly since my Mac is not bound to any domain. But there's a Windows 7 laptop on my desk at the moment which is bound to the same AD domain as the troublesome server and is showing the same symptoms. I'll pick up some log fragments tomorrow, I'm not in the office right now? 18 Sep 2019, 16:52 by samba at lists.samba.org: > On 18/09/2019

I imagine the numeric UID is my old boss who left the company a few years ago, and by this point his account has been removed, not just disabled. The only thing contained by the DOMAIN directory is a home directory for each user, which is owned by them. So I don't _think_ this is the problem. The command you suggested returns: winbind_lookup_rids failed: WBC_ERR_DOMAIN_NOT_FOUND The ACLs

On 18/09/2019 16:39, gac via samba wrote: > I have now - the 'net view' output is now sensible, and reports "Time Machine for gac" (which is the expected comment). But in log.smbd, it is now looking for a folder called "/backups/timemachine/DOMAIN\username" so access to the share itself is still not working Can we see the log fragment that shows it looking for the

On 06/09/2019 09:11, gac via samba wrote: > No problem - I've pastebin'ed it rather than include it, I don't know what this list's preferences are for config files.?https://pastebin.com/70vTmWyL <https://pastebin.com/70vTmWyL> > > Note that there's a lot of lines in there - the config has been ported between several boxes and upgrades over at least the 6 years

Hello all, I have a weird problem. We have several Windows 10 machines on our Network. All but one run older releases than 1709. We are using roaming profiles on those machines. The share is setup up as to allow different profiles depending on the machine used (see below). The %a is used as a legacy from times where WinXP and Win7 were used in parallel. The path then looks like this:

Am 30.08.19 um 13:09 schrieb L.P.H. van Belle via samba: > Now Christian, this failes for me. > radtest -t mschap 'NTDOM\username" 'passwd' localhost 0 testing > ( MS-CHAP-Error = "\000E=691 R=1 C=58f41f1a946ac94a V=2") > > So my question here is, are the username at REALM logins also working for you. > And are you using in smb.conf : winbind use