similar to: Upgrading 3.0alpha -> 3.0.0.rc2, error C000019b for old users only

Hello! I've run into a strange problem with samba-2.2.7a. I compiled it with --with-ldapsam on a Debian/Woody box, set up openLDAP 2.0.23 with all users and machine trust accounts and configured samba to using LDAP and being a PDC. Works ok so far, users may authenticate and use their shares. But they can not *always* log into the domain from NT4.0 workstations. Sometimes yes, sometimes

We have been using samba 2.2.7 for awhile now with ldap no problem. We are ready to move to Samba 3 though, and this is where the trouble begins. We do not have a domain set up. We have a few samba boxes and they just use the ldap servers to get their passwords from. (no roaming desktops or anything like that.) I did a bit of reading up and see that I need to run the convertSambaAccount script

I'm trying to get Samba on AIX 5.1 to work in appliance-like mode. I would like NT domain users to get automatically and persistently mapped to AIX/Unix users. This stuff seemed to work fine without much effort on Solaris 9, but AIX is a different story, and I'm new to AIX as well. AIX 5.1 doesn't use nss so winbind, in its current form, can't work. I saw a post from January

Hello, This is the 3rd time I'm sending the message. I've just upgraded from samba3-alpha23 to samba3.0.0 release. I'm running samba with an LDAP backend and I used the convertSambaAccount conversion script, and now the latest 3.0.0 ldap schema. The problem I have is that no Windows user can authenticate against their home directory, or any other machine. Authentication against the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use it at your own risk. The source code can be downloaded from :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use it at your own risk. The source code can be downloaded from :

I upgraded from Redhat 8 using LDAP 2.0.22 and Samba 2.28a to Fedora Core 1 .Reimported my LDAP Schema into the new version of Ldap but when attempting to run the following .. I recieve this error.. Any ideas? ./convertSambaAccount --input /usr/share/doc/samba-3.0.0/LDAP/txt.ldif --output new.ldif --sid S-1-5-21-387053420-3 --changetype modify Can't call method "get_value" on an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We've just posted another snapshot of the SAMBA_3_0 cvs tree for download. This is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/alpha/ The uncompressed tarball and patch file have been signed using GnuPG. The Samba public key is available at

I've been using Samba 2.x authenticating UNIX and Samba users to OpenLDAP 2.0.x fro quite some time. Now I need to upgrade OpenLDAP to 2.2.x and Samba to 3.0.x. Although I've been using OpenLDAP with the old samba schema to authenticate Samba users, I did not have a PDC set up. Now when I try to use the convertSambaAccount script to move to the new Samba schema it says "You

Hi everyone! im having problems with Samba 3.0.4 My PDC is samba+openldap+nss+pam+smbldaptools All work fine (posix account and logins in Win9x workstations) I can join in to my domain with WinNT4 but i can't login! Im get always this message: The system can not log you on (C000019B). Please try again or consult your system administrator. I have read the documents about this error around

I have upgraded recently from alpha22 to rc1. While trying to access printer properties from XP, i'm getting error "Runtime Error! program: C:\WINDOWS\explorer.exe abnormal program termintation". Printing is not possible as well. This error is reproducable from any WinXP computer on network on any shared by samba printer. Printers are HPLJ2100, drivers are latest PCL6 downloaded

Hello! I've got into problems with simultaneous access to files on samba server. Two (or more) people from different computers may open the same file and may independently change it (with openoffice, for example). Certainly, this is not the expected behavior. If the file is shared on windows machine, when the first user opens it, he gots RW permission, while the next one(s) may open this

Is there a how-to out there which could walk me through upgrading a working Samba 2.2.7/Openldap server to Samba 3.0.3/Openldap server? I can get Samba 3.0.3 and Openldap to work with a new install however when I attempt to import my old LDAP database I have to change the user's password and rejoin the workstations to the domain. Do I have to do this or should it be pretty seamless? I

Dear all, we have been using samba as PDC with ldap for over a year without any problems. Now we are trying to switch to a another operating system version and another samba version and have big problems with our windows clients (NT, 2000 and XP). Some have problems logging on to the domain (error C000019B), others give the net helpmsg 3678 (problems saving profile) and/or the netlogon script

It looks as if 2-way trusts are working between Samba and PCNL and between Samba/NT4. The one exception seems to be logging in as Samba/myname on the ENT4 PDC. I had created a ENT4/myname account. I had forgotten to add SAMBA/myname to the local users group on the ENT4 PDC before trying to the ENT4 PDC as SAMBA/myname. If I log in as SAMBA/anothername it is OK. This isn't real show

I found part of the prob may have been that I didn't join the samba PDC to its own domain. # net join samba -U root Joined domain SAMBA Now, commands like "wbinfo -t" and "wbinfo -m" indicate that the domains are trusted. Also, I can run "net rpc samdump" to dump the NT4 domain info (but not the PCNL domain.) If I try to log in to the NT4 server as a

hi, i'm trying to migrate my samba 2.2.8a pdc to 3.0.12 pdc. I'm using ldap and i have already migrated all the data. Also i have executed convertSambaAccount for the new schema. My problem is that I cannot set the old SID (samba 2.2.8) to the new samba 3.0.12 for that the clients can authentificate to pdc server. samba2.2.8> smbpasswd -S LDAP Successfully set domain SID to

PLEASE!! can somebody help me? I need much these! ----- Original Message ----- From: "Henrique" <henrique@astuto.com.br> To: "Samba Samba" <samba@lists.samba.org> Sent: Monday, June 21, 2004 3:35 PM Subject: Error C000019B > Hi everyone! im having problems with Samba 3.0.4 > > My PDC is samba+openldap+nss+pam+smbldaptools > > All work fine (posix

Hello, I've been using samba-3alpha22 as a PDC authenticating against LDAP. I am trying to add NT Groups using the smbgroupedit utility. It seems to me that smbgroupedit always looks in /etc/group and does not take into account the ldap configuration options specified in smb.conf. The relevant ldap entries are: passdb backend = ldapsam:ldap://ebola/ ldap suffix="dc=datasoft,

Hi! I've been trying to find a solution to a printer problem. All I found is a message posted to this list about a year ago, which describes about the same problem (the message is in the end of this mail). So, each time I try to print from windows 2000 or XP I get this error message: Microsoft Visuall C++ Runtime Llibrary Program: C:...Winword.exe Abnormal program termination I have three