Displaying 4 results from an estimated 4 matches for "nt4likedomainserv".
Did you mean:
nt4likedomainserver
2019 Jan 03
2
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
...man page for smb.conf notes "This mode will only work correctly if
> net(8) has been used to add this machine into a Windows NT Domain."?
> Did you add this host to a Windows NT domain, using "net join ..."?
>
Yes, I add this host with command:
net rpc join MEMBER -S NT4LIKEDOMAINSERVER -U root
I tried to change "security = USER" but it did not help.
I have to say that before upgrade samba from 4.7.1-9 to 4.8.3-4 I did
not use and did not run winbind daemon. But now it is necessary to run
winbind according to samba documentation:
https://www.samba.org/samba/history...
2019 Jan 04
3
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
Dne 4.1.2019 v 1:32 Gordon Messmer napsal(a):
> On 1/3/19 6:09 AM, Miroslav Geisselreiter wrote:
>> Yes, I add this host with command:
>> net rpc join MEMBER -S NT4LIKEDOMAINSERVER -U root
>
>
> I don't have any NT4-style domains handy to test with, so I can't be
> very specific.? Your logs seem to indicate that Samba believes itself
> to be the best DC for the domain.? See what you get from:
>
> net rpc info
> net rpc testjoin
>
> If...
2019 Jan 04
0
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
On 1/3/19 6:09 AM, Miroslav Geisselreiter wrote:
> Yes, I add this host with command:
> net rpc join MEMBER -S NT4LIKEDOMAINSERVER -U root
I don't have any NT4-style domains handy to test with, so I can't be
very specific.? Your logs seem to indicate that Samba believes itself to
be the best DC for the domain.? See what you get from:
net rpc info
net rpc testjoin
If nothing seems relevant, try leaving the domai...
2018 Dec 31
4
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
On 12/31/18 12:03 AM, Miroslav Geisselreiter wrote:
>
> This command is not working after upgrade. Logs say something about
> crap domain:
> set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was
> a DC for domain NT4MEMBER, refusing to initialize
What do you get from "wbinfo --ping-dc"?