I am accessing the new member server. All my other servers are still on 3.6.x. Both settings are set to "default". Will look at logs now. Thanks! On Tue, Apr 19, 2016 at 2:39 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote:> On 4/19/2016 2:08 PM, Bill Baird wrote: > >> Hi All, >> >> I just setup a new server and added it to my domain last week and it has >> been working well. We are running a NT4-style Samba PDC for our domain >> controller. This server is running the CentOS packages for Samba 4.2.10-6 >> as a domain member. My issue is that I have one Windows 7 workstation that >> will only auto-negotiate to the NT1 protocol. If I run smbstatus, all of >> my >> other workstations use SMB2_10, as expected. >> >> Has anyone seen this before? Is there a log file I can look at to >> determine >> what is going wrong in the protocol negotiation? >> >> Thanks! >> >> --Bill >> > You can enable client specific logging and see if it turns up anything. > > https://wiki.samba.org/index.php/Client_specific_logging > > Access a share and review the logs. > > Is this Windows 7 workstation accessing the new member server and > displaying NT1 or the old one? > > Can you run on both member servers and report? > > testparm -v |grep "client ipc max protocol" and testparm -v |grep "client > ipc min protocol" > > -- > -James > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- *Bill Baird* Chief Technology Officer Office: 845-876-8228 x311 Mobile: 203-545-0437 www.phoenixmi.com
lingpanda101 at gmail.com
2016-Apr-19 18:50 UTC
[Samba] Workstation Limited to NT1 Protocol
On 4/19/2016 2:43 PM, Bill Baird wrote:> I am accessing the new member server. All my other servers are still > on 3.6.x. > > Both settings are set to "default". > > Will look at logs now. > > Thanks! > > > > On Tue, Apr 19, 2016 at 2:39 PM, lingpanda101 at gmail.com > <mailto:lingpanda101 at gmail.com> <lingpanda101 at gmail.com > <mailto:lingpanda101 at gmail.com>> wrote: > > On 4/19/2016 2:08 PM, Bill Baird wrote: > > Hi All, > > I just setup a new server and added it to my domain last week > and it has > been working well. We are running a NT4-style Samba PDC for > our domain > controller. This server is running the CentOS packages for > Samba 4.2.10-6 > as a domain member. My issue is that I have one Windows 7 > workstation that > will only auto-negotiate to the NT1 protocol. If I run > smbstatus, all of my > other workstations use SMB2_10, as expected. > > Has anyone seen this before? Is there a log file I can look at > to determine > what is going wrong in the protocol negotiation? > > Thanks! > > --Bill > > You can enable client specific logging and see if it turns up > anything. > > https://wiki.samba.org/index.php/Client_specific_logging > > Access a share and review the logs. > > Is this Windows 7 workstation accessing the new member server and > displaying NT1 or the old one? > > Can you run on both member servers and report? > > testparm -v |grep "client ipc max protocol" and testparm -v |grep > "client ipc min protocol" > > -- > -James > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > > > > > -- > *Bill Baird* > Chief Technology Officer > Office: 845-876-8228 x311 <tel:845-876-8228%20x311> > Mobile: 203-545-0437 <tel:203-545-0437> > www.phoenixmi.com <http://www.phoenixmi.com/> >The man page for smb.conf reads for "client ipc min protocol" The value default refers to the higher value of NT1 and the effective value of client min protocol. What does testparm -v | grep "client min protocol" give? -- -James
*testparm -v | grep "client min protocol"* client min protocol = CORE On Tue, Apr 19, 2016 at 2:50 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote:> On 4/19/2016 2:43 PM, Bill Baird wrote: > > I am accessing the new member server. All my other servers are still on > 3.6.x. > > Both settings are set to "default". > > Will look at logs now. > > Thanks! > > > > On Tue, Apr 19, 2016 at 2:39 PM, <lingpanda101 at gmail.com> > lingpanda101 at gmail.com <lingpanda101 at gmail.com> wrote: > >> On 4/19/2016 2:08 PM, Bill Baird wrote: >> >>> Hi All, >>> >>> I just setup a new server and added it to my domain last week and it has >>> been working well. We are running a NT4-style Samba PDC for our domain >>> controller. This server is running the CentOS packages for Samba 4.2.10-6 >>> as a domain member. My issue is that I have one Windows 7 workstation >>> that >>> will only auto-negotiate to the NT1 protocol. If I run smbstatus, all of >>> my >>> other workstations use SMB2_10, as expected. >>> >>> Has anyone seen this before? Is there a log file I can look at to >>> determine >>> what is going wrong in the protocol negotiation? >>> >>> Thanks! >>> >>> --Bill >>> >> You can enable client specific logging and see if it turns up anything. >> >> https://wiki.samba.org/index.php/Client_specific_logging >> >> Access a share and review the logs. >> >> Is this Windows 7 workstation accessing the new member server and >> displaying NT1 or the old one? >> >> Can you run on both member servers and report? >> >> testparm -v |grep "client ipc max protocol" and testparm -v |grep "client >> ipc min protocol" >> >> -- >> -James >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> > > > > -- > *Bill Baird* > Chief Technology Officer > Office: 845-876-8228 x311 <845-876-8228%20x311> > Mobile: 203-545-0437 > www.phoenixmi.com > > The man page for smb.conf reads for "client ipc min protocol" > > The value default refers to the higher value of NT1 and the > effective value of client min protocol. > > What does testparm -v | grep "client min protocol" give? > > -- > -James > >-- *Bill Baird* Chief Technology Officer Office: 845-876-8228 x311 Mobile: 203-545-0437 www.phoenixmi.com