similar to: smbstatus -- protocol and feature information

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 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 Everyone, My doubts are for Samba4.1 performance related enhancements (SMB2.1 / SMB3.0). My experimental samba server hardware is running 4.1 version. Want to improve robocopy WRITE throughput from a two samba client machines (win7 or win8 or server2012 x86 servers). Someone please advice me how can I use SMB2.1 or SMB3.0 capabilities to improve WRITE throughput. I tried samba4.1

Trying to get a linux samba file server using samba 4.0.3 (compiled on the machine) running on ubuntu 3.8rc6 kernel to share out and negotiate with a linux client running the same kernel and smbd compiled from 4.0.3 samba source. Using wireshark to view the negotiations, I only see NT LM 0.12 (SMB v. 1). Tried forcing the file server via "min protocol = SMB2" in the

Hi all, Behavior described in this email is identical whether I try to mount at 192.168.100.2, my desktop and location of my Samba server, or 192.168.100.239, my laptop that is remote from my desktop with Samba server... I want to mount a share defined on my Linux desktop, on my Linux laptop, as a better alternative than sshfs or NFS. I want this mount to happen as version 2.x or 3.x, not as

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

Sorry for a rather 'unifornative' subject, but i've little o no clue on this. I'm using at work 'pam_mount' with a rather standard configuration to mount via CIFS/SMB user's home directory, from a samba AD member server. This configuration is a bit 'old' (mint sonya, AKA Ubuntu 16.04 as a client, so samba 4.3; debian and samba 4.8 as a server), but work

Hi, I am running samba-4.1.4 on my Fedora OS. I have provided the "client max protocol = SMB3" and "server max protocol = SMB3" parameters in smb.conf file I'm able to get only SMB2.1 packets using wireshark after fileshare access from my windows 7 machine. And not SMB3 packets. SMB2->NegotiateProtocol Response 0x0202 0x0210 Samba-4.1.4 is supporting SMB3 also. So

hi Michael, Sorry for taking so long to reply, I just get back on vacation. Your advice is very helpful. Our purpose is no IO interrupted with Window 7 cifs client accessing the shared folder when virtual IP taken over by another node. SMB3.0 or newer protocol do meet that demand, but Window 7 cifs client only supports SMB2.1 protocol and previous versions. So we need implement a

> > Unless you upload a network capture of you mounting and doing the ls -lR > on the client it's hard to say what really goes on. I understand you > might not want to make it public.. but if you do > This is the last thing I'll try after I've exhausted all the other options. How are you mounting your share (which mount options)? > Something weird is going on with

Dear all, I tried to do a backport of 'ssl_prefer_server_ciphers' (http://hg.dovecot.org/dovecot-2.2/rev/897484f45a87/) to Dovecot 2.1 (namely the Debian version of Dovecot) and wanted to ask if there is any chance to integrate this feature into Dovecot 2.1 'upstream' as well. As the code structure changed quite a bit, I am not sure if my patch is complete. I tested it with pop3s

Samba Team Releases Samba 4.0 ============================= December 11th 2012. The Samba Team is proud to announce the release of Samba 4.0, a major new release of the award-winning Free Software file, print and authentication server suite for Microsoft Windows clients. The First Free Software Active Directory Compatible Server

Samba Team Releases Samba 4.0 ============================= December 11th 2012. The Samba Team is proud to announce the release of Samba 4.0, a major new release of the award-winning Free Software file, print and authentication server suite for Microsoft Windows clients. The First Free Software Active Directory Compatible Server

Hello xen-users ! I am coming for help concerning the just released 4.0 version. Install has worked rather well on my Debian Lenny. I have just had a few bugs for which I have found the answer looking around on this list. I have created a Debian Lenny domU which boots up just fine. The only problem is that I am unable to get a console prompt when using "xm console nameofdomU". I do see

I did not set max protocol to SMB2 in smb.cnf, I don't want to force SMB2 selection if SMB3 can be used by a client. The machine is a Windows 7, so is SMB2 compliant. Le 22/07/2019 ? 11:44, Gaiseric Vandal via samba a ?crit?: > I would guess that changing the min protocol does not affect existing > connections unless you were to restart samba. > > Is the max protocol set to at

hello, We've just migrated our samba PDC v3.4.5 (FreeBSD) to samba v4.1.17 (Debian wheezy) with samba4 classic upgrade. Most of the stations works fine. When I try to register a Windows 2012 as a member into the new Samba AD, Windows 2012 says it cannot authenticate the user used for registering the new host into the domain. Of course, this user have admin privileges into the AD target

Hello, we frequently face locking issues with office applications and documents on samba shares. The office applications claim that the document is locked and hence no write access is possible. I can check on the samba server that there is no concurrent access/locking from other computers or users. It looks like the same user holds some lock and is denied to access the document because it?s

On 13/05/2019 17:05, Steve Litt via samba wrote: > Hi all, > > Behavior described in this email is identical whether I try to mount at > 192.168.100.2, my desktop and location of my Samba server, or > 192.168.100.239, my laptop that is remote from my desktop with Samba > server... > > I want to mount a share defined on my Linux desktop, on my Linux > laptop, as a better

Hello, I set client min protocol = SMB2 in my smb.cnf But I see some clients still connecting in NT1 (smbstatus) : smbstatus -p Mon Jul 22 11:39:36 2019 Samba version 4.8.3 PID???? Username???? Group Machine?????????????????????????????????? Protocol Version Encryption?????????? Signing

Hello I try to implement pam_mount and I have errors. When I login to ubuntu desktop client I have an error with "mounting read-only" but if later to logon on domain I go to the files application and map the resource shares manually, work fine. Attach the syslog trace: Sep 24 10:22:13 ubuntucliente lightdm[708]: (pam_mount.c:365): pam_mount 2.14: entering auth stage Sep 24 10:22:20