Greetings,
Is there any way to get Samba to interact with MS-DOS? I am
attempting to turn a Linux box into a VPN router for DOS clients. What I
need to know is, can I get a CIFS protocol stack for MS-DOS, is a TCP/IP
stack sufficient, are there any other solutions anyone knows about?
Thank You.
Tyrell Kumlin, Help Desk
Cipher Systems Ltd. - Providing quality software solutions & services since
1978.
E-mail: tyrell@ciphersys.com
Phone: (403) 256-8877, ext. 239
Fax: (403) 256-8878
Cipher was selected as the "Fastest Growing Company in Alberta"
by Alberta Venture magazine in 2000 & included in the 1999
Deloitte & Touche "Canadian Technology Fast 50."
Visit us at: http://www.ciphersys.com
> -----Original Message-----
> From: samba@samba.org [SMTP:samba@samba.org]
> Sent: Thursday, March 23, 2000 1:42 PM
> To: Multiple recipients of list SAMBA
> Subject: SAMBA digest 2460
>
> SAMBA Digest 2460
>
> For information on unsubscribing see http://lists.samba.org/
>
> Topics covered in this issue include:
>
> 1) Re: Looking for Large Scale SAMBA Install Success / Failure Storie
> by David Collier-Brown - Sun Canada <davecb@scot.canada.sun.com>
> 2) WINS weirdness
> by Edward Schernau <ed@schernau.com>
> 3) Authenticating to NT Domain
> by "Paul D. Ostwick" <paul@ubeek.com>
> 4) Win 98 password changes - Samba doesn't recognise data
> by "Ian Harris" <iharris@quadtel.com>
> 5) ./configure issues
> by "Henri J. Schlereth" <henris@neandertal.org>
> 6) windoz client won't print
> by jonathan <jfondow1@home.com>
> 7) RE:Cannot see Samba server on different network
> by Nickos Yoldassis <niyo@inbit.gr>
> 8) windows printer, samba password required?
> by awesome-dave1@juno.com
> 9) supressing output of netlogon scripts.
> by awesome-dave1@juno.com
> 10) Setting 'system' attribute on folders
> by Ryk Field <r.field@mailbox.uq.edu.au>
> 11) Messages with smbclient...
> by BRUNET Franck <franck.brunet@free.fr>
> 12) resource sharing
> by Alex <iordache@petrom.ro>
> 13) URGENT: WIN2K INVALID VOLUMENAME
> by "Oliver Rehmann" <oliver_rehmann@compuserve.com>
> 14) Printer shares question
> by "Jonathan Bayer" <a8targazer@bayerfamily.net>
> 15) w2K with Samba
> by "Nick Dolan" <nick@ipicorp.com>
> 16) Re: Printer shares question
> by "William R. Knox" <wknox@mitre.org>
> 17) Re: windoz client won't print
> by Steve Litt <slitt@troubleshooters.com>
> 18) Re: Printer shares question
> by Steve Litt <slitt@troubleshooters.com>
> 19) Re: Printer shares question
> by Steve Litt <slitt@troubleshooters.com>
> 20) HP-Unix 10.20
> by Gunter Reinhard <gunter.reinhard@cmg.de>
> 21) Policy Editor and Samba 2.0.6
> by "Paul Rijke" <p.rijke@truckland.nl>
> 22) samba-tng-alpha-1.3.tar.gz
> by Luke Kenneth Casson Leighton <lkcl@samba.org>
> 23) 2.0.7pre2: passwd change, log, ...
> by Giulio Orsero <giulioo@pobox.com>
>
> ----------------------------------------------------------------------
>
> Date: Wed, 22 Mar 2000 16:49:46 -0500 (EST)
> From: David Collier-Brown - Sun Canada <davecb@scot.canada.sun.com>
> To: samba@samba.org
> Subject: Re: Looking for Large Scale SAMBA Install Success / Failure
> Storie
> Message-ID: <200003222150.QAA26063@opcom-mail.canada.sun.com>
> MIME-Version: 1.0
> Content-Type: TEXT/plain; charset=us-ascii
> Content-MD5: rB7AqDdqbdFi4Xt9N+3Uog=>
> KSmith@bartoninsurance.com
> | I see a lot of the problems which are
> | reported on the SAMBA Digest but, with the exception of the slow samba
> | access of large directories, we haven't had any problems which we
were
> not
> | able to solve by studying the documentation.
>
> A tentative update on this: just before I left Toronto
> for Boston last week, a colleague tested a update-intensive
> program (maintaining a queue in a single directory) using the
> "logging" option of the Solaris 8 UFS, and got the same
> performance as with tmpfs (an in-memory filesystem).
>
> I suspect we'll see a moderate improvement in file-create
> delete and rename performance in large directories, but
> I won't bet on improved read performance (;-))
>
> If I have the opportunity, I'll see if I can get some timings.
>
>
> --
> David Collier-Brown in Boston
> Phone: (781) 442-0734, Room BUR03-3632
>
>
> ------------------------------
>
> Date: Wed, 22 Mar 2000 17:48:40 -0500
> From: Edward Schernau <ed@schernau.com>
> To: samba@samba.org
> Subject: WINS weirdness
> Message-ID: <38D94DC8.FFD961D7@schernau.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> I have a Samba server 2.0.7pre2 on linux 2.2.13, which has
> joined a domain using smbclient. Security=domain, and all
> works well.
>
> It is configured to be the WINS server.
>
> PCs and NT boxes in this domain, plus the DCs and PCs in 2
> other domains are set up to use this box as their WINS server.
> (this is Domain1) The PDC in Domain1 is the master
> browser (local and domain).
>
> Here is the problem:
> 2 other subnets...
> PDC in Domain2 only registers the <00> and <1E> NetBIOS names
> with the samba box. For the Domain name.
> PDC in Domain3 registers the <00>, <1B> and <1C> names
for
> its domain, but only the <00> and <03> names for itself, NOT
> the <20> name for itself.
>
> The consequence of these is that I can't use some of the NT
> Server admin tools from an NT server in Domain1.
>
> Is there anything I need to do on the client (NT PDC) side,
> so that they properly register with the WINS (Samba) server?
> Ultimately, I'd like to be able to browse the other
> domain/workgroups in Network Neighborhood, but at this point
> just being able to run User Manager will be a plus.
>
> --
> Edward Schernau http://www.schernau.com
> Network Architect mailto:ed@schernau.com
> Rational Computing Providence, RI, USA
>
> ------------------------------
>
> Date: Wed, 22 Mar 2000 18:09:02 -0500
> From: "Paul D. Ostwick" <paul@ubeek.com>
> To: samba@samba.org
> Subject: Authenticating to NT Domain
> Message-ID: <38D9528E.5F9D4D5E@ubeek.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> What is the point of authenticating to an NT Domain if the users still
> have to have an account on the Linux server? Is there a way to make it
> so that whether or not someone can connect to the Samba server is
> dictated by the usernames/passwords on the NT PDC?
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 11:40:44 +1100
> From: "Ian Harris" <iharris@quadtel.com>
> To: <samba@samba.org>
> Subject: Win 98 password changes - Samba doesn't recognise data
> Message-ID: <NDBBLICJMLLNFPHFLHDNCEJCCAAA.iharris@quadtel.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
>
> No, it's not a case of the password programs (ie, passwd) being
incorrect
> at
> the samba end, it's deeper than that - the smbd log says
>
> [2000/03/13 12:50:34, 0] smbd/chgpasswd.c:check_oem_password(699)
> check_oem_password: incorrect password length (-1423948563).
>
> So the actual data sent by win 98 appears to be unrecognised by Samba
> (2.0.6).
> We are running Win 98 second addition 4.10.2222 A.
>
> Any help with this problem would be appreciated.
> regards
> Ian.
>
>
> ------------------------------
>
> Date: Wed, 22 Mar 2000 19:32:41 -0600 (CST)
> From: "Henri J. Schlereth" <henris@neandertal.org>
> To: samba@samba.org
> Subject: ./configure issues
> Message-ID: <200003230132.TAA23885@kesrith.neandertal.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> I have run ./configure on both 2.0.7Pre2 and tng-alpha-1.1
> and get the following error message.
>
> ERROR: No locking available. Running Samba would be unsafe
> configure: error: summary failure. Aborting config.
>
> I have compiled Samba before. This is a RH6.1 machine with
> kernel 2.2.15-2.5.0 (RH6.2Beta). I am currently running
> Samba 2.0.6 with out any major problems.
>
> Any ideas?
>
> Henri
> --
> -------------------------------------------------------------
> "The weak shall perish." Species 8472
> -------------------------------------------------------------
>
> ------------------------------
>
> Date: Wed, 22 Mar 2000 22:05:36 -0500
> From: jonathan <jfondow1@home.com>
> To: samba <samba@samba.org>
> Subject: windoz client won't print
> Message-ID: <38D98A00.2585FBDE@home.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> I am running SuSE6.3, kernel 2.2.13, samba 2.0.6, lprold3.0.48. I can
> print to the print server from my workstation (SuSE6.3) using lpr
> remote, but when my wife tries to print from her windows machine, the
> file goes to /var/spool/lpd/lj4dith-letter-auto-mono-600 and then just
> sits there.
> File sharing is working great, just having a problem printing.
> Everything was working great until I got the brainstorm to upgrade. Any
> help would be greatly appreciated. TIA
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 09:22:17 -0800
> From: Nickos Yoldassis <niyo@inbit.gr>
> To: "'samba@samba.org'" <samba@samba.org>
> Subject: RE:Cannot see Samba server on different network
> Message-ID: <01BF94A9.4CA181A0@laptop.ibm.inbit.gr>
> MIME-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 8BIT
>
> quick solution:
>
> You have to put an entry for your SAMBA server in every machine's
LMHOSTS
> file (in network B). After you do that, you have to restart windows.
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 03:24:36 -0500
> From: awesome-dave1@juno.com
> To: samba@samba.org
> Subject: windows printer, samba password required?
> Message-ID: <20000323.032711.-254985.8.awesome-dave1@juno.com>
> MIME-Version: 1.0
> Content-Type: text/plain
> Content-Transfer-Encoding: 7bit
>
> Hello,
> I'm trying to use samba 2.06 to print to a shared windows printer.
> The
> problem is I keep getting the message connection refused, even though I
> don't have any password on this printer. Do windows printer shares also
> have to be listed in the smbpasswd file?
> Please e-mail privately.
> Thanks.
> Dave.
>
> ________________________________________________________________
> YOU'RE PAYING TOO MUCH FOR THE INTERNET!
> Juno now offers FREE Internet Access!
> Try it today - there's no risk! For your FREE software, visit:
> http://dl.www.juno.com/get/tagj.
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 03:26:04 -0500
> From: awesome-dave1@juno.com
> To: samba@samba.org
> Subject: supressing output of netlogon scripts.
> Message-ID: <20000323.032711.-254985.9.awesome-dave1@juno.com>
> MIME-Version: 1.0
> Content-Type: text/plain
> Content-Transfer-Encoding: 7bit
>
> Hello,
> I've got roaming profiles set up on my machines, that load and run
> netlogon scripts that do various things. I would like there output
> suppressed, i.e. I don't want to even see the dos box, I just want the
> things to do there job and go on. Is this possible?
> Thanks.
> Dave.
>
> ________________________________________________________________
> YOU'RE PAYING TOO MUCH FOR THE INTERNET!
> Juno now offers FREE Internet Access!
> Try it today - there's no risk! For your FREE software, visit:
> http://dl.www.juno.com/get/tagj.
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 20:57:48 +1000 (GMT+1000)
> From: Ryk Field <r.field@mailbox.uq.edu.au>
> To: samba@samba.org
> Subject: Setting 'system' attribute on folders
> Message-ID:
<Pine.OSF.4.21.0003232053530.22017-100000@dingo.cc.uq.edu.au>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hello all,
>
> I have been able to understand how to use the "x" attribute
> to indicate the system or hidden status of files on samba
> shares, but I need to be able to indicate to Windows that
> a folder on a Samba share is a 'System' folder, ie, has the
> windows System attribute set.
>
> Since the "x" bit is used (as far as my limited knowledge of
> unix goes) to indicated whether or not the user/group/other
> is allowed to go into a subdirectory, this seems to prohibit
> designating any folder with the system attribute in the
> same manner as a file.
>
> Is there some way to have samba present to windows computers
> the System attribute set for a folder?
>
> Thanks for any help you can offer.
>
> Ryk.
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 13:38:46 +0100
> From: BRUNET Franck <franck.brunet@free.fr>
> To: <samba@samba.org>
> Subject: Messages with smbclient...
> Message-ID: <953815126.38da1056b1801@imp.free.fr>
> MIME-Version: 1.0
> Content-Type: text/plain
> Content-Transfer-Encoding: 8bit
>
> Hello,
>
> OS : AIX 432
> SAMBA : 2.0.5a
>
> I have messages from smb when i
> execute smbclient -L <hostname> -N
> and it's very difficult to read the result.
> Messages are like that :
> ..
> smb_vwv[0]=8 (0x8)
> smb_vwv[1]=2775 (0xAD7)
> smb_vwv[2]=0 (0x0)
> smb_vwv[3]=8 (0x8)
> smb_vwv[4]=56 (0x38)
> smb_vwv[5]=0 (0x0)
> smb_vwv[6]=2775 (0xAD7)
> smb_vwv[7]=64 (0x40)
> smb_vwv[8]=0 (0x0)
> smb_vwv[9]=0 (0x0)
> ..
>
> Is anybody knows how to remove those messages ?
> Is there any option to put in compilation ?
>
> Thanks.
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 15:45:35 +0200
> From: Alex <iordache@petrom.ro>
> To: samba@samba.org
> Subject: resource sharing
> Message-ID: <38DA1FFF.D37F0381@petrom.ro>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-2
> Content-Transfer-Encoding: 7bit
>
> I want to know more about a problem the Samba developers solved it long
> time ago. It's about what's going on (in detail) when a NT or W95
user
> clicks a network neibourhood computer, in a TCP/IP only network, from
> the other's computer point of view.Someone told me to examine the
> receiving buffer, but I think that if this is the only solution, someone
> before me did that already and maybe can help me. I'm ready to learn by
> myself if someone help me with some links. Forever grateful to my saver
> !
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 15:03:57 +0100
> From: "Oliver Rehmann" <oliver_rehmann@compuserve.com>
> To: <samba@samba.org>
> Cc: "Chip Mefford" <cmefford@avwashington.com>
> Subject: URGENT: WIN2K INVALID VOLUMENAME
> Message-ID: <002101bf94d0$a2d723a0$e401a8c0@milkyway.galaxy.net>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Dear Samba Users
>
> I detected a strange behaviour between Win2k Prof. and Samba and I hope
> somebody can help me
> fixing it.
>
> The Bug:
> ======>
> Samba does not correctly return the volume name back to win2k.
> In the man pages it is written that by default the sharename is returned
> as
> volumename.
> This works fine for Win98 and NT4 but not for Win2k.
>
> If I say "label v:" (needless to say that v: is my samba drive)
from Win2k
> I
> get the following result:
>
>
=========================================================================>
Microsoft Windows 2000 [Version 5.00.2195]
> (C) Copyright 1985-1999 Microsoft Corp.
>
> H:\>label v:
> Volume in drive V: is ??? <=========== WRONG
!
> The label should be "privat" not "???"
> Volume Serial Number is 0A82-0A10
> Volume label (ENTER for none)?
>
>
=========================================================================>
> For sure the label is not "???" ! Win2k simply doesn't get a
correct
> answer.
>
> I have a software which does image cataloging (Thumbs Plus v4.1) which
> hardly relies on volume labels.
> The software works fine on my Windows 98 system. If I access the same
> database (from Thumbs Plus)
> from Win2k with the same drive (v:) mounted to my Redhat Linux System
> Thumbs
> Plus does not
> recognize the pictures on this drive as already cataloged. This works fine
> between Win98 and NT4.
>
> The keyword "volume = privat" in the share section of my
smb.conf file
> doesn't help neither.
>
> ANY idea ????
>
> My systems:
>
> LINUX:
> ----------
>
> RedHat Linux 6.1
> Samba Version: samba 2.0.7pre2
>
> Windows 2000:
> -----------------------
>
> Intel Windows 2000 Prof. Final (Build 2195) English
>
>
>
> With kind regards,
>
> Oliver Rehmann
> oliver_rehmann@compuserve.com
>
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 09:58:14 -0500
> From: "Jonathan Bayer" <a8targazer@bayerfamily.net>
> To: "samba@samba.org" <samba@samba.org>
> Subject: Printer shares question
> Message-ID: <200003231508.KAA22414@bayerfamily.net>
> MIME-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Hi,
>
> I checked the archives, but couldn't find this question:
>
> I have two printers set up on my RedHat Linux 6.1 box, called lp0 and lp1
> (original, huh?). Anyway, I want both of these printers to be visible
> and browsable on the network. I have the following relevant lines in my
> smb.conf file:
>
> printcap name = /etc/printcap
> load printers = yes
>
> [printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = no
> public = yes
> guest ok = yes
> writable = no
> printable = yes
>
> While I can net use to the printers, they don't show up in a net view
or
> when I look at the Network window on the Windows desktop. Do I need
> to specify each printer I want to be publicly visible, or am I missing
> something?
>
> Thanks.
>
>
> JBB
>
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 14:49:24 -0000
> From: "Nick Dolan" <nick@ipicorp.com>
> To: <samba@samba.org>
> Subject: w2K with Samba
> Message-ID: <NDBBKODOKKPNGHENHIDAGEEICCAA.nick@ipicorp.com>
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
> boundary="----=_NextPart_000_0011_01BF94D6.FB03B6A0"
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0011_01BF94D6.FB03B6A0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Hi,
>
> Not sure if I've got the right list, but here goes - wondering if
anyone
> has
> had this problem and solved it.
>
> we have Samaba 205 set up on Solaris 2.6 /2.7. in Share mode
>
> all our win95, win98 and NT 4 machines can browse the Solaris shares with
> no
> problems
>
> However our W2K machines see the netbios names of the Unix servers, but
> are
> unable to browse ? A error message saying account is not authorized or
> something about rpc not being registered is returned.
>
> Can anyone help ?
>
> Nick
>
> ------=_NextPart_000_0011_01BF94D6.FB03B6A0
> Content-Type: text/x-vcard;
> name="Nick R Dolan.vcf"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: attachment;
> filename="Nick R Dolan.vcf"
>
> BEGIN:VCARD
> VERSION:2.1
> N:Dolan;Nick;R;Mr.
> FN:Nick R Dolan
> NICKNAME:Nick
> ORG:IPI UK Ltd.;Client Services
> TITLE:Client Services Manager - Europe
> TEL;WORK;VOICE:0207 251 6767
> TEL;HOME;VOICE:0207 251 6767
> TEL;CELL;VOICE:0961 171 046
> TEL;HOME;FAX:0207 251 3161
> ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;IPI London;48-50 St. John >
St.=3D0D=3D0A;London;;EC1M;united Kingdom
> LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:IPI London=3D0D=3D0A48-50 St. >
John St.=3D0D=3D0A=3D0D=3D0ALondon EC1M=3D0D=3D0Aunited Kingdo=3D
> m
> ADR;HOME;ENCODING=3DQUOTED-PRINTABLE:;;8 Edmeston >
Close=3D0D=3D0A;London;;E9 5TJ;United Kingdom
> LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:8 Edmeston >
Close=3D0D=3D0A=3D0D=3D0ALondon E9 5TJ=3D0D=3D0AUnited Kingdom
> X-WAB-GENDER:1
> URL:http://www.ipicorp.com
> EMAIL;PREF;INTERNET:nick@ipicorp.com
> REV:20000322T184725Z
> END:VCARD
>
> ------=_NextPart_000_0011_01BF94D6.FB03B6A0--
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 10:08:36 -0500
> From: "William R. Knox" <wknox@mitre.org>
> To: Multiple recipients of list SAMBA <samba@samba.org>
> Subject: Re: Printer shares question
> Message-ID: <38DA3374.80354E02@mitre.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Jonathan,
> I do believe it's the 'browseable = no' parameter in your
[printers]
> section that's doing this. Try setting it to yes and see what happens.
> Good luck!
>
> --
> Bill Knox
> Senior Operating Systems Programmer/Analyst
> The MITRE Corporation
>
> Jonathan Bayer wrote:
> >
> > Hi,
> >
> > I checked the archives, but couldn't find this question:
> >
> > I have two printers set up on my RedHat Linux 6.1 box, called lp0 and
> lp1 (original, huh?). Anyway, I want both of these printers to be visible
> > and browsable on the network. I have the following relevant lines in
my
> smb.conf file:
> >
> > printcap name = /etc/printcap
> > load printers = yes
> >
> > [printers]
> > comment = All Printers
> > path = /var/spool/samba
> > browseable = no
> > public = yes
> > guest ok = yes
> > writable = no
> > printable = yes
> >
> > While I can net use to the printers, they don't show up in a net
view or
> when I look at the Network window on the Windows desktop. Do I need
> > to specify each printer I want to be publicly visible, or am I missing
> something?
> >
> > Thanks.
> >
> > JBB
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 10:28:09 -0500
> From: Steve Litt <slitt@troubleshooters.com>
> To: samba@samba.org
> Subject: Re: windoz client won't print
> Message-ID: <3.0.6.32.20000323102809.009401a0@pop.pacificnet.net>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
>
> Make sure it prints via the lpr command. Then temporarily place that
> command as the value of print command=, with the filename replaced by %s.
> Be sure to add a second command (separated by semicolon) to remove the
> file
> after printing.
>
> Steve Litt
>
> At 02:07 PM 03/23/2000 +1100, you wrote:
> >I am running SuSE6.3, kernel 2.2.13, samba 2.0.6, lprold3.0.48. I can
> >print to the print server from my workstation (SuSE6.3) using lpr
> >remote, but when my wife tries to print from her windows machine, the
> >file goes to /var/spool/lpd/lj4dith-letter-auto-mono-600 and then just
> >sits there.
> >File sharing is working great, just having a problem printing.
> >Everything was working great until I got the brainstorm to upgrade.
Any
> >help would be greatly appreciated. TIA
> >
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 10:33:26 -0500
> From: Steve Litt <slitt@troubleshooters.com>
> To: samba@samba.org
> Subject: Re: Printer shares question
> Message-ID: <3.0.6.32.20000323103326.009965f0@pop.pacificnet.net>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
>
> I'm not much of a proofreader, but your smb.conf looks good to me.
Perhaps
> it's one of those silly Windows Explorer browsing problems.
>
> Try smbclient -NL servername from the console of the server, and see if
> you
> see both printers there. If not, you know you've got something wrong in
> your smb.conf, However, both show up there, you've got one of those
little
> browsing Network Neighborhood problems often solved by the preferred
> master=yes parameter.
>
> Steve Litt
>
> At 02:00 AM 03/24/2000 +1100, Jonathan Bayer wrote:
> >Hi,
> >
> >I checked the archives, but couldn't find this question:
> >
> >I have two printers set up on my RedHat Linux 6.1 box, called lp0 and
lp1
> (original, huh?). Anyway, I want both of these printers to be visible
> >and browsable on the network. I have the following relevant lines in
my
> smb.conf file:
> >
> > printcap name = /etc/printcap
> > load printers = yes
> >
> > [printers]
> > comment = All Printers
> > path = /var/spool/samba
> > browseable = no
> > public = yes
> > guest ok = yes
> > writable = no
> > printable = yes
> >
> >While I can net use to the printers, they don't show up in a net
view or
> when I look at the Network window on the Windows desktop. Do I need
> >to specify each printer I want to be publicly visible, or am I missing
> something?
> >
> >Thanks.
> >
> >
> >JBB
> >
> >
> >
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 10:37:10 -0500
> From: Steve Litt <slitt@troubleshooters.com>
> To: samba@samba.org
> Subject: Re: Printer shares question
> Message-ID: <3.0.6.32.20000323103710.012c1bb0@pop.pacificnet.net>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
>
> Bill --
>
> The browseable=no just prevents a share called "printers" from
appearing
> in
> the browse. Because [printers] is a special share, it reveals all printers
> in printcap regardless of its browseable status. I learned this the hard
> way :-)
>
> Steve Litt
>
>
> At 02:09 AM 03/24/2000 +1100, William R. Knox wrote:
> >Jonathan,
> >I do believe it's the 'browseable = no' parameter in your
[printers]
> >section that's doing this. Try setting it to yes and see what
happens.
> >Good luck!
> >
> >--
> > Bill Knox
> > Senior Operating Systems Programmer/Analyst
> > The MITRE Corporation
> >
> >Jonathan Bayer wrote:
> >>
> >> Hi,
> >>
> >> I checked the archives, but couldn't find this question:
> >>
> >> I have two printers set up on my RedHat Linux 6.1 box, called lp0
and
> lp1 (original, huh?). Anyway, I want both of these printers to be visible
> >> and browsable on the network. I have the following relevant lines
in
> my
> smb.conf file:
> >>
> >> printcap name = /etc/printcap
> >> load printers = yes
> >>
> >> [printers]
> >> comment = All Printers
> >> path = /var/spool/samba
> >> browseable = no
> >> public = yes
> >> guest ok = yes
> >> writable = no
> >> printable = yes
> >>
> >> While I can net use to the printers, they don't show up in a
net view
> or
> when I look at the Network window on the Windows desktop. Do I need
> >> to specify each printer I want to be publicly visible, or am I
missing
> something?
> >>
> >> Thanks.
> >>
> >> JBB
> >
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 16:45:23 +0100
> From: Gunter Reinhard <gunter.reinhard@cmg.de>
> To: "'samba@samba.org'" <samba@samba.org>
> Subject: HP-Unix 10.20
> Message-ID: <8DF4B30F5551D211B5AE00104BB3F8D456BBD8@DE-ESC-MAIL01>
> MIME-Version: 1.0
> Content-Type: text/plain
>
> Hi,
>
> since december 1999 we have successfully running Samba on HP-Unix 10.20
> with
> nmbd version 2.04b. Suddenly it's no longer possible to connect from
Win9x
> clients - a connect from NT-Clients still works, but connection
> establishing
> is very slow.
>
> Here is an excerpt from the log.smb file for a connect request from a
> Win95
> client:
>
>
> [2000/03/22 16:54:36, 3] smbd/process.c:(974)
> priming nmbd
> [2000/03/22 16:54:51, 3] lib/util_sock.c:(645)
> sending a packet of len 1 to (127.0.0.1) on port 137 of type DGRAM
> [2000/03/22 16:54:51, 4] lib/time.c:(110)
> Serverzone is -3600
> [2000/03/22 16:54:51, 3] smbd/process.c:(615)
> Transaction 0 of length 72
> [2000/03/22 16:54:51, 2] smbd/reply.c:(95)
> netbios connect: name1=CMGGE60 name2=DE-ESC-LAP4408
> [2000/03/22 16:54:51, 5] smbd/connection.c:(127)
> trying claim /var/opt/samba/locks STATUS. 100000
> [2000/03/22 16:54:51, 0] lib/util_sock.c:(889)
> getpeername failed. Error was Invalid argument
> [2000/03/22 16:54:51, 5] smbd/reply.c:(147)
> init msg_type=0x81 msg_flags=0x0
> [2000/03/22 16:54:51, 0] lib/util_sock.c:(415)
> write_data: write failure. Error = Broken pipe
> [2000/03/22 16:54:51, 0] lib/util_sock.c:(190)
> write_socket: Error writing 4 bytes to socket 4: ERRNO = Broken
> pipe
> [2000/03/22 16:54:51, 0] lib/util_sock.c:(606)
> Error writing 4 bytes to client. -1. Exiting
>
> The Win95 client then shows a popup saying "\\Cmgge60 is not
accessible.
> The
> network is busy."
>
> I performed the tests described in Diagnosis.txt. Test 1 to 4 succeeded. I
> got problems with TEST 5 (nmblookup -B de-esc-lap4408 '*'): After 1
or 2
> minutes the program exits with
>
> Sending queries to 0.0.0.0
> 10.48.191.210 *<00>
>
> The IP-address is the one of the Samba server not the one of the client!
> The
> same happens with a query for a NT client.
>
> Is it a sudden name resolving problem? In this moment I have no idea how
> to
> proceed. The problem arose over night - no configuration files have been
> modified, everything looks like before - nevertheless something in our
> network environment must have changed, but what?
>
> Is there someone who has a usefull idea? That would be great!
>
> Regards,
> Gunter Reinhard
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 20:43:18 +0100
> From: "Paul Rijke" <p.rijke@truckland.nl>
> To: <samba@samba.org>
> Subject: Policy Editor and Samba 2.0.6
> Message-ID: <NCBBIMDLMKPBLKGBLLFNKEOAEEAA.p.rijke@truckland.nl>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Hi you Latin-American dansers,
>
> Does anyone has experience with the Policy Editor and Win95/Samba 2.0.6?
> I'd
> like to secure as much as possible for my users. The helpfile says
> something
> like put a .pol file in the netlogon share... but that didn't work. Or
did
> I
> something wrong?
>
> Well, I don't want to invent the wheel again so I ask all of you... Can
it
> be done and how?
>
> Paul Rijke
> Truckland B.V.
> Basisweg 47
> 1043 AN AMSTERDAM
> tel: 020 - 585 1234
> fax: 020 - 585 1189
> e-mail: p.rijke@truckland.nl *
> website: http://www.truckland.nl *
>
>
>
> ------------------------------
>
> Date: Fri, 24 Mar 2000 07:15:32 +1100
> From: Luke Kenneth Casson Leighton <lkcl@samba.org>
> To: samba-team@samba.org, Samba Mailing List <samba@samba.org>,
> Samba NT Domains Mailing List <samba-ntdom@samba.org>,
> Multiple recipients of list <samba-technical@samba.org>
> Subject: samba-tng-alpha-1.3.tar.gz
> Message-ID:
<Pine.SGI.4.05.10003240710180.14489-100000@samba.anu.edu.au>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> ftp://samba.org/pub/samba/alpha and mirrors.
>
> due to some confusion about how to use samedit's createuser command, i
put
> a warning / security message in whenever createuser hostname$ is used.
> it basically says, now you can join the workstation to the domain because
> you have just set the trust account to the insecure, well-known initial
> value, and you had best join the workstation to the domain ASAP for
> security reasons.
>
> i also checked that profiles work: they do. it helps to have write
> permission to the directory that the profiles are to be stored in, i
> found.
>
> one person reported the usual problem with profiles, namely that on
> logout, a connection is maintained to the profile share and the next user
> logging in, the workstation attempts to reuse the connection, which is not
> the right thing to do.
>
> for this reason, and others, it is best to use 2.0 or cvs main for file
> serving.
>
> luke
>
> <a href=" mailto:lkcl@samba.org" > Luke Kenneth Casson
Leighton </a>
> <a href=" http://cb1.com/~lkcl" > Samba and Network
Development </a>
> <a href=" http://samba.org" > Samba Web site
</a>
> <a href=" http://mcp.com" > Macmillan Technical
Publishing </a>
>
> ISBN1578701503 DCE/RPC over SMB: Samba and Windows NT Domain Internals
>
>
> ------------------------------
>
> Date: Thu, 23 Mar 2000 21:35:15 +0100
> From: Giulio Orsero <giulioo@pobox.com>
> To: samba@samba.org
> Subject: 2.0.7pre2: passwd change, log, ...
> Message-ID: <20000323203608.1D9852AE8E@i3.golden.dom>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 8BIT
>
> rh61, 2.2.14, 2.0.7pre2
>
> == 12)
> I cannot change password anymore from win9x control panel (changing with
> "$ smbpasswd" with sync, is ok).
> Last time I checked I used 2.0.6 and it worked perfectly.
>
> Logon from win95/win98SE to samba domain
> [2000/03/23 20:20:02, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:07, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:07, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:07, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:07, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:12, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:12, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:12, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:12, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:20:40, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 0
>
> Passwd change try (control panel):
> [2000/03/23 20:23:17, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:22, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:22, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:22, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:22, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:27, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:27, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:27, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
> [2000/03/23 20:23:27, 1]
> nmbd/nmbd_processlogon.c:process_logon_packet(70)
> process_logon_packet: Logon from 10.0.0.179: code = 7
>
> "Cannot find a domain controller"
>
> no log in log.smb
>
>
> $ nmblookup -S i4
> querying i4 on 10.0.0.255
> 10.0.0.7 i4<00>
> Looking up status of 10.0.0.7
> received 9 names
> I4 <00> - M <ACTIVE>
> I4 <03> - M <ACTIVE>
> I4 <20> - M <ACTIVE>
> ..__MSBROWSE__. <01> - <GROUP> M <ACTIVE>
> WORKGROUP <00> - <GROUP> M <ACTIVE>
> WORKGROUP <1b> - M <ACTIVE>
> WORKGROUP <1c> - <GROUP> M <ACTIVE>
> WORKGROUP <1d> - M <ACTIVE>
> WORKGROUP <1e> - <GROUP> M <ACTIVE>
> num_good_sends=0 num_good_receives=0
>
>
> == 13)
> log.smb (level 2) is full of
> pass_check_smb failed - invalid password for user [go]
> but the password is right and user go can access the share as uid go gid
> go.
>
>
> == 14)
> Sometime I get
> [2000/03/23 20:34:01, 0] lib/util_sock.c:set_socket_options(151)
> Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor)
> [2000/03/23 20:34:01, 0] lib/util_sock.c:set_socket_options(151)
> Failed to set socket option TCP_NODELAY (Error Bad file descriptor)
> [2000/03/23 20:34:01, 0] lib/util_sock.c:set_socket_options(151)
> Failed to set socket option SO_RCVBUF (Error Bad file descriptor)
> [2000/03/23 20:34:01, 0] lib/util_sock.c:set_socket_options(151)
> Failed to set socket option SO_SNDBUF (Error Bad file descriptor)
>
> Thanks.
>
> --
> giulioo@pobox.com
>
> ------------------------------
>
> End of SAMBA Digest 2460
> ************************