[Samba] DOS clients problem with 3.6.22 vs 3.6.18

[Dominic Raferd]

On 15/04/2014 06:34, Dominic Raferd wrote:
>
> On 14/04/2014 21:03, Günter Kukkukk wrote:
>> Am 14.04.2014 17:19, schrieb Dominic Raferd:
>>> I have tried to upgrade our samba server from 3.6.18 to 3.6.22 but 
>>> found that our DOS clients could no longer connect (using DOS 6.22 
>>> and Microsoft
>>> LAN Manager 2.1).
>>>
>>> With 3.6.18 we use smb.conf setting 'min protocol = LANMAN2' and it 
>>> works great, with 3.6.22 although clients can connect ok, they 
>>> cannot obtain a
>>> directory listing. Instead the first file (sometimes misnamed) just 
>>> relists endlessly.
>>>
>>> Using loglevel 4 I find this text in log file when a DOS client 
>>> connects to either version of samba 3.6:
>>>
>>>    Requested protocol [PC NETWORK PROGRAM 1.0]
>>>    Requested protocol [MICROSOFT NETWORKS 3.0]
>>>    Requested protocol [DOS LM1.2X002]
>>>    Selected protocol DOS LM1.2X002
>>>
>>> It seems like there is a bug in 3.6.22 or is there a new setting 
>>> that might work with 3.6.22 to get it working again? (Sorry I am 
>>> unable to try 3.6.23
>>> but I see nothing in the changelog which suggests that this problem 
>>> might go away with 3.6.23.)
>>>
>>> Thanks for any help
>>>
>>> Dominic
>> have a look at
>> https://bugzilla.samba.org/show_bug.cgi?id=2662
>>
>> Should be fixed now - but a user reported still seeing problems.
>>
>> Cheers, Günter
>>
>
> Thanks Gunter, that sounds just what I need, but which version of 4.1 
> do I need to run to try this fix? Is it in the main release 4.1.5 or 
> 4.1.6, or do I need to build my own?
>
> Regards
>
> Dominic

To answer my own question, it seems that 4.1.5 includes this fix 
(http://www.samba.org/samba/history/samba-4.1.5.html), so I will try it 
out asap.