similar to: 2.0.3: character set problem

linux 2.0.35, samba2.0.0 compiled from tgz. I have: character set = ISO8859-1 and client codepage defaults to 850, so that testparm shows client code page = 850 With samba 1.9.18p8, smbstatus showed the filenames with localized characters ok (ie: libert?.txt) I use the same smb.conf with 2.0.0 Now, with samba 2.0.0, if I connect with smbclient to a Samba share I see those characters ok, but

caldera/2.0.x and rh60/2.2.9. I've already posted about this twice to the samba list (since february) then to samba-bugs (19990301); no response, so I retry. I have character set = iso8859-1 client codepage = 850 With samba 1.9.18p8: smbstatus showed the filenames with localized characters ok (ie: libert?.txt); smbclient was ok. With samba 2.0.0 through 2.0.4b: if I connect with smbclient

I've already posted about this to the samba list and samba-bugs (19990301); no response, so I retry here. A win95 pc, and a linux 2.0.33 with: 1) smbclient1.9.18 (patched to restore subdirs) 2) a patched smbclient2.0.2 or smbclient2.0.3. On the win95 pc there's a share, this share contains a dir with: MB 4 Files 142 Subdirs 2 Tarring from the pc to the linux box takes: 1.9.18: 10sec

Why is www.secnet.com down ? i'm looking for the samba-audit-tool and didn't find any mirror. Thomas On Fri, 30 Apr 1999 samba@samba.org wrote: > SAMBA Digest 2073 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) Group-Shares > by Johannes Scherbaum <scherj@funkhaus.de> >

RH6.0. I downloaded: samba-2.0.4b-19990527.src.rpm Follwing the instrucions in README.smbmount, I edited samba2.spec to add 1) --with-smbmount to configure 2) the smbmount related files and man pages to the install and files sections. rpm -ba samba2.spec stops with: ..... Compiling smbd/ssl.c with -fpic Linking shared library bin/smbwrapper.so Compiling client/smbmount.c client/smbmount.c: In

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 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

This is the list of problems I had with samba-2.0.6 so far. Can anyone tell me if he can reproduce them and if he considers them as problems? 2.0.6 on linux 2.2.13 or 2.0.33 1) sighup/log reopening doesn't always work: connections that are already active keep logging to the old logs; logrotate rotates/zip the logs and samba stops logging completely till restart. 2) Localized chars. I have

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

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

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.

I found a strange behaviour in dovecot compressed folder, maybe a bug. It happens only if you have one (and just one!) email in a gz compressed folder. I'm talking about a mbox server. Step to reproduce: - create a new folder, using any client (I think this step is not important, it happens also if tou create this folder server-side). - copy one message (any message) into newly created

Hello, I've a problem known especially to german speaking users (and other nationalities using special characters). I'm using Samba 1.9.18 and a linux 2.0.35 kernel I want to create a directory or file with a name containing german umlaute from the win95 client so that I can see it on the linux machine with the equal characters I've used under win95. On the win95 machine the new

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

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

Looks like this question was indeed solved prior (finally found the searchable archive). Solution is to add ssl CA certDir=/usr/share/ssl/certs to the smb.conf file (or appearently any other directory for that matter). Jamin W. Collins > -----Original Message----- > From: Giulio Orsero [mailto:giulioo@pobox.com] > Sent: Monday, April 16, 2001 1:02 PM > To:

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>