[Samba] Accidental samba_dnsupdate success after NT_STATUS_CONNECTION_REFUSED
mail at crcomp.net
Sun Mar 17 20:44:12 UTC 2019
The process to join a new samba 4.6 DC to an existing samba 4.1 DC
samba_dnsupdate --verbose --all-names
to fail on the new DC with:
Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED
Noted: both samba versions are obsolete and will be updated post haste.
Regardless, samba_dnsupdate was accidentally invoked on the new DC while
the samba service on the existing DC just happened to be down and the
name service (bind) was up. bind accepted all new AD DNS records and
added them without error.
The domain join process was successfully completed and the domain
continues to seamlessly function under stress tests where only one DC
is available. It all appears to work.
My question pertains to the accidental discovery that the original
DC no longer failed with an NT_STATUS_CONNECTION_REFUSED when the
samba service on it was in a stopped state. Maybe it just doesn't
matter? Are there any hidden repercussions?
Thank you, 73,
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.
More information about the samba