Displaying 20 results from an estimated 1000 matches similar to: "upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap"
2018 Dec 21
0
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
I am sorry logs are bad formatted I am trying again and hope it will be
better. Otherwise lokk at link bellow or tell me how to send logs correctly.
Mirek
21.12.2018 v 13:19 Miroslav Geisselreiter:
> Originally I posted this question at CentOS forum 20.12.2018.
> https://www.centos.org/forums/viewtopic.php?f=48&t=69193
>
> Hi all,
>
> I am not able to mount samba shares
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"?
2019 Jan 01
0
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
# 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]:
2018 Dec 30
2
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
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
2018 Dec 31
0
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
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
2019 Jan 07
1
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
Dne 5.1.2019 v 0:46 Gordon Messmer napsal(a):
> On 1/3/19 11:46 PM, Miroslav Geisselreiter wrote:
>>
>> Previously I deleted all files from /var/lib/samba, than set ldap
>> admin password:
>> smbpasswd -W
>> Than I re-join DC, it did not help.
>
>
> Shame.? I'm not really sure what else to try, beyond my previous
> suggestion that it doesn't
2019 Jan 02
1
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
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
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
2019 Jan 03
2
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
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"
>
2017 Jun 12
2
'winbind use default domain' doesn't appear to work with ntlm_auth
Hi everyone,
We just upgraded Samba from 4.4.5 to 4.6.5 and appear to be experiencing a problem with authentication, when the RPC domain is not supplied as part of the username.
I have two scenarios where this has cropped up:
RADIUS authentication using ntlm_auth
Apache HTTP using mod_auth_ntlm_winbind
RADIUS authentication:
We use the freeRADIUS 'mschap' module to provide
2019 Apr 25
2
Win7 client error after classicupgrade from S3 to S4
Hi.
We're trying to upgrade an old NT domain to AD. It's our second upgrade, and while the first was successfull this one has raised some issues for existing Windows 7 clients.
If we disconnect the computer from the domain and join it back to the new S4 AD it works. Existing clients throws this error in Samba:
Kerberos: AS-REQ b1rd42nbtmp648$@NT4DOMAIN from ipv4:10.0.0.42:49472 for krbt
2019 Jan 02
0
upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
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
2018 Nov 29
2
log.wb-LXDOM
Hallo at all
after classicupgrade in my production environment, i found many of this
alert in log.wb-LXDOM
[2018/11/29 12:07:55.180009, 3]
../source3/winbindd/winbindd_rpc.c:272(rpc_name_to_sid)
name_to_sid: LXDOM\SPECOLA8$ for domain LXDOM
[2018/11/29 12:07:55.181274, 3]
../source3/winbindd/winbindd_samr.c:659(sam_sid_to_name)
sam_sid_to_name
[2018/11/29 12:07:55.837701, 3]
2017 Jun 14
1
'winbind use default domain' doesn't appear to work with ntlm_auth
Hi Rowland,
I did enable NTLMv1 to provide necessary support for pppd for PPTP VPN connections and that's working as expected. I however do not find any release notes pertaining to 'winbind use default domain = yes' no longer working on a Samba DC. The Samba man pages appear to detail options which apply to winbindd (https://www.samba.org/samba/docs/man/manpages/winbindd.8.html),
2016 Nov 13
1
smbd does not start NT_STATUS_NO_MEMORY
I'm trying to set up a simple test server, but smbd fails to start:
[2016/11/14 00:21:24, 0] ../source3/smbd/server.c:1241(main)
smbd version 4.2.10-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2014
[2016/11/14 00:21:24.881448, 0]
../lib/util/charset/convert_string.c:391(convert_string_talloc_handle)
convert_string_talloc: Conversion not supported.
[2016/11/14
2013 May 27
2
New Samba Error We Have Not Seen Before
We have about 40 samba servers in our domain. The two newest ones are throwing an error we've never seen before.
[root at vmhost06a samba]# net join
Enter root's password:
dos charset 'CP850' unavailable - using ASCII
convert_string_talloc: Conversion not supported.
Failed to join domain: failed to lookup DC info for domain 'MYCHARTS.MD' over rpc: Memory allocation error
2019 Nov 14
6
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
Upgraded to Samba 4.11.2 and I?ve now too started seeing the message:
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
A lot. I modified the source in source3/locking/share_mode_lock.c a bit in order to print out the values of the service path, smb_fname & old_write_time when it fails and it seems they are all NULL?
[2019/11/14 14:24:23.358441, 0]
2015 Feb 27
3
samba-tool time
On 27/02/15 11:45, L.P.H. van Belle wrote:
> Ok.. very strange ..
>
> for me :
> ERROR(runtime): uncaught exception - Connection to SRVSVC pipe of server 'internal.domain.tld' failed: NT_STATUS_NONE_MAPPED
>
> for peter:
> one works, one :
> ERROR(runtime): uncaught exception - Connection to SRVSVC pipe of server 'ulysses.home.serbe.ch' failed:
2019 Nov 29
4
get_share_mode_lock:, get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with Samba 4.11.2
Hello all,
after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in
our logfiles:
2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28
20:40:44.886615, 1]
../../source3/locking/share_mode_lock.c:597(get_share_mode_lock)
2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock:
get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
There are no symptoms accept
2014 Jun 17
2
net rpc join fails with NT_STATUS_NONE_MAPPED
After the join is attempted I am returned the following
Could not initialise lsa pipe
error looking up rid for user user$: NT_STATUS_NONE_MAPPED
Unable to join domain xxxx.
Running on freebsd 9.0 with samba-3.4.17
I haven't seen much in the logs. Everything was working fine before a reboot
LEGAL NOTICE This email and any files transmitted with it are confidential and intended solely for