Displaying 20 results from an estimated 2000 matches similar to: "Unable to contact RPC server on a new DC"
2023 Nov 06
3
Unable to contact RPC server on a new DC
Greetings, All!
I've added a new DC to the working AD, transferred FSMO roles (checked, all 7
are ok') and (supposedly) correctly demoted the old DC.
SchemaMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=
InfrastructureMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=S
RidAllocationMasterRole owner: CN=NTDS
2023 Jun 08
2
Unable to contact RPC server on a new DC
Greetings, All!
I've added a new DC to the working AD, transferred FSMO roles (checked, all 7
are ok') and (supposedly) correctly demoted the old DC.
SchemaMasterRole owner: CN=NTDS
Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=
InfrastructureMasterRole owner: CN=NTDS
Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=S
RidAllocationMasterRole owner: CN=NTDS
2023 Nov 06
2
Unable to contact RPC server on a new DC
Greetings, Rowland Penny via samba!
> On 08/06/2023 13:53, Andrey Repin via samba wrote:
>> Hello Rowland Penny,
>> > Thursday, June 8, 2023, 2:10:39 PM, you wrote:
>> > > >> On 08/06/2023 11:41, Andrey Repin via samba wrote:
>>>> Greetings, All!
>>>>> I've added a new DC to the working AD, transferred FSMO roles (checked, all 7
2023 Nov 06
1
Unable to contact RPC server on a new DC
On Fri, 9 Jun 2023 00:47:07 +0300
Andrey Repin via samba <samba at lists.samba.org> wrote:
> Greetings, Rowland Penny via samba!
>
>
>
> > On 08/06/2023 13:53, Andrey Repin via samba wrote:
> >> Hello Rowland Penny,
> >> > Thursday, June 8, 2023, 2:10:39 PM, you wrote:
> >> > > >> On 08/06/2023 11:41, Andrey Repin via samba
2023 Jun 08
2
Unable to contact RPC server on a new DC
On 08/06/2023 13:53, Andrey Repin via samba wrote:
> Hello Rowland Penny,
>
> Thursday, June 8, 2023, 2:10:39 PM, you wrote:
>
>
>
>> On 08/06/2023 11:41, Andrey Repin via samba wrote:
>>> Greetings, All!
>>>> I've added a new DC to the working AD, transferred FSMO roles (checked, all 7
>>> are ok') and (supposedly) correctly
2023 Jun 11
1
Unable to contact RPC server on a new DC
Hello Andrew Bartlett,
Friday, June 9, 2023, 11:25:01 PM, you wrote:
> On Thu, 2023-06-08 at 13:41 +0300, Andrey Repin via samba wrote:
>> Greetings, All!
>>
>> I've added a new DC to the working AD, transferred FSMO roles
>> (checked, all 7
>> are ok') and (supposedly) correctly demoted the old DC.
>>
>> SchemaMasterRole owner: CN=NTDS
2023 Nov 07
1
Unable to contact RPC server on a new DC
On Tue, 7 Nov 2023 20:00:40 +0300
Andrey Repin via samba <samba at lists.samba.org> wrote:
> Greetings, Rowland Penny via samba!
>
> > OK, I give in, why have 4 emails from Andrey Repin, that were
> > apparently sent in May & June of this year, just appeared in my mail
> > client ?
>
> Don't worry, your sanity is not affected. My mail provider had
2023 Nov 07
2
Unable to contact RPC server on a new DC
Greetings, Rowland Penny via samba!
> OK, I give in, why have 4 emails from Andrey Repin, that were
> apparently sent in May & June of this year, just appeared in my mail
> client ?
Don't worry, your sanity is not affected. My mail provider had changed
submission policy without a sufficient notification, causing my transit mail
server to block mail queue since last August.
2023 Jun 09
1
Unable to contact RPC server on a new DC
On Thu, 2023-06-08 at 13:41 +0300, Andrey Repin via samba wrote:
> Greetings, All!
>
> I've added a new DC to the working AD, transferred FSMO roles
> (checked, all 7
> are ok') and (supposedly) correctly demoted the old DC.
>
> SchemaMasterRole owner: CN=NTDS
> Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=
> InfrastructureMasterRole owner:
2023 Nov 07
1
Unable to contact RPC server on a new DC
LP
On Nov 7, 2023 at 18:06 +0100, Andrey Repin via samba <samba at lists.samba.org>, wrote:
>
>
> AD DC configuration:
>
> # Global parameters
> [global]
> auto services = homes
> client ldap sasl wrapping = sign
> dns forwarder = 192.168.1.12
> dos charset = CP866
> logging = systemd
> log level = 1
> netbios name = DC2
> panic action =
2023 Nov 07
1
Unable to contact RPC server on a new DC
On Tue, 7 Nov 2023 21:52:56 +0300
Andrey Repin via samba <samba at lists.samba.org> wrote:
> Greetings, Rowland Penny via samba!
>
> > I would remove these from the DC smb.conf, they are either defauts,
> > not required or flat out doing nothing on a DC:
> >
> > auto services = homes
> > client ldap sasl
2023 Nov 07
1
Unable to contact RPC server on a new DC
Greetings, Rowland Penny via samba!
> I would remove these from the DC smb.conf, they are either defauts, not
> required or flat out doing nothing on a DC:
>
> auto services = homes
> client ldap sasl wrapping = sign
> tls enabled = Yes
Without "tls enabled" ldaps:// access does not work.
> winbind
2023 Jun 09
1
Unable to contact RPC server on a new DC
On 09/06/2023 18:11, Andrey Repin via samba wrote:
> Greetings, Rowland Penny via samba!
>> OK, you have these lines on the DC:
>
>> winbind nss info = rfc2307
>> winbind use default domain = Yes
>> idmap config darkdragon : unix_nss_info = yes
>> idmap config darkdragon : unix_primary_group = yes
>>
2018 Feb 17
4
Winbind idmap partially fails to load attributes with 4.6.7 (Ubuntu 17.10)
Greetings, All!
I'm stumbled upon an event I can't understand. Rolled out a new Ubuntu 17.10
box in preparation for eventual 18.04 launch and… it just does not fly.
Here's a brief and apparent summary of the problem:
$ smbd -V; getent passwd anrdaemon
Version 4.3.11-Ubuntu (14.04, 16.04)
anrdaemon:*:10000:10001:Andrey Repin,,,,umask=0027:/home/anrdaemon:/bin/bash
Version
2023 Jun 11
1
Unable to contact RPC server on a new DC
Hello Rowland Penny,
Friday, June 9, 2023, 8:51:25 PM, you wrote:
> On 09/06/2023 18:11, Andrey Repin via samba wrote:
>> Greetings, Rowland Penny via samba!
>>> OK, you have these lines on the DC:
>>> winbind nss info = rfc2307
>>> winbind use default domain = Yes
>>> idmap config darkdragon : unix_nss_info = yes
2018 Feb 18
0
Winbind idmap partially fails to load attributes with 4.6.7 (Ubuntu 17.10)
On Sun, 18 Feb 2018 02:00:35 +0300
Andrey Repin via samba <samba at lists.samba.org> wrote:
> Greetings, All!
>
> I'm stumbled upon an event I can't understand. Rolled out a new
> Ubuntu 17.10 box in preparation for eventual 18.04 launch and… it
> just does not fly.
>
> Here's a brief and apparent summary of the problem:
>
> $ smbd -V; getent passwd
2018 Feb 18
0
Winbind idmap partially fails to load attributes with 4.6.7 (Ubuntu 17.10)
Hello,
I think the configuration changed in 4.6. see here:
https://wiki.samba.org/index.php/Idmap_config_ad
Regards
> Am 18.02.2018 um 00:00 schrieb Andrey Repin via samba <samba at lists.samba.org>:
>
> Greetings, All!
>
> I'm stumbled upon an event I can't understand. Rolled out a new Ubuntu 17.10
> box in preparation for eventual 18.04 launch and… it just
2015 Feb 03
3
pam_winbind vs. pam_ldap ?
Greetings, All!
I'm using Samba 3.6 and OpenLDAP currently.
The core configuration has been done eons ago, and I'm not quite sure it is
actual any more. I see a number of PAM-related errors every time the system
boot up. One concerning me is
Jan 28 02:31:21 daemon1 perl: pam_ldap: error trying to bind as user "uid=root,ou=Users,dc=darkdragon,dc=lan" (Invalid credentials)
Is this
2017 Mar 26
2
Unable to access directories after Samba upgrade
Greetings, All!
I have an extremely strange issue.
I'm using Ubuntu 14.04 and after upgrading Samba to
4.3.11+dfsg-0ubuntu0.14.04.6 I'm unable to access third level of
subdirectories on shares.
ACLs are even on both 2nd and 3rd levels, but I get access denied no matter
what I do.
$ getfacl . Android/ Android/The\ Settlers\ HD/
# file: .
# owner: anrdaemon
# group: domain\040users
2015 Apr 10
1
How can I have new users/groups to include posixAccount/posixGroup schema automatically?
Greetings, Rowland Penny!
>>>>>>>>> well tough, the smbldap-tools were written to do a job, map windows
>>>>>>>>> users to unix users and vice versa.
>>>>>>>> No. smbldap-tools were doing exactly the same as AD do: kept all users in one
>>>>>>>> database.
>>>>>>>>