similar to: Samba4 server not visible browsing network listed machines

Good afternoon, I've this issue: I have followed the instructions in this thread but, when I try to add quota.ldif I receive this error: Unable to find attribute quota in the schema ERR: (Invalid attribute syntax) "objectclass_attrs: attribute 'mayContain' on entry 'CN=systemQuotas,CN=Schema,CN=Configuration,DC=my_domain,DC=it' contains at least one invalid

Good afternoon, I have installed a fileserver with samba4 environment. This is configured to works as AD-DC even if I only use it as a fileserver (at the moment). All seems to works fine but, every 10 minutes, the log print these messages: Mar 22 11:53:17 fileserver samba[1946]: [2016/03/22 11:53:17.557554, 0] ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) Mar 22 11:53:17 fileserver

Good afternoon, I have a problem with rsync when I sync my virtual machines files between a Linux box and a NAS. This is the output: rsync: failed to set times on "/mnt/backup/Windows Server 2003/.Windows Server 2003.nvram.GSfBdw": No such file or directory(2) rsync: failed to set times on "/mnt/backup/Windows Server 2003/.Windows Server 2003.vmdk.0ykiw7": No such file or

Hi, I run Samba 4.2.3 on a fileserver since 2015 without any problem even if in the log file I read "NTLMSSP NTLM2 packet check failed due to invalid signature" several times a day. In my network are presents windows 7, 10, and some old XP machine. Yesterday evening, for the very first time, my server chrashes and I have to restart it. The samba error reported is: internal error:

On 22/03/16 14:38, Daniele Manfredi wrote: > Il 22/03/2016 14.45, Rowland penny ha scritto: >> On 22/03/16 13:35, Daniele Manfredi wrote: >>> Good afternoon, >>> I have installed a fileserver with samba4 environment. >>> This is configured to works as AD-DC even if I only use it as a >>> fileserver (at the moment). >>> All seems to works fine

Hai, ... > > As I said, where is the fault, is it something that Windows 10 is or > isn't doing, or is it Samba ? > > Well, we cannot change Windows, so on that basis, I think you should > make a Samba bug report and let it work through the system. > > Rowland Well, yes, we can change windows, by allowing/disallowing SMB1. Which might help in detecting whats

Package: logcheck Version: 1.3.3 Severity: normal After upgrading to the latest logcheck, I've noticed that some local rules I have written no longer filter out the logs properly. I've been able to correlate the non-matching to the presence of the '/' (slash) character or '[' (left bracket) in the string that the ".*" pattern ought to match. For instance, I

Since upgrading to Ubuuntu 16.04 LTS from 14.04 LTS, I cannot see either my Windows PC or any of three Linux-based NAS in either "Network" or "Windows Network". Both windows have no icons. After the upgrade, I did apt-get update and apt-get install samba and apt-get install winbind My Windows 7 Ultimate PC can see the Linux PC and the three NAS without

On 09/05/2020 10:34, Lorenzo Milesi via samba wrote: > 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

Mason, You can set these also on the share. Win7 and10 client min protocol = SMB2 client max protocol = SMB3 The one for the scanner, client min protocol = NT1 client max protocol = SMB2 Part of my smbstatus -a: PID Username Group Machine Protocol Version Encryption Signing 27316 root root

Hai Sonic, > -----Oorspronkelijk bericht----- > Van: Sonic [mailto:sonicsmith at gmail.com] > Verzonden: woensdag 1 mei 2019 14:51 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] Windows clients require reboot once a > day in order to access mapped drives > > On Wed, May 1, 2019 at 2:24 AM L.P.H. van Belle via samba > <samba at

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 =

Hi people: I recently installed a Samba 4.0.3 server in a small company. Users are still working as a workgroup -not as a NT nor ADS domain yet- using Windows XP and Windows 7. Everything seems to be working fine except for one thing: Windows clients can't find the samba server from the Windows Network Places (My Network Places -> Entire Network -> ...). It just appears the rest of

On 21/11/15 18:33, Andrey Repin wrote: > Greetings, Viktor Trojanovic! > >>> Is there at last a solution? I've only found questions, in the list, and on >>> the network. >>> >>> The issue is that DC built on Samba4 does not report to network browsers >>> neither it is participating in election to become browser itself. >>>

On 22/11/15 09:14, Andrey Repin wrote: > Greetings, Rowland Penny! > >>>>> Is there at last a solution? I've only found questions, in the list, and on >>>>> the network. >>>>> >>>>> The issue is that DC built on Samba4 does not report to network browsers >>>>> neither it is participating in election to become

On 29/12/15 16:32, Stefan G. Weichinger wrote: > I have to add a brand new fedora 23 server with samba 4.3.3 to an > existing Windows ADS domain. > > The join is OK: > > # net ads testjoin > Join is OK > > I use winbind as I still have to learn about sssd (and I am unsure which > one to prefer). > > config (workgroup and realm edited): > > [global] >

Greetings, All! Is there at last a solution? I've only found questions, in the list, and on the network. The issue is that DC built on Samba4 does not report to network browsers neither it is participating in election to become browser itself. Consequently, it is not visible in the neighborhood neither on Windows, nor on Linux. I've managed to force a second Linux host (member server)

On 29/12/15 17:30, Stefan G. Weichinger wrote: > Am 2015-12-29 um 18:05 schrieb Rowland penny: >> On 29/12/15 16:32, Stefan G. Weichinger wrote: >>> I have to add a brand new fedora 23 server with samba 4.3.3 to an >>> existing Windows ADS domain. >>> >>> The join is OK: >>> >>> # net ads testjoin >>> Join is OK >>>

Am 2015-12-30 um 10:40 schrieb Stefan G. Weichinger: > Thanks a lot for that explanation. > I read it after it started working here yesterday so excuse my late > reply. I never understood it the way you described it above, this would > have helped me with other servers earlier as well. Maybe off topic or another issue, but I add it to this thread as it affects the same server. The

Greetings, Viktor Trojanovic! >> Is there at last a solution? I've only found questions, in the list, and on >> the network. >> >> The issue is that DC built on Samba4 does not report to network browsers >> neither it is participating in election to become browser itself. >> Consequently, it is not visible in the neighborhood neither on Windows, nor on