similar to: Unable to connect to shares - Error about 'Domain Controller'

Hi folks, # uname -srvo Linux 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:01:26 EDT 2010 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # smbd --version Version 3.3.8-0.51.el5 I'm trying to run a backup samba server using some custom in-house scripts which I inherited and am stuck with. Essentially the primary server periodically rsyncs a bunch of

Hello, I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, SMP, 6.2 RELEASE). My log.smbd looks like below: --- samba starts normally: [2007/11/24 16:55:22, 0] smbd/server.c:main(944) smbd version 3.0.26a started. Copyright Andrew Tridgell and the Samba Team 1992-2007 --- but an error is reported: [2007/11/24 16:55:22, 0]

Hello I got a bunch of PANIC messages this morning on a FreeBSD 6.3 host, and had to restart Samba: ======== [2008/05/10 10:28:51, 0] lib/util.c:smb_panic(1633) PANIC (pid 43086): tdb_reopen_all failed. [2008/05/10 10:28:51, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 3 stack frames: #0 0x8220341 <smb_panic+73> at /usr/local/sbin/smbd #1 0x82b9389 <main+4773> at

[apologies to the samba list if you aren't interested in this] I've rewritten the TDB perl bindings from scratch. this version: * is on CPAN (http://search.cpan.org/search?mode=module&query=TDB_File) * supports 8-bit keys and values * gives access to the complete TDB API Feel free to include/reference in the TDB distribution (or ignore completely, of course ;) A few comments

Dear Samba- We're using the virtualization application openVZ to run small web services for researchers. Unlike other virtualization software, openVZ uses the host file system for the guest OS; essentially the root file system of the guest is a chrooted subdirectory on the host. When openVZ migrates a guest between two host machines it uses rsync to transfer the files. Unfortunately, this

Fellow samba folk, This one's making me want to tear out what little hair I have left. THE *NIX PLATFORM: FreeBSD 7.0-RELEASE, Samba 3.3.8. THE ENVIRONMENT: Small domain, Windows 2003 servers and XP-pro based workstations. The FreeBSD server is a member server in the domain, so at least that works. THE SYMPTOMS: This is bizarre. I can, using mount_smbfs on the FreeBSD side, easily

Fellow samba folk, Please disregard my earlier message. I have solved the problem, and it appears to have been a combination of things. First, somehow (I have no idea how), the Samba package must have gotten corrupted during installation. I cleaned up the mess, reinstalled, and had much better results. Second issue: I followed the instructions at this link, Section 2.6, VERY carefully, to

Hello, upgraded to Samba 3.2.6, and immediately printing went into coma. Observed that printers lose their configurations (driver models, locations, etc). And if I reset the printer drivers on each share, eventually they will be lost again. Looking at the logs we are getting panics like this: --- [2008/12/16 05:12:51, 0] lib/util_tdb.c:tdb_log(682) tdb(/var/lib/samba/printing/CanonC1.tdb):

I've recently developed these messages coming out of the log.smbd. I can no longer connect to my samba drives. I get an explorer window, but no shares displayed. Anyone have any ideas? Thanks [2006/10/29 07:58:48, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/db/samba/locking.tdb): tdb_reopen: open failed (No such file or directory) [2006/10/29 07:58:48, 0]

Hi, all: I am using Samba 3.0.5 with patch at http://samba.org/~jerry/patches/post-3.0.4/. But I found the follow messages in samba log: =============================================================== [2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1398) PANIC: internal error [2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1406) BACKTRACE: 3 stack frames: #0 smbd(smb_panic2+0xef)

Dear Samba friends, I have recently upgraded from Samba 3.0.36 to Samba 3.5.6. After upgrade I encounter the following error in log.smbd: [2011/06/03 10:09:43, 0] smbd/server.c:1119(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/06/03 10:09:43.379106, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The "share modes" option is

Hi everyone, I'm having an odd issue with a Samba install - it starts SIGABORTing complaining that gencache.tdb has gone missing.. ie [2007/08/09 12:52:50, 0] lib/util_tdb.c:tdb_log(662) tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such file or directory) [2007/08/09 12:52:50, 0] smbd/server.c:open_sockets_smbd(572) tdb_reopen_all failed. If I recreate it and restart

Hi everyone, Recently upgraded to 3.3.7 on a test server (can do everything on it if you need to test something like patch, configuration options, etc?), and got big problems with printing very similar to http://www.mail-archive.com/samba at lists.samba.org/msg97841.html signaled for version 3.2.6 I'm on CentOS 5.3 recently updated (with sernet packages) and I checked that I have the correct

Hi everyone, I recently wanted to try Samba 3.3.11 for CentOS 5.4. At first, I tried the Sernet packages then I compiled my own packages but in both cases, I get the same error messages (SMB?PANIC) when I try to install/delete/use printers in Samba. At first, I thought this was a right issue on filesystem (due to messages "Permission denied" in logs), so I change many rights at many

Fellow users, This is just a heads-up to let the list know that I'm still unable to get ANY sort of pop3 or pop3s authentication to work with Dovecot. Just as a sanity check, I set up an entirely separate system, running FreeBSD 6.1 production, postfix 2.3, and Dovecot 1.0rc2, as a testbed. I got the exact same problem that I had with the NetBSD 3.0 production server, specifically that

Fellow Dovecot'ers. I tried something tonight that I should have done a while back: Turned on verbose logging in the authentication section. I'm still unable to get the mail client I'm experimenting with (Pegasus) to complete a pop3s connection, in that I still get an indication of a failed password. However, at least I'm a little closer to understanding the failure itself.

Fellow Dovecot'ers, I've -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin at

Fellow techies, OK... This is going to go down as one of those "D'Oh!" moments in the world of computers. Boy, do I feel dumb... In short: I found the problem. One miserable little line in 'dovecot.conf' called 'auth_default_realm =.' I had this set to 'bluefeathertech.com,' thinking it was necessary to do so. I was wrong, at least for my environment,

Good day, gang, Chris McKeever was kind enough to write back to me over the weekend regarding the problems I'd experienced in using Backup Exec 8.x and 9.x to connect to Samba shares on a NetBSD system. Between his comments and my direct experience, I've only found ONE combination that will work, and that is: NetBSD 1.6, Samba 2.2.8a, and Backup Exec 8.6. If you take NetBSD up to 1.6.1,

Fellow Samba-shakers, I've run into an odd problem, and I'm seeking the advice of anyone who has implemented Veritas Backup Exec 8.6 or 9.0, on an NT 4.0 server platform, to perform backups of NetBSD 1.6x systems via Samba file shares. Said problem did NOT manifest itself until I tried using Samba 3.0.0. I have jumped back to 2.2.8a, since that's the last version that was known to