Researched the forums before posting but was not able to find solution to my
issue. Could be a unique problem.
GPO's are not being applied to users and computers because 'RPC is
unavailable'. The GPO's were being applied before, but not sure what
happened. Started noticing this once I binded a new instance of Windows 10
to the SambaDC and the machine nor user were picking up the GPO's. When I
run gpupdate /force there is no error given but when right clicking on the
OU and running 'Group Policy Update..', it shows failed and the RPC error
mentioned above. Has anyone ever experienced something like this?
<http://samba.2283325.n4.nabble.com/file/n4710461/Selection_001.png> .
Any help would be appreciated.
--
View this message in context: http://samba.2283325.n4.nabble.com/RPC-Server-is-Unavailable-when-updating-GPO-tp4710461.html
Sent from the Samba - General mailing list archive at Nabble.com.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
I think you would have to start looking at a network trace to
understand who is refusing what exactly.
I'm assuming this is something that is trying to trigger a process
directly on the client?
I realise you probably don't want to set up one just to test, but the
question that comes to mind is: Is it a Samba issue, or does this
happen in a Windows domain also? Is there any communication with the
DC?
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
--
View this message in context: http://samba.2283325.n4.nabble.com/RPC-Server-is-Unavailable-when-updating-GPO-tp4710461p4710469.html
Sent from the Samba - General mailing list archive at Nabble.com.
--
Cheers,
Garming