similar to: Intermittent permission denied when accessing share

Displaying 20 results from an estimated 1000 matches similar to: "Intermittent permission denied when accessing share"

2020 May 08
1
Only domain admins can access shares
I've set up a single server with a DC and fileserver. I've read through all docs and the warnings on the wiki (VERY well done, many thanks to all the contributors) more than once so I hope I haven't missed anything. smb.conf: # Global parameters [global] netbios name = FILESERVER realm = WDC.DOMAIN.IT server role = active directory domain controller
2020 May 18
2
Intermittent permission denied when accessing share
> What OS is this ? Ubuntu 18.04.4 > Can you run the attached script on the DC and copy the output into a > post (sanitised if required) I don't see any attachment. -- Lorenzo Milesi - lorenzo.milesi at yetopen.it YetOpen S.r.l. - https://www.yetopen.it/ Via Salerno 18 - 23900 Lecco - ITALY - Tel +39 0341 220 205 - Fax +39 178 6070 222 Think green - Non stampare questa e-mail
2020 May 18
4
Intermittent permission denied when accessing share
> trying again. here's the output. thanks! Config collected --- 2020-05-18-23:08 ----------- Hostname: fileserver DNS Domain: wdc.mydomain.it Realm: WDC.MYDOMAIN.IT FQDN: fileserver.wdc.mydomain.it ipaddress: 10.0.0.3 ----------- This computer is running Ubuntu 18.04.4 LTS x86_64 ----------- running command : ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc
2020 May 18
2
Intermittent permission denied when accessing share
> You missed that using a DC as a fileserver isn't recommended. It was between the lines of "I followed all the guidelines for doing things correctly in this specific situation" :) > From reading the samba log, it looks like Samba logons are not working, > but ldap connections are. This means Win clients are logging in via LDAP? Can this be related to the inaccessible
2020 May 17
0
Intermittent permission denied when accessing share
On 16/05/2020 16:52, Lorenzo Milesi via samba wrote: > I'm having a weird situation with a freshly installed Samba v4.12.1 compiled from source. This is a single server with DC and fileserver, I followed all the guidelines for doing things correctly in this specific situation and I hope I haven't missed anything. You missed that using a DC as a fileserver isn't recommended. > One
2020 Jun 03
3
get_ea_dos_attribute: Cannot get attribute from EA on file .: Error = No data available
I'm pasting below the output of the debug script you sent me some time ago. Other than this Samba has been compiled with standard options, just ./configure, following the wiki guide with the offered bootstrap file for ubuntu18.04. root at fileserver:~# smbd -b Paths: SBINDIR: /usr/local/samba/sbin BINDIR: /usr/local/samba/bin CONFIGFILE: /usr/local/samba/etc/smb.conf
2020 May 29
2
get_ea_dos_attribute: Cannot get attribute from EA on file .: Error = No data available
Samba 4.12.1, single server with AD+DC on Ubuntu 18.04. Filesystem: /dev/sdb1 on /home type ext4 (rw,relatime,stripe=32750,data=ordered) It all work as expected, but I occasionally get the error in subject which denies access to shares. Restarting Samba will restore functionality. What can be the cause of this problem? Thanks. [2020/05/27 18:24:35.795379, 8]
2019 Jul 02
3
Weird access problem to files
> The latest Samba version is 4.10.6 and there have been numerous updates > since 4.3.11, but you shouldn't be having the problem you have, so lets > start be you posting your smb.conf Thank you very much. Here it is: [global] server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate realm = domain.lan ldap server require strong auth =
2020 May 18
3
Intermittent permission denied when accessing share
> Not sure, but that is the way it looks, just a thought, are you using > sssd ? no, not even installed > Just like a normal share, '[homes]' is a special share that doesn't use > 'path. There used to be something on the wiki about using '[home]' on a > DC, I didn't know it had gone until you mentioned it ;-) So if I use [home] it would be a normal
2020 May 18
2
Intermittent permission denied when accessing share
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
2023 Feb 07
3
Replication between Samba DCs (on different sites)?
On 07/02/2023 18:35, Lorenzo Milesi via samba wrote: > > >> A little more context, manual replication unfortunately doesn't help: > > Last (sorry for the spam, I'm starting to forget things): > > # dig _ldap._tcp.pdc._msdcs.wdc.domain.it srv > > ;; ANSWER SECTION: > _ldap._tcp.pdc._msdcs.wdc.domain.it. 900 IN SRV 0 100 389 dc1.wdc.domain.it. > >
2020 May 09
4
New install of 4.12.1: fileserver not visible when browsing network
I've just deployed an AD DC fileserver with Samba4 but the server itself is not available when browsing network computers from a Windows PC. Is it because of this [1][2] or did I misconfigure it? Thanks my config: # Global parameters [global] netbios name = FILESERVER realm = WDC.MYDOMAIN.IT server role = active directory domain controller server services =
2020 May 08
2
Error changing server IP address: ERROR: Connecting to DNS RPC server
Samba Version 4.12.1 I'm trying to change server IP address from 10.0.0.69 to .3 on a single AD DC running also as fileserver (very small situation). I'm following this [1] guide, I have no interface restrictions in samba or in bind. I stop samba, change IP address, restart bind, start samba, but when I run samba_dnsupdate I get some messages until: 5 DNS updates and 5 DNS deletes
2023 Apr 14
2
Unable to "rejoin" existing DC after upgrade (infamous WERR_FILE_NOT_FOUND)
> That all smells quite similar to what I were seeing > here before, and what someone else were seeing too, > all with 4.17[.4]. This famouse WERR_FILE_NOT_FOUND > error too. We upgraded one more domain, and in the hope to avoid this error, we remained on 4.16. So we deployed a new 4.16.9 DC, joined, everything is fine. Remove the old DC, upgrade OS, install 4.16.10 (which was
2023 Apr 14
2
Unable to "rejoin" existing DC after upgrade (infamous WERR_FILE_NOT_FOUND)
On 14/04/2023 12:13, Lorenzo Milesi via samba wrote: > >> That all smells quite similar to what I were seeing >> here before, and what someone else were seeing too, >> all with 4.17[.4]. This famouse WERR_FILE_NOT_FOUND >> error too. > > We upgraded one more domain, and in the hope to avoid this error, we remained on 4.16. So we deployed a new 4.16.9 DC, joined,
2019 Jul 02
2
Weird access problem to files
> Can I suggest you keep upgrading, Samba 4.3.11 is EOL and I suppose the > version of Ubuntu you are running it on will be as well ;-) It's Ubuntu 16 LTS, so it's supported until 2021. > Probably because that is the old way of doing things ;-) I said that's the old installation, in the new one we remapped all the single user entries to the new ACL from RSAT. So we opened
2020 May 11
2
Unable to access shares by server alias
Hai, Verify dig -x $(hostname -i) Then dig A $(hostname -f) As long as these match any CNAME should work. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: maandag 11 mei 2020 9:21 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Unable to access shares by server
2020 May 22
3
log.samba missing rotation
I know about this param, I configured it and log.smbd, log.nmbd and others are rotated, log.samba is not. ----- Original Message ----- > From: "samba" <samba at lists.samba.org> > To: "Lorenzo Milesi" <maxxer at yetopen.it>, "samba" <samba at lists.samba.org> > Sent: Thursday, May 21, 2020 7:29:04 PM > Subject: Re: [Samba] log.samba
2020 May 18
2
Intermittent permission denied when accessing share
> I would expect to only see that on a machine with the MIT kdc installed, > try this > > apt-get -s remove krb5-kdc > > This will prove one way or other if it is installed and what it wants to > remove along with it, it will not remove anything. Apparently nothing requires it: The following packages were automatically installed and are no longer required:
2023 Mar 08
2
Unable to "rejoin" existing DC after upgrade (infamous WERR_FILE_NOT_FOUND)
08.03.2023 20:09, Fabrizio Rompani via samba ?????: ... > root at landc:~# samba-tool drs showrepl --summary > There are failing connections > Failing outbound connections: > CN=Configuration,DC=domain,DC=lan > Default-First-Site-Name\NEXTCLOUD via RPC > DSA object GUID: 3fa4ff9a-7fdc-4912-ad73-08b98f6bf347 > Last attempt @ Wed Mar 8