similar to: Different "Max Protocol" for different Clients?

Hi, my Vista box does hang if I try to copy an File on an Samba share. - Hanging does happen on both, explorer and CMD. In Explorer it shows up to calculate how long it might take. In CMD nothing happend. - Afterwards Vista refuses to shut down. - Creating an File on the Share and saving it from within notepad does not cause any trouble. - Limiting protocol to lanman2 seems to help

Hi. We have been using samba 3.0.11 for years and now we need to add some win7 machines to our domain. So I test up-to-date Samba versions (3.6.19, 4.1.0 compiled, and Centos today "native" binary package 3.6.something) and with all of them I run into the same problem. I get stuck with protocols when checking XP machines (which works like a charm in 3.0.11 domain) When max protocol is

Headway Research is closed for the Christmas and New Year holidays. Normal work will be resumed Monday January 4, 1999. Your email will receive the appropriate attention upon our return. We wish you a safe and happy holiday season!! *************************************************************************** Headway Research, Inc. |Telephone: 972-272-5431 3713 Forest Lane

Hello, I am trying to figure out how the different values for "max protocol" and "min protocol" (as seen in the smb.conf man page under the "max protocol" section) correlate to the Microsoft jargon for the different logon protocols. Here is what I've determined. Could some please verify this for me? Samba Microsoft CORE

A coworker and I have been doing some performance tuning with Samba 20b4 under Linux 2.0.36 (RedHat 5.2 distribution) on a 100-T network. The protocol is NT1. Two settings are tweaked in particular, "read raw" and "write raw". When both are yes, reading a large file results in 6M/s, but writing is only 2M/s, which is far below writing to an NT server (6M/s). If any of

On 06/03/15 17:35, Tim wrote: > I have to add noise: Provisioning a DC with sernet 4.1.x called NT1 as max default with me. > > > > Am 6. M?rz 2015 18:28:55 MEZ, schrieb James <lingpanda101 at gmail.com>: >> OK. Now I'm really confused. I was not aware of two 'testparm' >> commands. >> Running 'testparm -v' shows correct default values.

I have to add noise: Provisioning a DC with sernet 4.1.x called NT1 as max default with me. Am 6. M?rz 2015 18:28:55 MEZ, schrieb James <lingpanda101 at gmail.com>: >OK. Now I'm really confused. I was not aware of two 'testparm' >commands. >Running 'testparm -v' shows correct default values. So whats the >difference? > > >On 3/6/2015 12:20 PM,

On 06/03/15 17:05, Marc Muehlfeld wrote: > Am 06.03.2015 um 14:56 schrieb Rowland Penny: >>> From 'samba-tool testparm -v' : >>> >>> server max protocol = NT1 >>> >>> BUT 'man smb.conf' says this : >>> >>> Default: server max protocol = SMB3 >>> >>> OK, one of these is wrong, but which ??? > If

I have several Samba 3.6.24 domain controllers/file servers . Server1 - Solaris 10, Samba 3.6.24, max protocol NT1. This is the main file server. Server2 - Solaris 10, Samba 3.6.24, max protocol SMB2. 2ndary file server, not as heavily used as as server1. Server3 - Solaris 11, Samba 3.6.24, max protocol SMB2 . This was set up to replace Server 1. I also have a a Citrix XenApp

Hi Gaiseric, Do you happen to run into any oplock(opportunistic locking) issues? On my DC I have these issues with my group policy files. I'm hopeful using smb 2.0 will fix this problem. Thanks. On 3/4/2015 3:55 PM, Gaiseric Vandal wrote: > I have several Samba 3.6.24 domain controllers/file servers . > > > Server1 - Solaris 10, Samba 3.6.24, max protocol NT1. This is

OK. Now I'm really confused. I was not aware of two 'testparm' commands. Running 'testparm -v' shows correct default values. So whats the difference? On 3/6/2015 12:20 PM, Rowland Penny wrote: > On 06/03/15 17:05, Marc Muehlfeld wrote: >> Am 06.03.2015 um 14:56 schrieb Rowland Penny: >>>> From 'samba-tool testparm -v' : >>>>

On 06/03/15 13:36, James wrote: > Hi Marc, > > I'm a little confused. The values I provided for client and server > max protocol are default values. At least according to the command > 'samba-tool testparm -v'. I have not explicitly set them in my smb.conf > file. I assume SMB3 became the default at some point with a release? I'm > worried now that I must

Using Wireshark I see the protocol used as SMB2. Using a Windows workstation I tested by navigating to files and folders on my member server or to my sysvol folder on a DC. On 3/6/2015 8:56 AM, Rowland Penny wrote: > On 06/03/15 13:36, James wrote: >> Hi Marc, >> >> I'm a little confused. The values I provided for client and server >> max protocol are default

I have a big performance Problem when using Pegasus Mail storing it's Mail on on an samba Share. I assume PMail does write small blocks of data when saving files. The same performance degeneration is seen when copying files with "type file >copy" instead of using the copy Command. Client OS is Windows-Vista, Server is Samba Samba 3.3.4 Any Hints to optimize samba here? Elmar

My response is below. > -----Original Message----- > From: Gerald Carter [SMTP:gcarter@valinux.com] > Sent: Wednesday, July 12, 2000 12:29 PM > To: Hawks, Steven L > Cc: Multiple recipients of list SAMBA > Subject: Re: Can Samba be Installed on a Solaris 2.6 operating > system? > > "Hawks, Steven L" wrote: > > > > Can Samba be Installed on a

On Mon, 2017-11-27 at 15:32 +0100, Reindl Harald via samba wrote: > > Am 27.11.2017 um 15:13 schrieb Maxence SARTIAUX via samba: > > One of our customer has a Samba 3 domain and they have troubles when they try to join a Windows 10 computer, i'm pretty sure it's because we need to set > > server max protocol = NT1 > > on the domain configuration like the wiki says.

Hi, On asterisk 1.4.4 I have an strange effect on agents answering queue calls: If an agent does set current call on hold the phone immediately gets connected to the next incoming call. What might cause this effect? How can it be removed? Elmar

Hi Marc, I'm a little confused. The values I provided for client and server max protocol are default values. At least according to the command 'samba-tool testparm -v'. I have not explicitly set them in my smb.conf file. I assume SMB3 became the default at some point with a release? I'm worried now that I must make explicit changes to my smb.conf file when default values are

On Tue, 28 Nov 2017 09:58:41 +1300 Andrew Bartlett via samba <samba at lists.samba.org> wrote: > On Mon, 2017-11-27 at 15:32 +0100, Reindl Harald via samba wrote: > > > > Am 27.11.2017 um 15:13 schrieb Maxence SARTIAUX via samba: > > > One of our customer has a Samba 3 domain and they have troubles > > > when they try to join a Windows 10 computer, i'm

Hello, One of our customer has a Samba 3 domain and they have troubles when they try to join a Windows 10 computer, i'm pretty sure it's because we need to set server max protocol = NT1 on the domain configuration like the wiki says. But i'm wondering, what about other workstations ? There's no bad behavior limiting the maximum protocol to the current joined workstations