26.01.2017 15:31, debbie10t пишет:
>
> On 26/01/17 07:10, Dmitry Melekhov wrote:
>> 26.01.2017 10:59, Gert Doering пишет:
>>> Hi,
>>>
>>> On Thu, Jan 26, 2017 at 09:54:59AM +0400, Dmitry Melekhov wrote:
Could you tell me is this expected behavior and, if yes, is there any
workaround ,
On 26/01/17 07:10, Dmitry Melekhov wrote:
> 26.01.2017 10:59, Gert Doering пишет:
>> Hi,
>>
>> On Thu, Jan 26, 2017 at 09:54:59AM +0400, Dmitry Melekhov wrote:
>>> Could you tell me is this expected behavior and, if yes, is there any
>>> workaround , something like dhcp-release for windows?
>>
26.01.2017 16:43, debbie10t пишет:
>
> On 26/01/17 11:55, Dmitry Melekhov wrote:
>> 26.01.2017 15:31, debbie10t пишет:
>>> On 26/01/17 07:10, Dmitry Melekhov wrote:
26.01.2017 10:59, Gert Doering пишет:
> Hi,
>
> On Thu, Jan 26, 2017 at 09:54:59AM +0400, Dmitry Melekhov wrote:
On 26/01/17 11:55, Dmitry Melekhov wrote:
> 26.01.2017 15:31, debbie10t пишет:
>>
>> On 26/01/17 07:10, Dmitry Melekhov wrote:
>>> 26.01.2017 10:59, Gert Doering пишет:
Hi,
On Thu, Jan 26, 2017 at 09:54:59AM +0400, Dmitry Melekhov wrote:
> Could you tell me is this expected
Hi,
On Thu, Jan 26, 2017 at 07:36:32PM +0100, David Sommerseth wrote:
> Anyhow ... quick-fix/workaround: Don't use --auth-nocache
What happens if you have --auth-nocache, the server sends a token, and
the token expires? Will the client get something back that it can
understand as "oh, I need to
Hi,
On Fri, Jan 27, 2017 at 12:02:21AM +0100, David Sommerseth wrote:
> On 26/01/17 19:45, Gert Doering wrote:
> > On Thu, Jan 26, 2017 at 07:36:32PM +0100, David Sommerseth wrote:
> >> Anyhow ... quick-fix/workaround: Don't use --auth-nocache
> >
> > What happens if you have --auth-nocache, the
