similar to: Duplicate nobody pid entries from smbstatus

Displaying 20 results from an estimated 900 matches similar to: "Duplicate nobody pid entries from smbstatus"

2019 Sep 27
5
Browsing shares of a server
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
2020 Jun 19
1
Apparent large memory leak with encryption + SMB3_00 or SMB3_02
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
2017 Oct 17
2
Fwd: Cannot connect to Samba share (4.1.11) from Windows 10
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
2020 Feb 21
2
preexec with win 10
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
2024 Apr 01
1
Bad SMB2 (sign_algo_id=1) signature for message
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
2019 Sep 27
1
Browsing shares of a server
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
2019 Sep 27
1
Browsing shares of a server
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
2019 Feb 13
2
smbclient error talking to Netapp with SMB 3.11 / Samba 4.7.11
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
2015 Jan 05
4
Symbolic links not visible on osx 10.10
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
2015 Sep 06
4
Fwd: Cannot connect to Samba share (4.1.11) from Windows 10
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
2017 Oct 18
1
Fwd: Cannot connect to Samba share (4.1.11) from Windows 10
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
2016 Aug 31
1
Sudden unexplained slowness on share (caused by duplicate UID?)
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
2019 Oct 03
2
Browsing shares of a server
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
2016 Oct 10
1
unable to browse shares
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
2019 Sep 13
2
why windows 10 can't access centos samba
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
2018 Mar 02
2
Smbstatus shows many nobody users from win10 pc's
I know more people posted about this , but i see no solution. smbstatus gives over 100 nobody users The windows 10 pc is doing nothing, just a reboot ( and logon ) , than this happens: Samba version 4.6.2 Centos 7. PID Username Group Machine Protocol Version Encryption Signing
2017 Mar 01
2
[Announce] Samba 4.4.10 Available for Download
====================================================== "In a time of destruction, create something." Maxine Hong Kingston ====================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.4. Please note that this will likely be the last maintenance release of the Samba 4.4 release branch. Major
2017 Mar 01
2
[Announce] Samba 4.4.10 Available for Download
====================================================== "In a time of destruction, create something." Maxine Hong Kingston ====================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.4. Please note that this will likely be the last maintenance release of the Samba 4.4 release branch. Major
2019 May 01
0
Windows clients require reboot once a day in order to access mapped drives
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
2012 May 21
1
NFS - Strage Problem
Hi Dear List, i am experiencing strange problem with NFS, they is CentOS 6.2 x86_64 machines. One CentOS is sharing two directories (following) /etc 192.168.0.41(rw,sync,no_root_squash) /var/named/master 192.168.0.41(rw,sync,no_root_squash) nfs is started on server side there are proper entries in fstab at client side for both shares. however server is able to mount "/etc" alright