search for: lookup_name_smbconf

On Fri, 22 Feb 2019 14:34:49 +0100 Hans Schou via samba <samba at lists.samba.org> wrote: > Hi > > I have a Red Hat 7.6 server with samba-4.8.3 which report > lookup_name_smbconf failed when running "smbclient -L" from another > console on the same server. smbclient works fine on an old server > running Suse and samba version 3 and thew the > user. > > Any ideas of where to look or what to try? > > I got this in the logfile: > > # gre...

Hi I have a Red Hat 7.6 server with samba-4.8.3 which report lookup_name_smbconf failed when running "smbclient -L" from another console on the same server. smbclient works fine on an old server running Suse and samba version 3 and thew the user. Any ideas of where to look or what to try? I got this in the logfile: # grep "^ " /var/log/samba/log.172.23.10...

On Fri, 22 Feb 2019 17:12:56 +0100 Hans Schou via samba <samba at lists.samba.org> wrote: > On Fri, 22 Feb 2019 at 14:51, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > Its working now with smbclient from Linux without using password. > Thanks! On Windows I have to use fqdn but it might be that the search > path on Windows is wrong. (the word

On Fri, 22 Feb 2019 at 17:27, Rowland Penny via samba <samba at lists.samba.org> wrote: > > [global] > > log level = 3 > > unix charset = UTF8 > > dos charset = ISO-8859-1 > > workgroup = ACME.DOM > > Sorry, but you cannot use a workgroup with a dot in it. > I tried to remove ".DOM" but then I can not start

On Fri, 22 Feb 2019 at 17:46, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 22 Feb 2019 17:41:50 +0100 > Hans Schou via samba <samba at lists.samba.org> wrote: > > > On Fri, 22 Feb 2019 at 17:27, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > > > [global] > > > > log

On Fri, 22 Feb 2019 at 14:51, Rowland Penny via samba <samba at lists.samba.org> wrote: Its working now with smbclient from Linux without using password. Thanks! On Windows I have to use fqdn but it might be that the search path on Windows is wrong. (the word "search" in resolv.conf - I don't know what that is called on Windows) It was a lot changes to make. I just copied the

...0xb7733b95] #6 /usr/sbin/smbd [0xb7c4c00d] #7 /usr/sbin/smbd(pdb_default_getgrnam+0x90) [0xb7c486d7] #8 /usr/sbin/smbd(pdb_getgrnam+0x26) [0xb7bc10fb] #9 /usr/sbin/smbd(lookup_global_sam_name+0x1ee) [0xb7ebc6fd] #10 /usr/sbin/smbd(lookup_name+0x2a5) [0xb7bc6188] #11 /usr/sbin/smbd(lookup_name_smbconf+0xfb) [0xb7bc6c52] #12 /usr/sbin/smbd(token_contains_name_in_list+0x4a2) [0xb7e254b2] #13 /usr/sbin/smbd(is_share_read_only_for_token+0x9a) [0xb7e25559] #14 /usr/sbin/smbd(change_to_user+0x25a) [0xb7acb31a] #15 /usr/sbin/smbd [0xb7aecd82] #16 /usr/sbin/smbd(make_connection+0x796) [0x...

...ot have the ability to add the user/group information to AD directly at this time. Does anyone know exactly what the following error message "means"? It shows up every time these symptoms occur, and if I could understand why the lookup fails, I might be able to prevent the issue. "lookup_name_smbconf for CLIENTHOSTNAME$ failed" ________________________________ From: samba <samba-bounces at lists.samba.org> on behalf of Rowland penny via samba <samba at lists.samba.org> Sent: Friday, August 30, 2019 12:52 PM To: sambalist <samba at lists.samba.org> Subject: Re: [Samba] f...

...to do that, things seemed to stabilize again, but we are still seeing this occur every other day or so at seemingly random times. Most of our users on the clients are using Stata16 to access data on the mapped drive. The only additional clue is from the log.clienthostname file and is: ""lookup_name_smbconf for clienthostname$ failed". This appears to show the client trying to connect as itself and not a specific user. I cannot confirm if this is actually related to the core issue or simply a coincidence. We are running samba v4.8.3 on Centos v7.6.1810 and our clients are Windows Server 2016....

I left in some of the parameters I've been testing commented out. Interestingly, we've noticed another client triggering the same type of symptoms every morning at around the same time. Those symptoms being a line 'lookup_name_smbconf for COMPUTERNAME$ failed' and a flood of failed connection attempts from the same client. The issue seemed to resolve itself after a few minutes in this last case. I happened to be watch smbstatus at the time it occurred. [global] netbios name = service-samba4 #socket option...

...e way they are. I can certainly edit per your suggestions and see if it helps at all. I have noticed that as people are getting window pop-ups asking them to enter their credentials (which they shouldn't get of course), I'm seeing a corresponding error in the log.smbd file that says "lookup_name_smbconf for <domain>\<user> failed", so I'm trying to see if I can find anything more specific about what might be causing that issue. Also, I do have samba-winbind-4.8.3 installed and winbind appears to be running (ps -ef |grep winbind returns two lines of "/usr/sbin/winbindd -s...

...e share, correct? Instead, when I try to access the share, I get prompted for credentials, and then get denied. The following error is displayed in SMB logs: ==> /var/log/samba/__ffff_172.26.103.175.log <== [2012/12/07 14:57:18.622794, 1] auth/auth_util.c:848(create_token_from_username) lookup_name_smbconf for DOMAIN\testuser failed DOMAIN\testuser is a member of DOMAIN\testgroup. Any help would be greatly appreciated! Thanks, Josh

...t, things seemed to stabilize again, but we are still seeing this occur every other day or so at seemingly random times. Most of our users on the clients are using Stata16 to access data on the mapped drive. > > The only additional clue is from the log.clienthostname file and is: ""lookup_name_smbconf for clienthostname$ failed". This appears to show the client trying to connect as itself and not a specific user. I cannot confirm if this is actually related to the core issue or simply a coincidence. > > We are running samba v4.8.3 on Centos v7.6.1810 and our clients are Windows Serv...

...db95] #6 /usr/sbin/smbd [0xb7cf5fad] #7 /usr/sbin/smbd(pdb_default_getgrnam+0x90) [0xb7cf2677] #8 /usr/sbin/smbd(pdb_getgrnam+0x26) [0xb7c6b0eb] #9 /usr/sbin/smbd(lookup_global_sam_name+0x1ee) [0xb7f6666d] #10 /usr/sbin/smbd(lookup_name+0x2a5) [0xb7c70178] #11 /usr/sbin/smbd(lookup_name_smbconf+0xfb) [0xb7c70c42] #12 /usr/sbin/smbd(token_contains_name_in_list+0x4a2) [0xb7ecf452] #13 /usr/sbin/smbd(change_to_user+0x3a6) [0xb7b75466] #14 /usr/sbin/smbd [0xb7b96d6a] #15 /usr/sbin/smbd(make_connection+0x796) [0xb7b97c2f] #16 /usr/sbin/smbd(reply_tcon_and_X+0x404) [0xb7eeb9...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Where does he get those wonders toys?" -- The Joker (Batman 1989) ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is

/etc/samba/user_and_group_map.txt contains Windows username/group to linux username/group mappings. In our setup, all users exist in ldap, as do the directory groups, but the linux user and group information (namely uid/gid) do not. This has been setup such that the users connect to samba as the windows username (ex. PRODUCTION+user1) for an authroized group (PRODUCTION+group1), but the files

Thank you Rowland! I guess that's part of my confusion, I'm not sure how to best debug where Centrify ends and Samba begins. But if these log.smbd errors indicate Centrify vice Samba, I'm good with that. My global smb.conf is (didn't bother with the commented out stuff): [global] security = ADS realm = <our domain name> workgroup = <our workgroup name> netbios name =