Displaying 4 results from an estimated 4 matches for "kobol".
Did you mean:
cobol
2013 Jul 15
1
Packet loss with LocalDiscovery
Hi,
I believe I have found a bug with regard to the LocalDiscovery feature.
This is on tinc-1.1pre7 between two Windows nodes.
Steps to reproduce:
- Get two nodes talking using LocalDiscovery (e.g. put them on the same
LAN behind a NAT with no metaconnection to each other)
- Make one ping the other.
Expected result:
- The two nodes should ping each other without any packet loss,
hopefully at
2016 May 05
2
standalone ADDC with samba_internal dns backend - windows client do not register in dns
good lords of Kobol, that solved my problem !
thank you very much !
As we can consider this as an official workaround, should it be in the
wiki ? (this is definitively in my docs now :)
On 05/04/2016 07:55 PM, lingpanda101 at gmail.com wrote:
> On 5/4/2016 5:02 AM, David STIEVENARD wrote:
>> Hi
>>...
2016 May 23
1
standalone ADDC with samba_internal dns backend - windows client do not register in dns
...eated by computer-user named
"my-machine$"), the host is owner of the object and as "full control" on
the entry.
2016-05-14 12:19 GMT+02:00 Andrew Bartlett <abartlet at samba.org>:
> On Thu, 2016-05-05 at 16:52 +0800, David STIEVENARD wrote:
> > good lords of Kobol, that solved my problem !
> > thank you very much !
> >
> > As we can consider this as an official workaround, should it be in
> > the
> > wiki ? (this is definitively in my docs now :)
> >
>
> Turning off DNS update security really should not be recommende...
2016 May 04
3
standalone ADDC with samba_internal dns backend - windows client do not register in dns
Hi
first project with samba, first post on this mailing list and, actually,
first time using a mailing list ever ;-)
In summary
==========================================
I try to install samba in a test VMs, everything seems fine but when
windows client joins the domain it doesn't register in samba's internal dns
in detail
==========================================
My objective
-