Displaying 19 results from an estimated 19 matches for "4c79".
Did you mean:
479
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
...st SRV
_kpasswd._udp.mydomain.at dc.mydomain.at 464
Lookup of _kpasswd._udp.mydomain.at. succeeded, but we failed to find a
matching DNS entry for SRV _kpasswd._udp.mydomain.at dc.mydomain.at 464
need update: SRV _kpasswd._udp.mydomain.at dc.mydomain.at 464
Looking for DNS entry CNAME
e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mydomain.at dc.mydomain.at
as e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mydomain.at.
Lookup of e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mydomain.at.
succeeded, but we failed to find a matching DNS entry for CNAME
e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mydomain.at...
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
On 31/07/2019 12:04, Stefan G. Weichinger via samba wrote:
> Am 31.07.19 um 12:50 schrieb Rowland penny via samba:
>> On 31/07/2019 11:40, Stefan G. Weichinger via samba wrote:
>>> Am 31.07.19 um 12:32 schrieb Rowland penny via samba:
>>>> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote:
>>>>> "dc" was the old name a few years ago
2019 Jul 31
4
GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 11:51 schrieb L.P.H. van Belle via samba:
> Run : nslookup dc
non-existent: good, afaik
> If this one removed, then its a hunt for the dc record in the AD and DNS.
> Review with Windows tools, the Active Directory Sites and Services
> If there is nothing left there.
It's there in Sites - Default-First-Site-Name - Servers ...
>> sorry for going loops
2019 Mar 13
7
replication fails
Am 13.03.19 um 13:25 schrieb Stefan G. Weichinger via samba:
> My DC1 is named "PRE01SVDEB02"
> and DC2 = "PRE01SVDEB03"
checked for resolv.conf and DNS-pointers again. made sure that all 3
FQDNs (2 DCs, one DM) resolve from the servers.
showrepl is happy again on DC1, but still fails on/to DC2
hm
manual replicate: no progress or success visible (either from DC1 or
2019 Aug 07
2
Bind9 doesn't updated - TSIG error with server: tsig verify failure
...;10.41.20.67']
force update: A king.smb 10.41.20.67
force update: NS smb king.smb
force update: NS _msdcs.smb king.smb
force update: A smb 10.41.20.67
force update: SRV _ldap._tcp.smb king.smb 389
force update: SRV _ldap._tcp.dc._msdcs.smb king.smb 389
force update: SRV
_ldap._tcp.6be160cc-cf53-4c79-a088-b81267a01ec2.domains._msdcs.smb king.smb
389
force update: SRV _kerberos._tcp.smb king.smb 88
force update: SRV _kerberos._udp.smb king.smb 88
force update: SRV _kerberos._tcp.dc._msdcs.smb king.smb 88
force update: SRV _kpasswd._tcp.smb king.smb 464
force update: SRV _kpasswd._udp.smb king.sm...
2019 Jul 12
3
GPO infrastructure? -> 4.8.x to 4.9.x
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Stefan G. Weichinger via samba
> Verzonden: vrijdag 12 juli 2019 10:24
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] GPO infrastructure? -> 4.8.x to 4.9.x
>
> Am 10.07.19 um 08:40 schrieb Stefan G. Weichinger via samba:
>
> > more of this:
> >
2019 Mar 13
0
replication fails
...n DC2
>
>
> [2019/03/13 14:38:55.729004, 3]
> ../source4/dsdb/repl/drepl_service.c:206(_drepl_schedule_replication)
> _drepl_schedule_replication: forcing sync of partition
> (61081d43-e55d-4791-9d4c-e87f036a8772,
> DC=DomainDnsZones,DC=pilsbacher,DC=at,
> e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mytld.at)
>
>
> but no progress
>
> -
>
> I let my fingers off it for now ... new user(s) needed there
> next week.
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.sa...
2019 Jul 12
0
GPO infrastructure? -> 4.8.x to 4.9.x
..._kpasswd._udp.mydomain.at.
> Checking 0 100 464 pre01svdeb03.mydomain.at. against SRV
> _kpasswd._udp.mydomain.at dc.mydomain.at 464
> Checking 0 100 464 dc.mydomain.at. against SRV
> _kpasswd._udp.mydomain.at
> dc.mydomain.at 464
> Looking for DNS entry CNAME
> e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mydomain.at dc.mydomain.at
> as e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.mydomain.at.
> Looking for DNS entry SRV
> _ldap._tcp.Default-First-Site-Name._sites.mydomain.at
> dc.mydomain.at 389
> as _ldap._tcp.Default-First-Site-Name._sites.mydomain.at.
>...
2019 Mar 13
2
replication fails
Am 13.03.19 um 12:49 schrieb Rowland Penny via samba:
>> Should /etc/hosts contain pointers to own FQDN or not? To DCs?
>>
>
> /etc/hosts should contain a line that points 127.0.0.1 to localhost and
> a line that points the DC's ipaddress to its FQDN and shorthostname
>
> EXAMPLE:
>
> 127.0.0.1 localhost
> 192.168.0.6 dc4.samdom.example.com dc4
>
2019 Jul 31
1
GPO issues - getting SYSVOL cleaned up again
...t-First-Site-Name
> ,CN=Sites,CN=Configuration,DC=mydomain,DC=at
> objectGUID: a60fbb5f-926b-484d-992c-c1ef5cc0936d
>
> # record 2
> dn: CN=NTDS
> Settings,CN=DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,
> CN=Configuration,DC=mydomain,DC=at
> objectGUID: e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4
>
> that's a no then
Ah, so this is what needs to be fixed.
>
>
> > Then, klik on the GUID, properties, and where you see
> Server: SERVERNAME , there you can choose "change".
>
> so I wait here?
No, here you select the correct DC n...
2019 Jul 31
1
FW: GPO issues - getting SYSVOL cleaned up again
...dc..at 88
/var/lib/samba/private/dns_update_cache:SRV _kerberos._tcp.dc._msdcs..at
dc..at 88
/var/lib/samba/private/dns_update_cache:SRV _kpasswd._tcp..at dc..at 464
/var/lib/samba/private/dns_update_cache:SRV _kpasswd._udp..at dc..at 464
/var/lib/samba/private/dns_update_cache:CNAME
e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs..at dc..at
/var/lib/samba/private/dns_update_cache:SRV
_ldap._tcp.Default-First-Site-Name._sites..at dc..at 389
/var/lib/samba/private/dns_update_cache:SRV
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs..at dc..at 389
/var/lib/samba/private/dns_update_cache:SRV
_kerber...
2019 Jul 31
4
GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 11:25 schrieb Stefan G. Weichinger via samba:
> So to me it seems obvious to get rid of that "dc.mydomain.at" ... at
> least as a next step.
Went through DNS on the windows server and rm-ed all containing
"dc.mydomain.at"
There was a SRV-record below
"_msdcs.mydomain.at" "pdc" "_tcp" pointing to "dc.mydomain.at"
2019 Jul 31
3
FW: GPO issues - getting SYSVOL cleaned up again
(oeps) this need to be in this mail also.
Try : rgrep "dc.domain.at" /etc/*
> -----Oorspronkelijk bericht-----
> Van: L.P.H. van Belle
> Verzonden: woensdag 31 juli 2019 12:17
> Aan: 'samba at lists.samba.org'
> Onderwerp: RE: [Samba] GPO issues - getting SYSVOL cleaned up again
>
> Ok, on that server.
>
> This
> >
2019 Jul 31
5
GPO issues - getting SYSVOL cleaned up again
...c.pilsbacher.at
464 as _kpasswd._udp.pilsbacher.at.
Checking 0 100 464 pre01svdeb03.pilsbacher.at. against SRV
_kpasswd._udp.pilsbacher.at dc.pilsbacher.at 464
Checking 0 100 464 dc.pilsbacher.at. against SRV
_kpasswd._udp.pilsbacher.at dc.pilsbacher.at 464
Looking for DNS entry CNAME
e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.pilsbacher.at
dc.pilsbacher.at as
e5922d4b-9bf0-4c79-b256-ff5f75a3e4f4._msdcs.pilsbacher.at.
Looking for DNS entry SRV
_ldap._tcp.Default-First-Site-Name._sites.pilsbacher.at dc.pilsbacher.at
389 as _ldap._tcp.Default-First-Site-Name._sites.pilsbacher.at.
Checking 0 100 389...
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
?? And we did compair this months ago..
You did say, everything is in sync now.
Ahhh... ;-)
If you really want to know if you DC's are setup the same.
Tip.. Copy /etc of both server into a new folder.
And runn diff -r /etc-dc1/ /etc-dc2/ > check-me.txt
And check-me.txt
I just did that on my brand new Buster proxy servers, 2 with keepalived.
I'm almost done with this, you
2004 Sep 24
1
sharing /etc/passwd
How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that
can't do PAM, perhaps NIS is the way to go (assuming, of course, you're
behind a firewall). You can store login information in LDAP like you want,
then use a home-grown script to extract the information to a NIS map. Or,
if you have a Solaris 8 machine lying around, you can cut out the middle
step and use
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...(348840ee-8420-488b-b755-2deb08d11162) on home-client-2
[2017-10-25 10:14:13.383890] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/0B7E0F9968E74CF20E3E83FD7BD2AA42096BAB7C (c10fa851-00e2-4593-84dd-36cc544c792e) on home-client-2
[2017-10-25 10:14:13.392941] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/5B4C2B09520F12BF5CEF5FF95E27AF5334F49E96 (f05af161-0ce1-41e6-9b8e-2d03b5a28055) on home-client-2
[2017-10-2...