similar to: SSL CA cert error from smbclient (solved)

I'm getting the following error on two of my RH7 boxes that are using SMB to connect to other Windows boxes on our network. I'm sure that someone else has run into this problem, as I have found a cursory reference to it on this mailing list. However, I have not been able to locate a fix for it (other than that the last individual change the directory that SSL was looking to for certs).

samba@samba.org Jeremy Allison <jeremy@valinux.com> Jeremy Allison <jeremy@valinux.com> "Deborah Barba" <dbarba@yahoo-inc.com> Jeremy Allison <jeremy@valinux.com> "Michael Martin" <michael@violetstar.com> Michael Gerdts <gerdts@cae.wisc.edu> Sachin Patil (C&A_Projects) <cna-sp@asc.ltindia.com> Luke Kenneth Casson

samba@samba.org Giulio Orsero <giulioo@pobox.com> Mike Quin <m.r.quin@stir.ac.uk> Matthew Halliday <matthewh@fesa.co.uk> Carsten =3D?iso-8859-1?Q?Nordstr=3DF8m?=3D Jensen <north@get2net.= "Carlos Vinueza M." <carlos@ecuadorexplorer.com> Eric Dahnke <edahnke@istreetlabs.com> Giulio Orsero <giulioo@pobox.com> Giulio Orsero

Hey, digest 2286 incomplete, only first 3 topics contained. Can I get a new copy ? Thanks, Hans-Joerg Glock > -----Urspr?ngliche Nachricht----- > Von: samba@samba.org [SMTP:samba@samba.org] > Gesendet am: Mittwoch, 27. Oktober 1999 22:12 > An: Multiple recipients of list SAMBA > Betreff: SAMBA digest 2286 > > SAMBA Digest 2286 > > For information on

samba@samba.org "Chris" <chrisv@satl.com> "Chris" <chrisv@satl.com> thomas.heiligenmann@t-online.de (Thomas Heiligenmann) thomas.heiligenmann@t-online.de (Thomas Heiligenmann) Jeremy Allison <jeremy@valinux.com> Jeremy Allison <jeremy@valinux.com> David Collier-Brown - Sun Canada <davecb@scot.canada.sun.com> Subba Rao

vl by samba.anu.edu.au with ESMTP id <S12875607AbPJPKg0>; Sat, 16 Oct 1999 20:36:26 +1000 Received: from i3.golden.dom ([212.216.109.2]) by fep09-svc.tin.it (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991016103606.RHGY435.fep09-svc@i3.golden.dom> for <samba@samba.org>; Sat, 16 Oct 1999 12:36:06 +0200 Received: from pc79

I have a similar problem to Giulio Orsero. I have failure messages in the log files, but I actually have samba mapping failures. A PC will map every day for two weeks properly and then not connect. Fifteen minutes later, it will connect. Any suggestions? Alvin ---------- Giulio Orsero <giulioo@tiscalinet.it> 7) I have 2.0.6-PDC and a 2.0.6-domain-member of the 1st pdc.

Hello Samba, ???????, 30 ??????? 99, you wrote: sso> SAMBA Digest 2359 sso> For information on unsubscribing see http://lists.samba.org/ sso> Topics covered in this issue include: sso> 1) Re: Unix .TXT vs DOS .TXT files sso> by Gerry Creager N5JXS <gerry@cs.tamu.edu> sso> 2) Switching user share on NT and smbd spawning sso>

Hi everyone, There's been a few people lately asking about this problem. I've already offered the solution twice, and I believe Andrew has mentioned it too, but we obviously keep getting new people on the list ;) So here's how to fix it, once again: Add the following line to the [global] section of your smb.conf: ssl CA certDir = /usr/share/ssl/certs That's it! The default

Well I figured it out.. did not know that I could make a host file on the winblows client. I knew about the lmhosts file however.. this is a great list.. thanks to all.. *++++++++++++++++++++++++++++++++++++++* * Les Higger ITAF , * Local Area Network Coord. * lhigger@lausd.k12.ca.us * Francisco Bravo Medical Magnet High School * Los Angeles

On 18 Jul 99, giulioo@tiscalinet.it (Giulio Orsero) had questions about 2.0.4b: logrotate problems: [snip] > As I said, my problem was not that logrotate didn't rotate; but > thet after logrotate rotated a log smbd kept logging to the > rotated file instead of to the newly created, empty, log.smb. The > newly created log.smb remained empty forever, till I restarted > smbd.

Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store

Hello Puppet Users, I have encountered an interaction problem between the Puppet CA and Apache mod_ssl, when the Puppet CA configuration files are moved. By default Puppet CA and the Puppet client share the same location for their configuration files, $vardir/ssl. If this is changed so that they use different directories, and Apache mod_ssl is being used like in the Mongrel configuration, then

Just thought it was old enough to be deleted. The problem was not that hard looking back at it now. Thanks Ian __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -------------- next part -------------- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0

samba@samba.org Serge Gavrilov <serge@pdmi.ras.ru> Ed Schernau <ed@schernau.com> Jeremy Allison <jeremy@valinux.com> Cristian POP <cpop@compas.dntcj.ro> Ed Schernau <ed@schernau.com> John Evans <samba@kilnar.com> David Bullock <davidb@loftuscomp.com.au> Gunnar Lindholm <gunnar.lindholm.320@student.lu.se> Junaid Iqbal

Hello! I'm still trying to configure samba with SSL. The operating system is Suse Linux 6.4, samba version 2.0.7. Without ssl, it works well. I installed SSLeay and got no error messages. After installing it, I configured samba with ssl option and no error messages. When I tried to test my configuration file with testparm, I have the following: Load smb config files from

3.0.25rc1 has the same issue. On Fri, 06 Apr 2007 22:52:05 +0200, Giulio <giulioo@gmail.com> wrote: >Vista32 >3.0.25pre2 (I understand vista patches for "share level" are already in) >security = share (with "valid users" on share definition) >host msdfs = no > >user/pass in smbpasswd file. > > >If I use "connect network

Can anyone validate this? I am attempting to run the puppet cert/ca standlone commands. I am running form an unchanged master branch and if I run (simplified for the example): puppet cert generate host the resulting ca_key.pem is not encrypted. If I run : puppet ca generate host the resulting ca_key.pem is encrypted. In both cases the ca.pass file is created but the code path through cert does

I am building a mail server on Centos 6.3 and working with OpenSSL to create a self-signed certificate for mail use. Along the line of learning the 'best' options to use for OpenSSL and dealing with the default SSL virtual host for Apache, I discovered that the localhost cert created (I believe) during firstboot has the X509v3 extensions set as a CA cert (eg basicConstraint CA:TRUE).

Hello ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -