Displaying 2 results from an estimated 2 matches for "7fb38333".
Did you mean:
77.38333
2016 Jun 08
0
inconsistent DNS information, windows domain member issues..
...6 GMT+02:00 Rowland penny <rpenny at samba.org>:
[dropped lots]
Now with the changes I still get the following in the log of dc2, at least occasionally.
[2016/06/08 20:10:13.832105, 0] ../source4/librpc/rpc/dcerpc_sock.c:240(continue_ip_open_socket)
Failed to connect host 192.168.177.21 (7fb38333-aced-4ce8-9a15-a3f6459ecc2a._msdcs.samba.lindenberg.one) on port 135 - NT_STATUS_CONNECTION_REFUSED.
I write occasionally because I tried restarting samba on dc2 and then the message did not appear.
Nothing suspicious in log of dc1.
Getting back to my initial issue list:
> -----Ursprüngl...
2016 Jun 06
2
inconsistent DNS information, windows domain member issues..
To regenerate dns.keytab I expect you only need to relaunch
samba_upgradedns --dns-backend=BIND9_DLZ.
If I'm wrong (it happens quiet often) you would have to first launch:
samba_upgradedns --dns-backend=SAMBA_INTERNAL
and then
samba_upgradedns --dns-backend=BIND9_DLZ
Here you should have a dns.keytab.
Now, right issues: dns related files in samba/private must be accessible to
the UNIX user