30.07.2017 12:08, Nenhum_de_Nos wrote:
> I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1. All
> was fine.
>
> Then I updated to 11.1-R by recompiling from svn, using the same
> kernelconfig from 10.3, and now my windows client shows timeouts and
> really slow connection.
On Tue, August 1, 2017 11:41, Werner Griessl wrote:
> On 08/01/17 04:52, Nenhum_de_Nos wrote:
>>
>> On Sun, July 30, 2017 02:08, Nenhum_de_Nos wrote:
>>> Hi,
>>>
>>> I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1.
>>> All
>>> was fine.
>>>
>>> Then I updated to 11.1-R by
On 08/01/17 04:52, Nenhum_de_Nos wrote:
On Sun, July 30, 2017 02:08, Nenhum_de_Nos wrote:
Hi,
I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1. All
was fine.
Then I updated to 11.1-R by recompiling from svn, using the same
kernelconfig from 10.3, and now my windows
> Then I updated to 11.1-R by recompiling from svn, using the same
> kernelconfig from 10.3, and now my windows client shows timeouts and
> really slow connection. File copy never past kilobytes per second :(
I think the issue is with the SAMBA port. I was running the samba36
port under FreeBSD
On Sun, July 30, 2017 02:08, Nenhum_de_Nos wrote:
> Hi,
>
> I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1. All
> was fine.
>
> Then I updated to 11.1-R by recompiling from svn, using the same
> kernelconfig from 10.3, and now my windows client shows timeouts and
> really
Hi,
I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1. All
was fine.
Then I updated to 11.1-R by recompiling from svn, using the same
kernelconfig from 10.3, and now my windows client shows timeouts and
really slow connection. File copy never past kilobytes per second :(
I
