similar to: Can't add machine account with 3.0.0; ldapsam backend

Resending as I'm no closer to a solution and really would appreciate any help that anyone has to offer. Hi, Please cc me on any replies as I'm not subscribed. First, I've seen reference to this problem on the list but no solution, eg.: http://marc.theaimsgroup.com/?l=samba&m=106032316504352&w=2 Platform is: # uname -a Linux allanon 2.4.21-xfs-aihplc3 #1 SMP Thu Aug 21

Hi folks. I discovered this odd behaviour a few days ago while playing with SAMBA_3 for the first time. The following points apply to samba-3.0.0beta and to cvs-20030807. 1. (tested with tdbsam) If I create a user entry with pdbedit, the domain name field is not set to the domain specified in the configuration file. For me it's getting set to the local machine name. If I logon to a

Hello, Im using samba-3.0.0rc4 with ldapsam. adding users works fine but when i try to add a machine account i alway get this error: pdc:/usr/bin# pdbedit -v -a -m -u test_pc ldapsam_modify_entry: Failed to add user dn= uid=test_pc$,ou=Systems,dc=ovid,dc=evva,dc=com with: Object class violation object class 'sambaSamAccount' requires attribute 'sambaSID'

Please help, I am experiencing a weird error when trying to join a winXP Pro workstation to my samba3 + LDAP Domain. When I specify the account to on my system that has uid 0, I receive a user account cannot be found error. Now I know this isnt the case since I can browse the samba server with this account. Note: it is in tdbsam not ldap When I look for the machine account in the ldap

Hello, I already worked with Samba (3.0.?) several month now on my NSLU2 with SlugOS BE. A few days ago the version was updated to 3.2.0 and no connection was possible afterwards. I searched the net but without relevant hits. I've created a new config file from scratch but got the same error again: root@LKG65AAA4:~$ netstat -an |egrep ':(137|138|139|445)' netstat: no support for

Hi there, Im using for long time winbind + squid for my proxy server and it has been working very good... No problems at all. Some months ago, I decided to get rid of Netbios protocol and start to use only dns for name resolution on my domain. That's when my problem begin. All my windows servers and workstations are doing fine without netbios but I cant get winbind to work without

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I run a ldap backednd smaba 3.0.21c domain. I have 1 PDC, and 6 BDC's. On all the BDC's I can run 'pdbedit -Lw' but I get an error on the PDC. I turned the debuging up to 5, here's the output: pdbedit -Lw INFO: Current debug levels: all: True/5 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0

I have been trying to access a personal share being hosted by my schools netapp server and have been unable to do so using both version 3.04 and version 3.06 of samba. I have read the mailing list archives and found one set of posts related to the problem however there was no solution posted, so I am asking if anyone knows how to solve this problem. The previos posts that I am talking about are

I have the problem with smbclient -L ... This is a level 50 debug message [2004/02/23 10:45:00, 5] lib/debug.c:debug_dump_status(359) INFO: Current debug levels: all: True/50 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0 rpc_parse: False/0 rpc_srv: False/0 rpc_cli: False/0 passdb: False/0 sam: False/0 auth: False/0 winbind:

Thanks for your help in adance !!! I work with SAMBA HEAD since alpha24. I have running a BDC, PDC, Printserver on 3 separate pc's. In my domain is integrated a nativ w2k Fileserver ( Dell Nas PowerVault 725 ) for fileserving. Passwords are held in LDAP on every (Linux) machine pam-ldap works. Every thing was fine before the last update to BETA 3. Problem : I was updating from BETA 2 to

Hallo, I have an old samba-cups printserver (debian woody), connected to the domain through winbind,?that I must replace now. I installed a new samba-cups server on a sarge machine. Windbind works, I can get all users and groups. I copied the generic windows postscript driver files as in cupsaddsmb-manpage described to /usr/share/cups/drivers (tried also adobe drivers) Also tried the same

I am trying to vampire the account database from my NT 4 DC (that has SP6A installed). The DC's name is nemesis. The samba computer's name is mjollnir. The directions seem trivial: 1.) Join the Domain as a BDC with: net rpc join -S nemesis -W WHSD -U Administrator this worked fine and I can see the computer listed in server manager with type "Windows NT Backup" 2.) Run

Hi List, We have a problem in connecting ADS server from SAMBA. Whenever we try to contact the ADS server from the Samba its giving error as LDAP_NO_RESULTS_RETURNED. We have varified the code also, in the code also its giving three possibilities to raise that error message, I am pasting the portion of code here, File name: libads/ldap.c Function name: ads_server_info Code snippet

Hi I can't get a Windows 2000 SP4 client login on my PDC (SAMBA SERVER). Here are some infos about the server Samba version 3.0.2pre1 running Suse 8.2 with a OpenLDAP server version 2.1.12, nss_ldap and pam_ldap. I constantly get the message : User / Password is wrong from the client. The root is created.Here are the debug messages I get, starting by the LDAP and SMBD logs: ###log.ldap###

Hi! I am seeing other users with the same problem as I have. My samba also fails to add machine accounts. It seems to me if it didn't even try. If I use some other script (pdbedit, smbldap-tools) than smbpasswd it manages to add the account but still fails to authenticate within the same session. If I try again the machine account exists and authentication goes ok. server:~# smbpasswd -a -m

Hello everybody, I am trying to keep my samba pdc working with windows 7 pro clients. After my upgrade: 2016-12-15 15:10:16 upgrade samba:amd64 2:3.6.6-6+deb7u7 2:3.6.6-6+deb7u10 Some of the Windows 7 client can not login anymore and respond with: The trust relationship between this workstation and the primary domain failed Changing the setting client use spnego = no will make the Windows

Greetings. Since this is my first post to this list, hello everyone. Here's an issue concerning the ldapsam backend. I'm having a problem with the "ldap user suffix" param not being honored as expected. Specifically, when a user logs on, the "ldap user suffix" is ignored and the ldapsam backend attempts to lookup the user doing a full subtree search in the context

On 08/03/2016 06:30 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> [alice at pern ~]$ ldd /usr/bin/curl |grep crypto >> libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f4524390000) >> libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f45234ca000) > > What do the following show: > > ldd /usr/bin/curl

On 08/03/2016 06:13 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> Something in the curl build will always link the binary against >> OpenSSL if the openssl-lib package is present, and will always link >> the library against OpenSSL if any TLS option is enabled in the >> configure. > > No, it doesn't. You can

Hi, Michael Felt wrote on Mon, Aug 20, 2018 at 05:00:17PM +0200: > ./nl_langinfo > setlocale -> "C" > nl_langinfo -> "ISO8859-1" Thanks, that is helpful. So i think i was wrong and Damien was right. This means that OpenSSH returns truncated messages when non-ASCII bytes occur in them, even when the user requests LC_CTYPE=POSIX. That's not good. While