search for: nt4member

....23-51.el6.x86_64. Machine with CentOS 7.6 is domain member offering network shares to windows clients. Before upgrade my samba-4.7 run only smb and nmb services and everything were fine. After upgrade samba-4.8.3 runs smb nmb and winbind services. smb.conf: workgroup = NT4DOMAIN netbios name = NT4MEMBER |# wbinfo -m --verbose Domain Name DNS Domain Trust Type Transitive In Out BUILTIN Local NT4MEMBER Local NT4DOMAIN INTRANET.XX Workstation Yes No Yes # wbinfo --own-domain NT4DOMAIN | I discovered that winbind is not authenticating users with NT4DOMAIN but only with NT4MEMBER. In this case NT...

...th CentOS 7.6 is domain member offering network shares to > windows clients. Before upgrade my samba-4.7 run only smb and nmb > services and everything were fine. After upgrade samba-4.8.3 runs smb > nmb and winbind services. > smb.conf: > workgroup = NT4DOMAIN > netbios name = NT4MEMBER > |# wbinfo -m --verbose Domain Name DNS Domain Trust Type Transitive In > Out BUILTIN Local NT4MEMBER Local NT4DOMAIN INTRANET.XX Workstation > Yes No Yes # wbinfo --own-domain NT4DOMAIN | > > I discovered that winbind is not authenticating users with NT4DOMAIN > but only with...

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"?

On 12/21/18 12:15 PM, Miroslav Geisselreiter wrote: > Thanks for tip, Kenneth. > Please find proper formatted logs here: > https://pastebin.com/eXfNWBLu This looks like a discussion of a similar problem.? There are two suggested solutions: https://unix.stackexchange.com/questions/454004/smbclient-not-able-to-connect-to-after-upgrade-to-rhel7

Thank you Gordon for this tip but it does not solve my problem. From smb.conf: workgroup = NT4DOMAIN netbios name = NT4MEMBER I am able to connect to smb share from linux client: smbclient //NT4MEMBER/share1 -U NT4MEMBER\\user1 but from windows machine it is not possible. Correct command from linux client should be smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1 (user is from NT4DOMAIN, not from NT4MEMBER) This comman...

On 1/1/19 12:21 AM, Miroslav Geisselreiter wrote: > # wbinfo --ping-dc > checking the NETLOGON for domain[NT4DOMAIN] dc connection to > "nt4member.intranet.xx" succeeded Well, the host where you ran that command thinks that "nt4member" is the DC.? Do you see anything in your configuration file that might indicate why?? You haven't given us enough information to be much more use.

# wbinfo --ping-dc checking the NETLOGON for domain[NT4DOMAIN] dc connection to "nt4member.intranet.xx" succeeded Here is debug log from winbind: [15833]: request interface version (version = 30) [15833]: request location of privileged pipe [15833]: request interface version (version = 30) [15833]: request misc info [15833]: request netbios name [15833]: request domain name [15833]...

...39;d expect that your > system would work without any interactions with the DC. > I found some solution which solve only part of my problem and is not very "clean". When I run winbind with these options client which are member of my NT4DOMAIN are now able to mout smb shares from NT4MEMBER server: # winbindd -i -d 3 -S -n --option="netbios name"=NT4DOMAIN --option="ntlm auth"=yes option "netbios name"=NT4DOMAIN overwrites this option from smb.conf: "netbios name"=NT4MEMBER Nenertheless I am not able to mount smb shares from clients which a...

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

On 1/2/19 12:09 PM, Miroslav Geisselreiter wrote: > some parameters from smb.conf: > [global] > ??? workgroup = NT4DOMAIN > ??? netbios name = nt4member > ??????? security = domain > ??????? passdb backend = ldapsam:"ldap://ldap1server.intranet.xx > ldap://ldap2server.intranet.xx" I'm not sure it makes sense to use "security = domain" with an ldap passdb backend.? If you're using a real NT4 domain, then you...

Dne 2.1.2019 v 21:54 Gordon Messmer napsal(a): > On 1/2/19 12:09 PM, Miroslav Geisselreiter wrote: >> some parameters from smb.conf: >> [global] >> ??? workgroup = NT4DOMAIN >> ??? netbios name = nt4member >> ??????? security = domain >> ??????? passdb backend = ldapsam:"ldap://ldap1server.intranet.xx >> ldap://ldap2server.intranet.xx" > > > I'm not sure it makes sense to use "security = domain" with an ldap > passdb backend.? If you're usi...