similar to: ntlm_auth = NT_STATUS_NO_LOGON_SERVERS: No logon servers (0xc000005e)

Can anyone tell me what might be going on here? Thanks in advance David : Jan 9 22:02:15 dns1 winbindd[19219]: [2010/01/09 22:02:15, 0] winbindd/idmap.c:smb_register_idmap_alloc(201) Jan 9 22:02:15 dns1 winbindd[19219]: idmap_alloc module tdb already registered! Jan 9 22:02:15 dns1 winbindd[19219]: [2010/01/09 22:02:15, 0] winbindd/idmap.c:smb_register_idmap(149) Jan 9 22:02:15 dns1

Hello, I have problem with idmap configuration. I would like to use LDAP as backend for idmap in Samba+ADS environment, but i have following errors in log.winbindd-idmap: [2011/06/08 16:57:54.805575,? 0] winbindd/idmap.c:201(smb_register_idmap_alloc)????????????????????????????????????????????????????????????????????????????????? ? idmap_alloc module ldap already

All, After two days of googling, reading, swearing and cursing, I am finally admitting I cannot solve this one. I have three production FreeBSD servers running various network utilities (DHCP, bacula, zabix, syslog, rsync). These have been running fine for several years. As a primary Windows domain (accounting firm. Not much choice), I like to centralize all logins into AD which is currently

hi all, i'm not expert with Samba integration into domain. I did setup many servers acting with local auth that were running very fine. We've a Windows 2008 acting as Domain controller. So to not create more login/password to users, i decided to authenticate using Active Directory. The shares work, but sometimes users failed to access. The server is running Debian stable Lennny. The

Hello everyone I have a Debian Lenny running Samba 3.4.7 + OpenLDAP as PDC. I'm having trouble with Winbind. He logs so much messages that my disk is almost full! here is the log: Dec 13 16:18:14 fileserver smbd[10017]: [2010/12/13 16:18:14, 0] lib/util_sock.c:539(read_fd_with_timeout) Dec 13 16:18:14 fileserver smbd[10017]: [2010/12/13 16:18:14, 0]

Hi there I have samba-3.0.27a rolled out over a large number of servers, and every once in a while one of them will start failing to allow people to connect, with winbind reporting NT_STATUS_NO_LOGON_SERVERS, and ntlm_auth failing with "NT_STATUS_NO_LOGON_SERVERS: No logon servers". The same problem occurred with earlier versions too. I think I've tracked down the cause of the

Hello have configured samba to authenticate with an LDAP backend everything works fine including testing the configuration files until I start the net sam provision. Below is the error<http://www.tomshardware.com/forum/237835-50-samba-ldap-failing-create-domain-users-admins#>message I get lib/smbldap_util.c:310(smbldap_search_domain_info) smbldap_search_domain_info: Adding domain info for

Hello everyone, We've been running Samba for years, and with the exception of IDMAP, we've been very happy. Well, now we have a real need to keep this information in a shared DB, so I'm trying to set up the idmap_ldap plugin. I *think* I have lookups working correctly-- at least, I can see that Samba is contacting the LDAP directory. But since there's nothing actually

I have setup a test PDC with samba 3.4.7 on a fedora core 12 linux machine. I have setup two way interdomain trusts with a Windows 2008 domain. The domain and forest functional levels are Windows 2003. Since the samba machine is not emulating an Active Domain Controller, the Windows 2008 machine should think it is talking to an NT4 server. And since NT4-based domains don't use

Hi, We have just managed to get winbind behaving correctly in a Samba domain with Samba member servers with help from Sernet. It is now not adding spurious entries for the "own domain". However, a member server keeps trying to add group mappings that already exist in the LDAP idmap ou. This would not be a problem, apart from the fact that every time it fails adding an entry, the

As per earlier post, I was having problems getting trusts setup between my Samba domain (3.0.x PDC, 3.4.x BDC on Solaris 10) and two Active Directory domains (each in a separate forest.) One domain is a test Win 2003 PDC in native Win 2003 mode, the other is a Win 2008 system also in native Win 2003 mode. To summarize some of the progess- things work better if the Samba 3.4 is the PDC,

Hi, I am more or less following this tutorial Ldapsam Editposix = http://wiki.samba.org/index.php/Ldapsam_Editposix but can't quite get my domain to work. I think the issue is with the idmap part of the smb.conf but can't quite figure out what's wrong with it or what the correct format should be. My SMB.CONF file.... #interfaces = lo0 em0 127.0.0.1 bind interfaces only = no

Hi, I used to have a working Samba + Winbind configuration in ADS mode under FC4; Samba version was 3.0.14a-2. I joined a W2k domain, and winbind correctly returned the user information. krb5.conf and smb.cong have been modified according to Howtos and tutorials found on the net. One day Samba has been updated to 3.0.23a-1.fc4.1 and it stopped working. No modification has been done to the

On my test Samba PDC, I updated the krb5.conf file to add realm info for the Windows 2008. This seems to have resolved my "wbinfo" issue. "getent passwd" is still not working (I did update nsswitch.conf) but I suspect this is because of an idmap allocation issue. The syntax for idmap allocation in smb.conf seems to change between 3.0, 3.2, 3.3 and 3.4. I have also tried

Every few minutes windbindd posts an error message like: winbindd: ../source3/libads/ldap.c:552(ads_find_dc) winbindd: ads_find_dc: name resolution for realm 'XXX.CO' (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS where XXX.CO is the domain name of a company my company recently acquired and XXX_01 seems to be like they name of the DCs around here. I'm assuming

Hello all, after migration from 3.0.26a to 3.4.2 we get lots of the following messages in our winbind-idmap logfile. Has anybody seen this before? [2009/11/10 10:51:14, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module ldap already registered! [2009/11/10 10:51:14, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module tdb already registered! [2009/11/10

I am getting a lot of winbind errors in my logs on one server. Any idea's? Apr 7 10:32:19 pdc winbindd[8789]: [2011/04/07 10:32:19.062866, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) Apr 7 10:32:19 pdc winbindd[8789]: idmap_alloc module ldap already registered! Apr 7 10:32:19 pdc winbindd[8789]: [2011/04/07 10:32:19.063011, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) Apr 7

[2009/11/18 12:41:05, 1] winbindd/idmap.c:438(idmap_init_passdb_domain) Could not init passdb idmap domain [2009/11/18 12:41:05, 1] winbindd/idmap_tdb.c:214(idmap_tdb_load_ranges) idmap uid missing [2009/11/18 12:41:05, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module tdb already registered! [2009/11/18 12:41:05, 0] winbindd/idmap.c:149(smb_register_idmap) Idmap

Greetings list, This sounds sort of twisted but in its essence Windows ADS has an LDAP server too, so here is what I do hoping it'll work: 1. Install Utilities and SDK for UNIX-based application and Identity Management for UNIX on Windows server 2003, create a new OU named "idmap". 2. Configure smb.conf as per Samba HOWTO chapter 14 "IDMAP storage in LDAP using winbind"

hasm> Every few minutes windbindd posts an error message like: hasm> winbindd: ../source3/libads/ldap.c:552(ads_find_dc) hasm> winbindd: ads_find_dc: name resolution for realm 'XXX.CO' hasm> (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS hasm> How can I shut this thing up? I've also seen, not sure hasm> whether related, winbindd shooting up to