similar to: Some errors importing accounts from NT4 PDC with net vampire

Hi I have folowed this guide http://www.enterprisenetworkingplanet.com/netos/article.php/3457461 to import users from my NT4 domain to a debian sarge with samba 3.0.14a Everything runs fine till the net rpc vampire command, some users give an error others are imported fine. I don't see any problem on this users configuration in the NT4 server, here is part of the output: thanks.

Hi, i've just migrated from nt4 to samba 3.0.10-1.4E.9 with tdbsam, running on Centos 4.4 The net rpc vampire went fairly smoothly. Now that samba is running as the PDC (nt4 machine has been laid to rest) i am having trouble renaming computers in the domain. If i try this from the windows workstation (XP Professional) i get access denied. I use "root" or administrator which is

The exact configuration mentioned below used to work on rhel3, and when updated to rhel4 it stopped working... when visited the samba log file, there was this error : useradd: invalid user name 'wpvm01$' rpc_server/srv_samr_nt.c:_samr_create_user(2272) could not add user/computer wpvm01$ to passdb. Check permissions? [2005/03/17 07:42:27, 0] passdb/pdb_tdb.c:tdb_update_sam(609)

Hi all ! This is a patch for Group mapping bug #1 reported here : http://lists.samba.org/archive/samba-technical/2004-January/034057.html It activates users' primary group SID update when adding/modifying/deleting a group mapping. It patches utils/net_groupmap.c (net_groupmap_add, net_groupmap_modify, net_groupmap_delete) and can be applied to samba-3.0.2rc1. net_groupmap_add : Scan users

Running Samba 3.0.5-0 (backports) and Debian 3.0. I keep seeing this in my syslog, and was wondering what it meant. I can't seem to find a solution using google. Aug 6 15:45:13 rivendell smbd[3209]: [2004/08/06 15:45:13, 0] \ passdb/pdb_tdb.c:tdb_update_sam(652) Aug 6 15:45:13 rivendell \ smbd[3209]: Unable to modify TDB passwd ! Error: Record does not exist Aug 6 15:45:13 rivendell

> I have few Windows2000 Pro samba domain members which logon to the domain > without any obstacles. Recently I decided to upgrade all client workstations > to WindowsXP SP2. Fresh copy of WindowsXP joined domain properly but when I > tried to logon as usual it accepted password and shut down after a while > (logs of samba confirm that workstation logged on). Windows claims that

I am replacing an old NT4.0 Server with a debian 4.0R1 etch Linux server (samba 3.0.24). This was with a completely fresh install of debian. My smb.conf is pretty simple: [global] workgroup = BUTLER netbios name = STAR3 passdb backend = tdbsam domain master = No domain logons = Yes os level = 33 add user script = /usr/sbin/useradd -m '%u' delete

Using samba 3.5.12 on aix 6.1 when I set "server signing = mandatory" nothing can connect to my server. Included the smb.conf followed by errors showing up in the level 10 debug output. Thanks, >cat /usr/local/samba/lib/smb.conf [global] workgroup = somename netbios name = someserver server string = somename Samba Server %v security = user

Hi, i was the one who had problems with the start_tls function. I applied the patch yesterday. But now the compiling doesn't work anymore. This is what happens : --------snipp---------- [Lots of compiling output cut away] Linking bin/smbd passdb/pdb_ldap.o: In function `pdb_setsampwent': passdb/pdb_ldap.o(.text+0x1730): multiple definition of `pdb_setsampwent'

Hello, During a re-start of Samba I got the following error: [2006/03/22 12:36:14, 0] passdb/pdb_tdb.c:tdbsam_tdbopen(196) Unable to open/create TDB passwd [2006/03/22 12:36:14, 0] passdb/pdb_tdb.c:tdbsam_getsampwrid(490) pdb_getsampwrid: Unable to open TDB rid database! The result is a new password file. The second problem is that after creation of the users and a new join of the

the following problem occurs when using samba 2.2.4 or 2.2.5 with ldap support as PDC: any time when a user logs on he is asked to change his/her password. whether he change it or not he will be asked again next time he logs on. this is annoying. the reason is, that the LDAP attribute 'pwdMustChange' is not updated at all. the easiest way to solve this to set the attribute to the

Hi, When I upgraded from Fedora 22 to Fedora 25 my Win10 box lost the ability to connect to shares on the F25 box. The F25 box can still access shares on the Win10 box. F25 is currently running Samba 4.5.13 and I have a simple workgroup setup. Let's call the Win10 box 'fred' and the F25 box 'ethel'. When fred tries to access a share on ethel, I am prompted for username and

Hi, debian etch + samba 3.0.24-6 on 2.6.18-4-amd64. Today I got a panic email from samba. [2007/08/14 08:46:55, 0] smbd/nttrans.c:call_nt_transact_ioctl(2338) call_nt_transact_ioctl(0x9005c): Currently not implemented. [2007/08/14 09:25:05, 1] smbd/service.c:make_connection_snum(950) c601356 (...) connect to service FD_Systeme initially as user theckne (uid=5053, gid=1068) (pid 16275)

Hi everyone. I have a problem when using samba together with usrmgr. When adding a global group I get an error message. The group is still created. You can't see before you refresh but that's a minor detail. In the logfiles May 10 17:47:27 lanchester smbd[28424]: [2005/05/10 17:47:27, 0] passdb/pdb_tdb.c:tdbsam_tdbopen(195) May 10 17:47:27 lanchester smbd[28424]: Unable to

Hi. I've tried Samba 3.4.3 and it upgraded my passdb.tdb file. After testing I concluded that I'm not going to upgrade to 3.4.3 yet, because 'getent passwd' was broken in recent BlastWave Solaris packages: http://wiki.blastwave.org/forum/viewtopic.php?f=5&t=447&start=0 Now, after I downgraded the Samba back to 3.0.32, client connections started to malfunction. I saw

Hi there, I'm trying to import a smbpasswd-file into a Samba 3.0 installation on Debian Sarge using tdbsam as sole passdb backend. Copying pdbedit's documentation I used pdbedit -i smbpasswd:/root/smbpasswd.old The error message returned was tdb_update_sam: Failing to store a SAM_ACCOUNT for [foo] without a primary group RID where foo is the username to be imported. This message was

Hi, I'm running Samba as a PDC on a Debian Etch machine (3.0.24-6etch9). It's been some time (months, maybe 1 year) since I last added a new machine to the domain, but I'd need to do it today and I'm getting an error: #>pdbedit -a -m Woodstock-VMXP tdb_update_sam: struct samu (woodstock-vmxp$) with no RID! Unable to add machine! (does it already exist?) The machine does NOT

Hi all, I use tdbsam backend. When I create a box for win2k machine: # pdbedit -a -m -u machine$ tdb_update_sam: SAM_ACCOUNT (machine$) with no RID! Unable to add machine! (does it already exist?) What is wrong? Other failer message: Unable to open TDB rid database! Regards, Roland

I have problem adding users after I set up a goupmap. Before there was no problem. net groupmap ntgroup=Users unixgroup=users Users (S-1-5-32-545) -> users useradd pesho -g users pdbedit -a pesho new password: retype new password: tdb_update_sam: Failing to store a SAM_ACCOUNT for [pesho] without a primary group RID Unable to add user! (does it already exist?) pesho of cource doesn?t exist

I have problem adding users after I set up a goupmap. Before there was no problem. net groupmap ntgroup=Users unixgroup=users Users (S-1-5-32-545) -> users useradd pesho -g users pdbedit -a pesho new password: retype new password: tdb_update_sam: Failing to store a SAM_ACCOUNT for [pesho] without a primary group RID Unable to add user! (does it already exist?) pesho of cource doesn?t exist