[mythtv-users] OT: Linux problem

Damian myth at surr.co.uk
Mon Sep 28 08:35:46 UTC 2015


On 28/09/2015 00:15, Kirk Bocek wrote:
>
>
> On September 27, 2015 1:27:09 PM PDT, Damian <myth at surr.co.uk> wrote:
>> On 19/09/2015 15:21, Kirk Bocek wrote:
>>>
>>>
>>> On 9/19/2015 7:03 AM, Peter Bennett (cats22) wrote:
>>>> On 09/03/2015 09:46 AM, Damian wrote:
>>>>> Hi Everyone,
>>>>>
>>>>> I have tried to get to the bottom of this problem on a more general
>>>>> Linux forum (ubuntuforums.org/showthread.php?t=2289024) but no one
>>>>> seems to be able to help.
>>>>>     From windows, it says "Cannot connect all network drives", then
>> if I
>>>>> click on it says, "An error has occurred while reconnecting S: to
>>>>> [path] Microsoft Windows Network: Not enough storage is available
>> to
>>>>> process this command. This connection has not been restored." I
>> can't
>>>>> remember the error from a Linux box, but its similar and mentions
>>>>> memory.
>>>>>
>>>> I have had this problem before and a setting had to be changed in
>>>> Windows to fix it. I don't have a record of what I did, but I think
>> this
>>>> is the answer, see below links:
>>>>
>>>> https://support.microsoft.com/en-us/kb/106167
>>>>
>>>>
>> http://www.techfleece.com/2011/03/03/how-to-fix-not-enough-server-storage-is-available-to-process-this-command-error/
>>
>>>>
>>>>
>>>>
>>>
>>> I just went through something similar on my CentOS 6.6 host running
>>> Mythbackend. The answer was to add:
>>>
>>> Max Protocol = SMB2
>>>
>>> to the Global section of smb.conf. Note this host is running Samba 3.
>>
>>> My solution for a long time was to run Samba 4 but that starting
>>> causing other problems and I finally had to downgrade.
>>>
>>> It's weird because I have two other office servers running CentOS 6.6
>>
>>> and Samba 3 that don't require this setting and the work fine.
>>>
>>> Kirk
>> You fixed it !!!!!!!!!!!!!!!!!!!!!
>>
>> Thanks Kirk :-)
>>
>> Line added, quick reboot, now everything is working as it used to.
>> Result! :-)
>>
>
> Excellent. I still don't know why this was required. An interaction with Myth? But I really don't see how.
>
>

I spoke too soon.

The problem is back again this morning :-(


More information about the mythtv-users mailing list