similar to: unexplained 'access denied' for windows workstations

On 3/3/2016 2:02 PM, Marc Muehlfeld wrote: > It would help if you would provide some information about your system: > - Samba version - smb.conf - "ls -ld" of the directory - etc. Regards, > Marc Hello, version: samba-4.3.4-1.fc23.x86_64 ls -ld: ls -ld /home/blaster drwxrwx--- 76 blaster users 4096 Mar 3 14:15 /home/blaster testparm Load smb config files from

Hello, I'm having a permissions problem I just can't quite figure out. I can not access any directory that is owned by my userid if the permissions are 700. If I change them to 770, with my default group on the directory, then I can access the directory. This was working fine with Fedora 19 for several years, and it broke when I upgraded to Fedora 22, and still broken with F23. my

Hi, finally everything is working fine on my Samba 4.6 AD Domain member server after _exactly_ following https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs (no more fiddling with acl_xattr:ignore system acls = yes, thanks Rowland Penny). Next thing i wanted to try is vfs_shadow_copy2 (with LVM snapshots:

I could still really use some help here.... After spending hours on this, I have determined that it's only my user account that is having this problem. Everyone else can access 700 files/directories owned by them just fine. Thinking of perhaps a UID conflict somewhere, even though there didn't appear to be one, I deleted my account and recreated it with a new UID, copied everything

I've just upgraded my DM from samba 4.5 to 4.8, using luois repos (also, debian jessie -> stretch). I'm experimenting some troubles on some shares, seems that both guest access and 'machine account' access does not work. The share is rather simple: [wpkg] browseable = No comment = WPKG Automated Software Deploying System force create mode = 0664 force directory mode =

Hello, I am experiencing a strange behaviour that I think might be a bug. I was advised to consult the mailing list instead of trying to file a bug, so here it is. I have a user `kate` which is both a member of a `family` group and a `feddkate` group. There is a share called `FeddAndKate` which I what to be accessible to the `feddkate` group but not to a `family` group, and I've set up

Hello, I have domain NAVIDOM. There is also a fileserver that has joined the domain (both file server and DC are samba 4.6.0). If I try to connect as NAVIDOM\Administrator, I cannot access the file server (from Linux and Windows): [root at dc var]# smbclient -U Administrator -L fileserv Enter NAVIDOM\Administrator's password: session setup failed: NT_STATUS_ACCESS_DENIED I can do it as

Hi, My configuration: 1 server with Samba4 as a DC (dc01) 1 server with Samba4 as a file/print server DC seems to work fine. file server is connected to DC using this howto https://wiki.samba.org/index.php/Samba/Domain_Member smbd, nmbd, winbindd is running on file/print server. Bu when I try with a windows client (a windows 2003 server) to connect to file server. client ask for a user

We've a Samba 4 domain (no AD, just DC) with LDAP backend on Ubuntu 14.04. This server has been migrated from files backend to LDAP by the previous maintainer, I know the version is pretty old but we cannot update at the moment. The domain works fine with some W7 and W10 (updated from 7) computers, but we have purchased a new Lenovo laptop with Win10 which joined the domain seamlessly but

Hi all, Just migrated users to a samba 4 server on built on Solaris 11 samba pkg. Some users are mapping all required drives (G:, H:, and I:) but some are not able to map them. The affected users user log files indicate that the %g variable is being translated to '-1' instead of the users Unix group. I would welcome any feedback or suggestions on how to resolve this issue. >From my

I have a toshiba multifunction device that can save to an smb share. For years its been saving to an windows server. I'm trying to move it to samba 4.x. My samba 4 is running an samba AD DC on a machine called vc1. The samba 4 file services is running on a system called srv1. I've made the share on the srv1 smb.conf and have been able to connect to it using the smbclient tool. I've

Hai Marco, Few pointers. First, time is in sync? I guess it is, but check it. Second. Guest access enabled on a domain joint PC ? If you really really want that, then enable user guest in the AD also. But better is avoiding Guest access completely. Join the domain, dont allow guest access and configure it correctly, best tip i can give, for the software deploying share. [wpkg] path

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

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 for the suggestions! > The latter is easiest to deal with, replace it with a CNAME in the AD dns. I did the CNAME, but when I remove the netbios alias I can see the shares list when accessing \\aliasname, but then I'm not allowed into any of them. I tried rebooting the client but same result, and I also don't see anything in the logs :( > The first will require a bit more

Sorry all, I think I attached the wrong files. Apologies for the noise. Correct files attached. again .. these are from the logfile on the server and were in the log file named 192.168.168.13.log 192.168.168.13 is the IP address of the test client orgonon that I have set up for this. I have cut two sections from the log and they start at the same point and seem to be the same until line 162;

>> >> This is my nsswitch file: >> >> >> passwd: files ldap compat winbind >> group: files ldap compat winbind >> shadow: files ldap compat > > Do you have anything that needs to connect via LDAP ? > If you have what it is it ? > I would remove 'ldap' > > 'files' and 'compat' basically

Are there any logs on the client or server at a higher log level? Andrew Bartlett On Wed, 2020-05-20 at 12:39 +1200, Grant Petersen via samba wrote: > I forgot to mention that using the smbclient option > > -A /etc/cred/authfile > > behaves the same way as attempting to manually enter the password on > the command line; failing in 4.12.2 and working in 4.11.0 > >

Dear all, I experience now a strange bug with Samba 4.1.11 : When I define a fixed-name as logon script in smb.conf, it works : logon script = employee.bat But if I try either %g.bat or %G.bat, or even "%G.bat", it doesn't work : * logon script = %g.bat * logon script = %G.bat * logon script = "%G.bat" In the logs, there was a message showing that Samba was

Hi, Some users are experiencing problems working with files in Windows and Samba shares within engineering applications. The sequence is as follows: A user opens a file, e.g. a drawing, inside an application. The user works fine for a while, but suddenly it cannot edit the file anymore. The only way to continue working is closing and opening the file again, like if the session had expired and a