similar to: SMB2 Negotiate Request

Hello, on our servers we have shares with no authentication required (no DC, security = share, guest ok = yes). Worked fine for years, but now with Samba 3.5.4, when I enable smb2, Windows 7 clients can not connect anymore to these shares. Looking at the logs, I can see : [...] [2010/08/25 10:13:08.058358, 3] auth/auth_sam.c:399(check_sam_security) check_sam_security: Couldn't find

Hi Samba list! I was very excited that SMB2 is finally working with samba 3.6.0 - great job!! I just know that SMB2 has a smaller command set compared to SMB1 and this, beside many other rebuilds of the code makes it faster As I am completely new to the file transfer protocol world, I want to ask a few basic things: - is Samba backward compatible ... xp can't use SMB2 as far as I

Hi all, At the moment we are running Debian squeeze with stock samba 3.5.6. and are testing some new samba installations from ubuntu 12.04, centos 6.4 and debian wheezy. All running in a VM on a XenServer. The samba servers are member of a 2008R2 domain, using smb1 protocol all are running fine and we get a constant 90MB/s (big file transfer) on our 1GB network. We would like to enable smb2

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

I have a client that recently upgraded from Win XP to Win 7. They were seeing odd slowdowns and poor performance, so we upgraded to Samba 3.5.6 and enabled win 7 support "max protocol = SMB2". They contacted me this morning with a report of more strange behavior, names the inability to access newly created folders with the message "file is too large for file system". There

Greetings list, I just upgraded to samba 3.6.0 trying SMB2. Though Windows 2008 R2 can work with SMB2 shares just fine, I'm unable to access SMB2 shares with mount.cifs or smbclient, even with "-m smb2" specified -- I get this "Unrecognised protocol level smb2", whereas smbclient comes with samba-client-3.6.0-63.1.rpm. So is this supported yet (from client side) or I

Good morning, folks. I've been driving myself to distraction trying to test out SMB2 performance under Linux. I see that the Samba on RHEL 5 is relatively old, I'm dealing with an upstream NetApp fileserver that is configured for SMB2, so I've got clients to test. The Samba on RHEL 5 is relatively old, 3.0.33, with samba3x-3.5.4 alternatively available, and cifs-utils-* available

Hi I've a Windows 2008 R1 connected to a share on a samba 3.5.6 (this samba is a domain member of a samba pdc). All work fine. I've enabled "max protocol = smb2" : i can access the share but when it was impossible to rename a new directory named "New Folder" on the share (created by Windows new folder menu). I've the error : init_smb_request: invalid wct

hi All, We have a glusterfs cluster with 5 nodes on Ubuntu 12.04 amd64. We use this smb.conf: [global] socket options = IPTOS_THROUGHPUT TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=131072 SO_RCVBUF=131072 read raw = yes server string = %h write raw = yes #oplocks = yes max xmit = 131072 dead time = 15 getwd cache = yes use sendfile=yes block size = 131072 load printers = no aio read size

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

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

Andreas, On Thu, Aug 24, 2017 at 03:37:07PM +0200, awl1 via samba wrote: > Before I follow your advice to move this whole issue/topic to the > samba-technical alias and start over there with a clean description of the > scenario and the findings, I have two simple questions: > > 1) I plan to use a new, reproducible test scenario with 2000 random small > files with a file length

Hi, A number of students are unable to connect to our print server from their Windows 10 client laptop without entering a user/pass. More precisely: If you try to connect manually to \\IP it says "Username or password incorrect" and prompts to enter a username/password. Despite the server setting to map all users to guest (see further down). I did a packet dump and the client pc

Hello Ivan, 'FastCopy' has an option to revise max I/O size and works for SMB :) it is a tool for file transferring and could be installed to win10, download here: https://fastcopy.jp/ This is an example for writing, a job would write a file named '1GB.img' from a local disk 'H:' to a remote SMB mounted net disk 'Z:', open 'FastCopy' tool and specify

I have a classic NT4 domain with the PDC also the wins server. With the recent ransomware problem, we're trying to remove SMB1 and below protocols. However when I do this, the browse list is gone. Hosts can access properly the shares, but they have to know exactly \\machine\share in order to to connect. The same thing from a linux client: smbclient -L {PDC} -m SMB2 Domain=[{MYDOMAIN}]

I am trying to setup a SAMBA server using 3.5.0rc2 to test SMB2. Without using SMB2, my windows 7 was able to browse the public share listed on the server anonymously. However, when SMB2 is enabled, a network error message is always popped up when I try to browse the samba server from Win 7. I have looked at the trace. It seemed to me that Win 7 had troubles accessing wkssvc, srvsvc, etc.

On Fri, Aug 18, 2023 at 04:25:28PM +0000, Jones Syue ??? wrote: >Hello Ivan, > >'FastCopy' has an option to revise max I/O size and works for SMB :) >it is a tool for file transferring and could be installed to win10, >download here: https://fastcopy.jp/ > >This is an example for writing, a job would write a file named '1GB.img' >from a local disk

Hi forks: I've been testing SMB2 with samba 3.6.4 performance these days, and I find a weird benchmark that SMB2 write performance is slower than SMB1 in 10Gb ethernet network. Server ----------------------- Linux: Redhat Enterprise 6.1 x64 Kernel: 2.6.31 x86_64 Samba: 3.6.4 (almost using the default configuration) Network: Chelsio T4 T420-SO-CR 10GbE network adapter RAID: Adaptec 51645 RAID

On Fri, Jan 23, 2015 at 01:20:05PM -0800, Jeremy Allison wrote: > On Fri, Jan 23, 2015 at 10:16:34PM +0100, Ralph B?hme wrote: > > On Fri, Jan 23, 2015 at 01:08:31PM -0800, Jeremy Allison wrote: > > > On Fri, Jan 23, 2015 at 10:05:44PM +0100, Markus Doits wrote: > > > > > > > > On 23.01.15 19:57, Miguel Medalha wrote: > > > > > I am using

Hello, We are running some legacy software that instructs us to, via Windows registry settings, disable all oplocks and SMB2 entirely on each Windows workstation that connects to the Samba share where the software is hosted. The software maintainers give dire warners of corruption, etc., if oplocks (and SMB2) are left enabled. We?ve run this software off of a Samba share for 20 years and have