search for: msmb2

...hasing up the performance issues I posted about earlier which may be caused by my Linux clients defaulting to SMB1 (via gvfsd-smb) while Windows happily negotiates SMB2 with the servers. If I restrict the servers to SMB2, gvfs can't connect, while smbclient on the console works fine if I pass -mSMB2. I can't see anything in https://git.gnome.org/browse/gvfs/tree/daemon/gvfsbackendsmb.c that would restrict the protocol version, either. Any ideas? Thanks, Adam

...ult everything ok. uhh. So what happend then... Now i tested again but typed a wrong password.. And,, yes, it was a typo in my password, .. (oeps) sorry for the noise. Now bit more testing, all with a wrong password. A samba 4.5.12 give this output smbclient -L $(hostname -f) -Uadministrator -msmb2 Enter administrator's password: session setup failed: NT_STATUS_LOGON_FAILURE A 4.6.6 however.. smbclient -L $(hostname -f) -Uadministrator -m smb2 NTDOM\administrator's password: Kinit for administrator at REALM to access member1.internal.domain.tld failed: Preauthentication failed sess...

Hi, We are facing difficulties writing to Alternate Data Streams (ADS) on a Windows CIFS mount on CentOS/RHEL Linux. Steps followed on both machine: -------------------------------------------- On RHEL(cifs.ko version: 1.68) 1. Created sample.txt file using vim with come content inside the Windows CIFS share mounted on linux. 2. Then wrote some content with “vim

On Fri, Nov 03, 2017 at 01:54:10PM +0100, Dr. Peer-Joachim Koch via samba wrote: > Hi Micha, > > no, I have to this. I'm normally just check what smbstatus shows: > > 33837   BGC\pkoch    users        XXX (ipv4:XXX:51118)    SMB2_10 > > Bye the way - 45 MB/s is not so bad, I just wanted to know if it's > possible to get 90MB/s or at 10G a little bit more. >

Hai, Im missing at least one of these on the PC. Primary Dns Suffix  . . . . . . . :  DNS suffix search list       : Are you using DHCP server or static ips on the pc. Thats where this problem is, i dont think its the server (samba) setup. @Rowland, > smbclient -L localhost -U% -d3 Wont work, due to bug in smbclient thats tries smb1 first ( or something like that ) I suggest test like

Hai, What happens if you add to the mount the option -mSMB2 If that does not work, tell the exact running OS, RH (NR) , Centos (NR) And samba version. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Krishna G via samba > Verzonden: woensdag 13 februari 2019 15:41 > Aan:...

...ac-sha1-96 rc4-hmac des-cbc-crc des-cbc-md5 default_tkt_enctypes = aes128-cts-hmac-sha1-96 aes256-cts-hmac-sha1-96 rc4-hmac des-cbc-crc des-cbc-md5 permitted_enctypes = aes128-cts-hmac-sha1-96 aes256-cts-hmac-sha1-96 rc4-hmac des-cbc-crc des-cbc-md5 And test again with smbclient -mSMB2 \\server.domain.tld\share That should do the trick. If you google a bit more for squid and the samba list, you see more of things i posted. You can use that also. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Alex &...

smbclient/mount.cifs stopped working when connecting to a Windows 7 server. The Windows machine is not part of a domain and smbclient is authenticating with one of its local accounts. Upon uninstalling the January Windows security patch (KB4480970) from the server, everything works again. The tests below are with a custom compiled copy of the latest smbclient (4.9.4) for troubleshooting purposes

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...

...the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet being defined for the SMB2 or SMB3 protocols. The second way to select SMB2 or SMB3 connections is to set the "...