similar to: smbstatus information and layout

Hi Marc, > >Is there any tool like smbstatus that shows which protocol version (and > >possibly which features) a client is using in a connection? (Feature in > >the sense of 'using encryption' for example). > You can't see this in smbstatus or somewhere. A network trace would > show it. However, we had this question twice in the past and someone > had a

Hi all, But I do see the protocol version against each client connection in smbstatus output as below, =============================================================================== Samba version 4.2.0rc5 PID Username Group Machine Protocol Version ------------------------------------------------------------------------------ 10350 -1 -1

Hi Jeremy, > > Do you think requesting this as a feature for smbstatus in the Samba bug > > tracker does make sense? > > Yes please. We certainly need a 'protocol' field somewhere > in the smbstatus output I think. done. https://bugzilla.samba.org/show_bug.cgi?id=11262 -- Adi

Hi, I am trying to figure out what features in terms of protocols (SMB/CIFS, SMB2, SMB2.1, SMB3) a client uses when being connected to a Samba server (v4.1.17). Is there any tool like smbstatus that shows which protocol version (and possibly which features) a client is using in a connection? (Feature in the sense of 'using encryption' for example). Thanks, Adi

Hi, I just installed Samba 3.0.4 on a Solaris 2.6 server. I had no problem compiling, intalling and configuring it, and everything seems to go OK. People can connect to all the configured shares without any problem. But I have some problems when getting server status either via SWAT/STATUS or using smbstatus: First, in the "Client" field of the SWAT/STATUS report I have problems

I have a Samba server configured as PDC for ~100 computers. It's version 3.0.24 running on Debian Etch (distribution package). I want to write a tool for user logon/logoff tracking. Because parsing log files is hard job (windows frequently disconnets or connects during user session or etc.) I decide to use smbstatus output which seem to be reliable. So I run smbstatus binary every 10

Hallo, in 3.0.8pre2 the smbstatus command always shows connections _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for showing locks only: test2 # smbstatus --help Usage: [OPTION...] -p, --processes Show processes only -v, --verbose Be verbose -L, --locks

Hi Team, While building smbd and smbstatus statically I am getting below error (using make). *ERROR: source source3/smbd/notify_msg.c is in more than one subsystem of target 'smbstatus': ['smbd_base.objlist', 'smbstatus.objlist']* *Environment Details:* Machine: Ubuntu 18.04 Samba Version: 4.11.6 *My Makefile excerpt:* ./configure --with-logfilebase=/var/log \

I use a lot of "force user" and "force group" directives on various shares. With smbstatus of Samba 2 I could always verify with a glance what uid and gid a particular service is being accessed as, with Samba 3 you can't. I'd REALLY like to see that come back to smbstatus. Here's a real world example of my complaint... Samba 2 smbstatus output... Samba version

I am running Samba version 2.0.6 on Solaris 2.6. When I run smbstatus, it coredumps. Here is some detailed information that may help in killing this bug. This is a run of smbstatus where it coredumps, and afterwards, a gdb session. root@grads:/depot/samba-2.0.6/bin 174# ./smbstatus Samba version 2.0.6 Service uid gid pid machine ----------------------------------------------

Somemore information regarding the smbstatus error. The sigbus error is occuring where I noted below. I now have data values to go along with the location. The SIGBUS generating bit is "entry_scanner_p->e.pid" which looks to be in an unaccessable area of memory. Looking back through the code, I find a couple of bizarities. For example file_scanner_p->num_share_mode_entries

Dear list, I have just upgraded our main Samba server from version 2.2.8a to 3.0.6. It seems to be working fine except for 2 things: 1. when I use smbstatus(or swat/status) only some of the connections are listed and then smbstatus hangs forever(swat comes back after a while, but only with some of the connections) Have any of you experienced something similar ? How can I debug

-------- Original Message -------- Subject: smbstatus getting a SIGBUS error Date: Thu, 08 Jun 2000 13:52:13 +0700 From: Arnold Troeger <stssart@bkk.unocal.com> To: samba-bugs@samba.org CC: arnold.troeger@bkk.unocal.com I'm running Samba 2.0.7 and have been having a few problems with it. Just to keep things focused, I'll stick with smbstatus as this one has been the longest lasting

I am trying to use the "shared mem size" parameter in Samba 2.0.4b, but the size reported by smbstatus does not match the value I am using. Without the parameter, the default is 1MB, and the size reported by smbstatus is indeed 1048576. However, when I set the value of "shared mem size" to 5242880 (5MB), smbstatus says 879608. Is smbstatus not reporting the actual size, or

Hello list, I'm running a samba 3.5.3 CTDB cluster, found the output is different Q1: What does the "0:" mean in pid column? There was no such stuff in non-CTDB smbstatus output. <snip> samba_01:~ # smbstatus -S 2>/dev/null Service pid machine Connected at ------------------------------------------------------- ben 0:21363 samba Mon Oct

Greetings, After recently upgrading Samba from 2.0.7 to 2.2.2 on my Solaris Unix servers, I have problems running command 'smbstatus'. When I run smbstatus as root, it correctly displays connection information for users who've mapped network drives to server shares. However, when I run smbstatus as non-root, instead of displaying connection information, it issues the message

Hello, If I use Samba as a PDC, what does the output from "smbstatus" mean? Will all logged in users be displayed at all times when I do "smbstatus -b"? The reason I ask is that users who are logged in occasionally disappear from the output of smbstatus, even though they are still logged in. Is this to be expected? regards, David

Hi, Despite looking at https://www.samba.org/samba/docs/current/man-html/smbstatus.1.html and "man smbstatus", I don't see how to know the full list of possible exit status for command smbstatus. All I could test brings an exit code of 0 in most cases and 255 if option -s is an unreadable file. Is there a man page that lists all possible return values? Regards Santiago

Hi we use samba 3.0.25a on FreeBSD 6.2. We use a 'multiple' approach on our server: we have a smbd daemon for the Users section (with its configuration file) and a smbd daemon for the Groups section (with another configuration file). We would like to discriminate the locks and the other details for these two daemons: we would like to have a report for smbd-users and a report for

Arnold Troeger wrote: > I'm running Samba 2.0.7 on a heavily patched Solaris 2.6 machine. For > about 3 minutes after I restart smb and nmb I can run smbstatus (as > root) with no trouble. After that though smbstatus starts segfaulting. > It shows the shares properly, but the locks and memory usage messages do > not appear. Have I found a bug in smbstatus? > > Thanks