search for: dnss

...be tied into your > main problem or it could be a totally separate problem, but you will not > know until you sort the main problem ;-) RSAT works when I enter the IP of a DC ... I can edit objects etc -> ok for me now I don't know what to fix, though ;-) I will have them check the DNSs on the one PC. Or check via teamviewer later. The windows-server-user pulls the GPOs ok. dbcheck looks OK on both DCs, wbinfo-queries work ...

...meserver that is set in the DCs > smb.conf if > > using the internal DNS server, or if in the named conf > files if using > > Bind9 > > additional question here as I also prepare to deploy a 2nd DC > at one site: > > right now I tell the clients to use these as DNSs (via DHCP): > > samba-DC, DNS on router to internet, one DNS upstream (just in case, > maybe stupid) > > with additional DCs I assume I would have to list the DCs as well as > DNSs, to make sure DNS (in terms of AD *and* "normal" DNS) still works > in case the first...

Hi Rowland, many thanks for your help, On Wed, Nov 08, 2017 at 11:00:59AM +0000, Rowland Penny wrote: > > On Wed, 8 Nov 2017 11:18:10 +0100 > Ervin Hegedüs <airween at gmail.com> wrote: > > > > ======== > > open-ldap: ... > > -------- > > /etc/resolv.conf > > search core.mydomain.hu > > nameserver 127.0.0.1 > > nameserver

...oblem could be tied into your main problem or it could be a totally separate problem, but you will not know until you sort the main problem ;-) RSAT works when I enter the IP of a DC ... I can edit objects etc -> ok for me now I don't know what to fix, though ;-) I will have them check the DNSs on the one PC. Or check via teamviewer later. The windows-server-user pulls the GPOs ok. dbcheck looks OK on both DCs, wbinfo-queries work ... Stefan, you didn't have a problem, a new PC was added and you now have problem. I would be peering very, very closely at the new PC and ruling that...

...is not. The patch is not included in the mainstream version which is supplied by most of the linux distribution. For instance with openssh 6.2p2-1 supplied by Arch Linux '#man ssh_config' doesn't know anything about the directive 'GSSAPITrustDNS' and I'm not able to resolve DNSs. This is really crazy: a patch has been there since 7 years ago, but still not fixed! -- You are receiving this mail because: You are the assignee for the bug.

Am 03.06.19 um 12:08 schrieb Rowland penny via samba: > On 03/06/2019 10:58, Stefan G. Weichinger via samba wrote: >> Am 03.06.19 um 11:40 schrieb Rowland penny via samba: >>> On 03/06/2019 10:22, Stefan G. Weichinger via samba wrote: >>>> samba-4.8.12 on 2 DCs, replication works ... >>>> >>>> An external admin joined a new PC and the GPOs

I can prove this within my environment: at the main site: one DC server(samba 4.1.13), one dhcp server, two DNS servers(forward AD query to two AD servers), at the branch site: one DC server(samba 4.1.13), one dhcp server, one DNS server(forward AD query to two AD server), DNSs on client machines point to the DNS servers(not point to the DC). The two DCs are synced and do their work properly without any issue(almost one year, connected via openVPN). Two sites are configured(using windows sites and services tool): one site for branch with its subnet, and the Default-F...

On 11/20/2015 10:17 AM, mathias dufresne wrote: > > > 2015-11-20 15:11 GMT+01:00 James <lingpanda101 at gmail.com > <mailto:lingpanda101 at gmail.com>>: > > On 11/20/2015 7:40 AM, Ole Traupe wrote: > > > > Am 20.11.2015 um 11:54 schrieb mathias dufresne: > > Hi Ole, > > I'm still not answering your issue