similar to: Duplicate nobody pid entries from smbstatus

On 9/27/19 1:32 PM, Rowland penny via samba wrote: ....snippity... > I repeat, smbclient never had anything to do with network browsing, so > it is unlikely to have anything to do with Network Discovery. Perhaps > you are thinking of libsmbclient ? this can be used by other packages to > provide network browsing. > > You could always code up what you require and propose it as

Hello, I've recently set up Samba (4.12.3) on Arch Linux as the target for Time Machine backups for a couple of Macs. Shortly thereafter I started seeing OOMs whenever a backup would start. I stumbled upon disabling encryption on the server (i.e. changing "smb encrypt" from "required" to "off") to prevent this issue. After further digging, I'm able to

Dear all, Le 07.09.2015 à 15:52, soonerdave a écrit : > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet support > except in the current 4.3 release candidate. I suspect for now disabling > SMB2/3 on the Windows 10 client is your best, if not ideal, option. > > Instructions for doing.this can be found > here: https://support.microsoft.com/en-us/kb/2696547

Il 19/02/20 10:22, Rowland penny via samba ha scritto: > On 19/02/2020 08:05, Roberto Tagliaferri - Tosnet srl via samba wrote: >> Sorry for the english :) >> >> Good morning, i've a little network with samba 4.2 on centos 6, NT style >> domain and win7 client. > > Excuse me, but do you not believe in updating things ? > > Samba 4.2.x went EOL at the end

01.04.2024 13:56, Jones Syue ???: >> I can't say for sure but I *think* each time the client is windows server 2012. > > Looks good :) If run this script[1] to test multiple dialects, found only > SMB3_00 and SMB3_02 has this "(sign_algo_id=1)", and per doc[2] it could > be happend with ws2012 and ws2012r2. This *is* 2012 r2. The protocol version it negotiates is

On 9/27/19 1:39 PM, Jeremy Allison via samba wrote: > On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you

On 9/27/19 5:38 PM, Jeremy Allison wrote: > On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are

Hi, we have a situation where access to a share on some Netapp box fails with “client max protocol” set to SMB3_11 (or unset): protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE With a protocol max set to SMB3_10 or SMB3_02 the login prompt is reached and subsequent file access is succeeds: negotiated dialect[SMB3_00] against server[192.168.42.42] got

Hello, I'm using the latest git 4.2.0 samba version (4.2.0rc4-GIT-93b73bf, to get latest vfs_fruit module). I noticed the following strange behavior with OSX clients (10.10.1, 10.10.2 beta): When they connect using either smb 3.0 or 2.1 (verified on the server with `smbstatus` and the `version` column `SMB3_00` or `SMB2_10` respectively), symbolic links pointing at non existent files are not

Hi! I have a Samba server version 4.1.11 running on Ubuntu Server 14.04. I cannot connect from Windows 10 (but I can from Windows 7). The server and the clients are not on the same LAN. The error message given by Windows is that the server is online but not responding. However the Samba logs say otherwise. I have attached the logs for a failed connection attempt from Windows 10, and those for

Dear Rowland, Thanks a lot for your anwswer ! Le 2017-10-17 20:16, Rowland Penny via samba a écrit : > On Tue, 17 Oct 2017 19:31:17 +0200 > "Denis BUCHER via samba" <samba at lists.samba.org> wrote: >> Le 07.09.2015 à 15:52, soonerdave a écrit : >> > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet >> > support except in the

Hi, We have 5 Samba domain controllers, and 4 file servers. All are 4.2.10-Debian. Our file servers have been working fine until recently (on the 26th), when suddenly access to the \\users.store.example.com\user share (hostname p-cats) became extremely slow. Access to other shares on other machines is fine, and users is 128G total (smaller than other shares). The machine isn't under

On 9/27/19 1:39 PM, Jeremy Allison wrote: > On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are

Hi there I'm having some troubles with Shadow Copy2 & zfs Snapshots. I have hourly and daily snapshots. If I use the following settings it works (but omits daily snapshots): vfs objects = shadow_copy2 shadow:snapdir = .zfs/snapshot shadow:sort = desc shadow:localtime = yes shadow:format = easysnap-hourly_%Y-%m-%d-%H-%M-UTC However when I try to use the BRE with the prefix,

I am running samba on arch linux and I cant browse the shares I get prompted for password over and over. I see this in my logs [2016/10/10 17:14:50.128711, 1] ../source3/librpc/crypto/gse.c:497(gse_get_server_auth_token) gss_accept_sec_context failed with [ Miscellaneous failure (see text): Failed to find cifs/rimfire.hebe.us at HEBE.US(kvno 2) in keytab MEMORY:cifs_srv_keytab

OS platform: FreeBSD 10.1-RELEASE-p25 Filesystem: ZFS Samba version: upgraded from 4.1.17 to 4.1.22 Problem: I have been using the shadow_copy2 and zfsacl VFS modules to enable access control and the Previous Versions feature for Windows clients. With /usr/local/etc/smb4.conf configured this way (excerpt): vfs objects = shadow_copy2 zfsacl shadow:snapdir = .zfs/snapshot

Hi! Setup: Samba version 4.5.12-Debian. smb.conf: [global] security = USER server role = standalone server log file = /var/log/samba/log.%m log level = 3 max log size = 1000 panic action = /usr/share/samba/panic-action %d map to guest = Bad User passdb backend = tdbsam username map = /etc/samba/usersgroups.map usershare path = disable spoolss = Yes load printers = No printcap name = /dev/null

On 2/17/2016 5:00 AM, Rowland penny wrote: > On 17/02/16 00:03, Ian wrote: >> I've recently attempted to migrate some windows server files over to >> samba 4 hosted on a FreeNAS server. >> >> Using robocopy with the /copyall switch, I expected everything, >> including ACL's and ownership information to transfer over. For the >> most part they have.

Hi, windows 7 supports smb3. If centos's samba server suport smb3, how to make windows 10 support smb3 too? Thanks! Regards Andrew At 2019-09-13 15:47:34, "John Hodrien" <J.H.Hodrien at leeds.ac.uk> wrote: >On Thu, 12 Sep 2019, me at tdiehl.org wrote: > >> Why? This is NOT necessary for win 10 to work. I do not even know if it will >> work with

Hi Jeremy, Here's the log with log level 10: https://pastebin.com/0EAuz2B8 The location of the shared folder: /pool/shadowtest The location of the snapshots: /pool/shadowtest/.zfs/snapshot Here are how snapshots are named: autosnap_2019-09-01_13:29:01_daily autosnap_2019-09-01_13:29:01_hourly autosnap_2019-09-01_13:44:09_frequently And this is currently in my smb.conf file: [shadowtest]