similar to: corrupt tdb problems

We have a problem with our setup that exposed another problem in winbindd. Setup: Samba 3.0.1, openLDAP 1.2.23 for idmap backend using port 1389, security=ads (w2k). All works after we get the daemons started successfully. The first issue has to do with the initial setup of both a Samba server [smbd, nmbd, winbindd, slapd], and a Samba client [just nmbd and winbindd]. We do the

Hi all This one has me baffled - leading me to beleive it could be a bug similar to https://bugzilla.samba.org/show_bug.cgi?id=2695 I am running samba 3.0.20b on debian unstable and am having problems with some users not resolving properly using winbind. wbinfo -u shows all users on the system, no problem wbinfo -a user%password works for any user getent passwd shows most but not all users

Greetings, I'm new to Samba and I'm wondering where I went wrong.... My setup: Two FreeBSD 5.1 machines Samba 3.0.1r2 from ports collection One tdbsam domain controller and one member server - domcon and memsrv My problem: I've been working on this for a few days and still scratching my head. I can view the base directory of the member server (only as root). But when I try to

[CC to Debian package maintainer] Hi there, I'm still experiencing this worrysome tdb corruption even after I upgraded to 2.2.5. I built this package myself from the officially released 2.2.5 source. Here's a log snippet: Aug 3 11:15:04 Server smbd[23307]: [2002/08/03 11:15:04, 0] tdb/tdbutil.c:tdb_log(492) Aug 3 11:15:04 Server smbd[23307]: tdb(/var/run/samba/connections.tdb):

Hi there, isn't there really anybody who can give hints about this problem? Thanks, Ralf ==================BEGIN FORWARDED MESSAGE================== >From: "Ralf G. R. Bergs" <rabe@RWTH-Aachen.DE> >To: "samba@lists.samba.org" <samba@lists.samba.org> >Cc: "Eloy A. Paris" <peloy@debian.org> >Date: Sat, 03 Aug 2002 12:19:24 +0200

I'm running Samba 3.0.11. Compiled with: ./configure '--with-ads' '--with-pam' '--with-winbind' '--with-smbmount' '--with-shared-modules=idmap_rid' It configured, make and make installed fine. I configured the idmap_rid using the following directives in the smb.conf. ; IDMap Stuff idmap backend = idmap_rid:<DOMAINNAME>=500-100000000

Hello everyone! We're using samba-3.0.2rc2 with OpenLDAP-2.1.27, cupsys-1.1.20final-cvs200403 and a Samsung printer. Printing was working fine but yesterday all of a sudden it stopped working. The error message on the windows machine was: "A StartDocPrinter call was not issued". On viewing samba logs for the machine, we got following error:

I am running Ubuntu with LTSP authenticating to ADS on a Windows 2003 server SP1. My windows side of the network is running fine. The Linux terminals are not able to login all users... weirdly, some can, some can't. In my log.winbindd-idmap file, I get a slew of entries similar to this: [2006/09/25 22:54:21, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/lib/samba/winbindd_idmap.tdb):

Guten Tag Samba-List, after updating my Linux-Server from Debian Etch to Lenny, some of my workstations (W2kSP4) couln't log into the domain. I removed the machines from the domain, changed the name, created a new machine-account, but I still can't add the machine to the domain. My /etc/smb.conf (see below the logfile) is unchanged since Debian Etch. Perhaps someone

High I'm using samba in my private network since 1 year. Since yesterday I fi nd the mesg in the appendix when I trie to print. File transfer works fine, you find all printers but its not possible to print anything. Where to search ? Thanks a lot Bernd -------------- next part -------------- [1995/12/08 12:52:10, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/lib/samba/printing.tdb):

Hi everyone, Our system is a Debian GNU/Linux box running Linux kernel 2.4.17-xfs and Samba 2.2.3 (from the 2.2.3-5 package from Sid), built using gcc-3.0.3. With Samba 2.2.2 we hit certain tdb errors where make_connection would reject connections arbitrarily. Supposedly this was fixed using 2.2.3 so we upgraded right away (thankfully we do only have Windows 95, 98 and ME clients so we

Suddenly, today, my wife's Windows 95 machine can't print to the network printer on my Linux machine. It complains that "there was an error printing to \\posh\lp ... There was a problem printing to the port." The error 1st occurred (coincidentally?) after I had upgraded the kernel from 2.4.18 to 2.4.19. But rebooting to 2.4.18 has made no difference. We're running smbd

Can't print from client computers: I tailed the /var/log/samba/log.phong (note phong is a windoze client) and got: [2004/02/10 12:10:20, 0] tdb/tdbutil.c:tdb_log(531) tdb(/var/cache/samba/printing.tdb): rec_free_read bad magic 0x0 at offset=1905 6 [2004/02/10 12:10:20, 0] tdb/tdbutil.c:tdb_log(531) tdb(/var/cache/samba/printing.tdb): rec_read bad magic 0x0 at offset=17964 Any help will be

I've had a consistent problem with Samba from 2.2.1 onwards, maybe even before then, I'm not sure when it started. Anyway, Samba will randomly stop responding to any requests, although it usually occurs after transfering large amounts of data (1 GB+). To get around the problem, I've been restarting samba every night, but we still have the problem occasionally. smbclient shows:

Hi folks, First of all I have a well-working samba-2.2.2-20011013 on a Redhat 7.1 with 2.4.7. (Fast like a thunder 8-). Good job guys!) But. I have a little problem with printing: At my work we have only NT 4.0 workstations on our LAN with sp6a or sp5. This problem is appearing when a client try to print onto a printer attached to samba. Sometimes. But sometimes not. > api_net_sam_logon:

I've been occasionally trying to build the FreeBSD base system (on amd64 / x86_64) using lld in order to see how things are progressing. With a few hacks in the FreeBSD build I can now link the base system userland. The missing functionality I had to work around is listed below. Some of these should probably be addressed in our FreeBSD build infrastructure, while others should be handled in

THANKYOU THANKYOU THANKYOU!!!! That was it exactly. I looked all over the net for the solution to this problem for the last two weeks. Once again thank you!!! jor -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jordan Thompson wrote: | Can't print from client computers: | | I tailed the /var/log/samba/log.phong (note phong is a windoze | client) and got: | [2004/02/10 12:10:20, 0]

Skipped content of type multipart/mixed

Hi there, My Mandrake server has been working fine for years, and I just recently tried adding some rpms to get my squirrel mail updated. (Of course I just removed my uneeded sound card at the same time, amd also found my /var was filling(fixed - printing still doesn't work_, so I am not sure what (if any) broke my system. Any how... here are the symptoms: (1) I can access my shared samba

Samba 3.0.11 on SLES8 on z/VM The system will be running fine then every few days the Winbind daemon will stop. Below are the last lines of the log file. [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475) rid_idmap_get_id_from_sid: no suitable range available for sid: S-1-5-32-545 [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475)