please take us off of the samba e-mail list for the time being thanks.
----- Original Message -----
From: <samba@samba.org>
To: Multiple recipients of list SAMBA <samba@samba.org>
Sent: Monday, October 25, 1999 5:44 AM
Subject: SAMBA digest 2283
> SAMBA Digest 2283
>
> For information on unsubscribing see http://samba.org/listproc/
> Topics covered in this issue include:
>
> 1) Speed problem: 3Com vs. crossover cable
> by Edward Schernau <ed@schernau.com>
> 2) Password Problem
> by Menno Scholten <m.scholten@wxs.nl>
> 3) Re: How to find out who is the LOCAL master ???
> by John LeMay <jlemay@njmc.com>
> 4) Re: PDC ability
> by Gerald Carter <cartegw@Eng.Auburn.EDU>
> 5) Hybrid configuration
> by gtroup@rfs.com.au
> 6) Re: semaphores and Solaris 7 8/99
> by Todd Pfaff <pfaff@edge.cis.mcmaster.ca>
> 7) RE: PDC ability
> by "Roeland M.J. Meyer" <rmeyer@mhsc.com>
> 8) Corrupted files with applications using Samba/NetaTalk-Server
> by Lars Martin <lars@softwarebuero.de>
>
> ----------------------------------------------------------------------
>
> Date: Sun, 24 Oct 1999 10:06:44 -0400
> From: Edward Schernau <ed@schernau.com>
> To: samba@samba.org
> Subject: Speed problem: 3Com vs. crossover cable
> Message-ID: <38131274.A27964D9@schernau.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> First of all, a crossover cable works just fine, provided you make
> it decently.
>
> Leave full-duplex and auto-sensing on.
>
> I had similar weirdness with a Win95b client (with DUN 1.3 installed)
> and a 486-33 RH 6.0 box running samba.
>
> Turns out that I nuked TCP/IP and reinstalled, and it is back
> up to where I think it ought to be, around 300 K/sec.
>
> --
> Edward Schernau http://www.schernau.com
> Network Architect mailto:ed@schernau.com
> Rational Computing Providence, RI, USA
>
> ------------------------------
>
> Date: Sun, 24 Oct 1999 16:55:07 +0200
> From: Menno Scholten <m.scholten@wxs.nl>
> To: samba@samba.org
> Subject: Password Problem
> Message-ID: <38131DCB.D188077C@wxs.nl>
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
> boundary="------------E95BF6B3F1086C028A90C8C2"
>
> This is a multi-part message in MIME format.
> --------------E95BF6B3F1086C028A90C8C2
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Hi there,
>
> I'm having a little trouble with Samba ( duh, otherwise I wouldn't
be
> writing to this list :)). It used to work just fine, but after I
> reinstalled my linux box, and samab with it I'm having a little trouble
> with the passwords. When I logon using my normal user account, and try
> to set my Samba password I get this error:
>
> $ smbpasswd
> Old SMB password:
> New SMB password:
> Retype new SMB password:
> smbpasswd: machine 127.0.0.1 rejected the session setup. Error was :
> ERRSRV - ER
> Rbadpw (Bad password - name/password pair in a Tree Connect or Session
> Setup are
> invalid.).
>
> This would mean that the Old SMB password is incorrect. The problem is,
> it isn't supposed to exist. I've never set that password before.
I've
> tried to enter my normal user password, leave it blank, but I doesn't
> work. Really desperate, I de-installed Samba, removed all the files,
> including the smbpasswd file, installed everything again, and still, the
> same problem. If I create a new user, I face the same problem. I have to
> enter an old ( non-existing ) password. If I login as root and then try
> to smbpasswd, it doesn't ask for the old password, but instead ask for
a
> new one.
>
> I'm really stuck here, perhaps anyone can help me.
> The SMB server is a 486 with Debian, kernel 2.2, Samba version 1.9.
I've
> added the simplified version of my smb.conf, the one I'm using now for
> Diagnostic purposes.
>
> Thnx in advance,
> Menno Scholten
>
>
> --------------E95BF6B3F1086C028A90C8C2
> Content-Type: text/plain; charset=us-ascii;
> name="smb.conf"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline;
> filename="smb.conf"
>
> ;
> ; /etc/smb.conf
> ;
> ; Sample configuration file for the Samba suite for Debian GNU/Linux
> ;
> ; Please see the manual page for smb.conf for detailed description of
> ; every parameter.
> ;
>
> [global]
> printing = bsd
> printcap name = /etc/printcap
> load printers = yes
> guest account = nobody
> invalid users = root
>
> ; "security = user" is always a good idea. This will require a
Unix
account> ; in this server for every user accessing the server.
> security = user
>
> ; Change this for the workgroup your Samba server will part of
> workgroup = SCHOLTEN
>
> server string = %h server (Samba %v)
>
> ; This socket options really speed up Samba under Linux, according to my
> ; own tests.
> socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096
SO_RCVBUF=4096>
> ; Passwords are encrypted by default. This way the latest Windows 95 and
NT> ; clients can connect to the Samba server with no problems.
> encrypt passwords = yes
>
> ; It's always a good idea to use a WINS server. If you want this server
> ; to be the WINS server for your network change the following parameter
> ; to "yes". Otherwise leave it as "no" and specify your
WINS server
> ; below (note: only one Samba server can be the WINS server).
> ; Read BROWSING.txt for more details.
> wins support = yes
>
> ; If this server is not the WINS server then specify who is it and
uncomment> ; next line.
> ; wins server = 172.16.0.10
>
> ; Please read BROWSING.txt and set the next four parameters according
> ; to your network setup. There is no valid default so they are commented
> ; out.
> os level = 65
> domain master = yes
> local master = yes
> preferred master = yes
>
> ; What naming service and in what order should we use to resolve host
names> ; to IP addresses
> name resolve order = lmhosts host wins bcast
>
> ; This will prevent nmbd to search for NetBIOS names through DNS.
> dns proxy = no
>
> ; Name mangling options
>
> preserve case = yes
> short preserve case = yes
>
> ; This boolean parameter controlls whether Samba attempts to sync. the
Unix> ; password with the SMB password when the encrypted SMB password in the
> ; /etc/smbpasswd file is changed.
> unix password sync = false
>
> ; For Unix password sync. to work on a Debian GNU/Linux system, the
following> ; parameters must be set (thanks to Culus for pointing this out):
> passwd program = /usr/bin/passwd %u
> passwd chat = *New\spassword:* %n\n *Re-enter\snew\spassword:* %n\n
*Password\schanged.* .>
> ; The following parameter is useful only if you have the linpopup package
> ; installed. The samba maintainer and the linpopup maintainer are
> ; working to ease installation and configuration of linpopup and samba.
> ; message command = /bin/sh -c '/usr/bin/linpopup "%f"
"%m" %s; rm %s' &
>
> ; The default maximum log file size is 5 MBytes. That's too big so this
> ; next parameter sets it to 1 MByte. Currently, Samba rotates log
> ; files (/var/log/{smb,nmb} in Debian) when these files reach 1000
KBytes.> ; A better solution would be to have Samba rotate the log file upon
> ; reception of a signal, but for now on, we have to live with this.
> max log size = 1000
>
> [homes]
> comment = Home Directories
> browseable = no
>
> ; By default, the home directories are exported read only. Change next
> ; parameter to "no" if you want to be able to write to them.
> read only = yes
>
> ; File creation mask is set to 0700 for security reasons. If you want to
> ; create files with group=rw permissions, set next parameter to 0775.
> create mask = 0700
>
> ; Directory creation mask is set to 0700 for security reasons. If you want
to> ; create dirs. with group=rw permissions, set next parameter to 0775.
> directory mask = 0700
>
> [printers]
> comment = All Printers
> browseable = no
> path = /tmp
> printable = yes
> public = no
> writable = no
> create mode = 0700
>
> [test]
> comment = Test share
> browseable = yes
> path = /tmp
> public = yes
> writeable = yes
>
> ; A sample share for sharing your CD-ROM with others.
> ;[cdrom]
> ; comment = Samba server's CD-ROM
> ; writable = no
> ; locking = no
> ; path = /cdrom
> ; public = yes
> ;
> ; The next two parameters show how to auto-mount a CD-ROM when the
> ; cdrom share is accesed. For this to work /etc/fstab must contain
> ; an entry like this:
> ;
> ; /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
> ;
> ; The CD-ROM gets unmounted automatically after the connection to the
> ;
> ; If you don't want to use auto-mounting/unmounting make sure the CD
> ; is mounted on /cdrom
> ;
> ; preexec = /bin/mount /cdrom
> ; postexec = /bin/umount /cdrom
>
>
> --------------E95BF6B3F1086C028A90C8C2--
>
>
> ------------------------------
>
> Date: Sun, 24 Oct 1999 13:01:27 -0400
> From: John LeMay <jlemay@njmc.com>
> To: unlisted-recipients:; (no To-header on input)
> Subject: Re: How to find out who is the LOCAL master ???
> Message-ID: <38133B67.1DA9234A@njmc.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Two utils exist in the ntreskit for this. The first is a gui tool called
> browmon.exe. The second is a console util called browstat.exe. I've
> personally never had luck with browstat, but browmon seems to work well.
>
> Another NT related tip if you are running wins - look for the entry in
> the WINS DB with the "1bh" indicator - that's the master
browser. As I
> recall, a NBTSTAT -a <machinename> will also show an entry for
> "..__MSBROWSE__." on the browser machine.
>
>
> Giulio Orsero wrote:
> >
> > On Sat, 23 Oct 1999 20:00:02 +1000, hai scritto:
> >
> > >On our network, our samba server seems to loose the local master
elections.> > >I dont have access to the samba server, but I want to find out who
is
the> > >local master.... how can I do this ???
> >
> > If you can telnet to samba server
> > nmblookup -M -
> >
> > else I think there is an utility in the nt reskit that do this.
> >
> > else from a win9x dow box do:
> > nbtstat -a <name of a pc>
> > for every pc of your lan till you find the one who registered the
> > .__MSBROWSE__.<01>
> > name
> >
> > --
> > giulioo@tiscalinet.it
>
> --
> John J. LeMay Jr.
> NJMC, LLC.
> http://www.njmc.com
>
> ------------------------------
>
> Date: Sun, 24 Oct 1999 21:23:28 +0000
> From: Gerald Carter <cartegw@Eng.Auburn.EDU>
> To: mwernig@aon.at
> Subject: Re: PDC ability
> Message-ID: <381378D0.BCDAF67D@eng.auburn.edu>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> mwernig wrote:
> >
> > well, folks, here are two questions that will show
> > that i`m not really up to date:
> > 1) Can samba act as PDC already?
>
> Unofficially, this is a 'Yes.' See the Samba NT Domain
> FAQ linked under the documentation page on the Samba
> site.
>
> > 2) Can samba serve Win2K clients?
>
> For file serving, this would also be a 'Yes'. If you
> mean serving in the sense of a domain controller, this
> would be a 'no'
>
>
>
>
>
> Cheers,
> jerry
> ________________________________________________________________________
> Gerald ( Jerry ) Carter
> Engineering Network Services Auburn University
> jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw
>
> "...a hundred billion castaways looking for a home."
> - Sting "Message in a Bottle" (
1979 )
>
> ------------------------------
>
> Date: Mon, 25 Oct 1999 09:08:59 +1000
> From: gtroup@rfs.com.au
> To: samba@samba.org
> Subject: Hybrid configuration
> Message-ID: <4A256814.007F778B.00@RFS_SMTP.RFS.COM.AU>
> Mime-Version: 1.0
> Content-type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
>
>
> I am having some trouble setting up a hybrid configuration. After
searching the> archives, I can find a reference that suggests embedding one smb.conf
within> another, but I cannot seem to configure this to work. Are there any
> instructions available with examples?
>
> Also with this configuration will SWAT still work?
>
> Regards,
>
> GTR
>
>
>
>
____________________________________________________________________________
____> **********************************************************************
> This email and any attachments are confidential and are
> intended solely for the recipient. The contents and any
> attachments are the opinion of the sender and not
> necessarily that of RFS Australia
> **********************************************************************
>
>
>
> ------------------------------
>
> Date: Sun, 24 Oct 1999 22:26:29 -0400 (EDT)
> From: Todd Pfaff <pfaff@edge.cis.mcmaster.ca>
> To: Kevin Van Der Hart <kvanderhart@vermeermfg.com>
> Subject: Re: semaphores and Solaris 7 8/99
> Message-ID:
<Pine.GSO.4.10.9910242209360.5187-100000@edge.cis.mcmaster.ca>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> jeremy allison posted a patch to deal with this issue back in july. have
> a look through the samba archives or see this dejanews article:
>
> # You can view this message and the related discussion by following this
link:> #
http://www.deja.com/dnquery.xp?search=thread&svcclass=dnserver&recnum=%3c7nq
44j$1h@dfw-ixnews3.ix.netcom.com%3e%231/1> # We hope to see you soon at Deja.com.
>
> unfortunately, this patch has not always solved the problem for me. it
> seems to work on some solaris 7 systems and not others. i have seen this
> problem with various installation of solaris 7 (mostly 5/99) on both 32-
> and 64-bit kernels. i have never been able to pin down in which cases it
> does or does not work. i have even seen the case where samba is running
> fine after a reboot but then exhibits this locking problem if i manually
> stop and restart smbd sometime later.
>
> in some cases, i have been able to eliminate the problem by reverting to
> an older build of samba-2.0.5a made on a solaris 2.5 system, without the
> aforementioned patch.
>
> just out of curiosity, could you try some tests?
>
> 1) starting smbd and nmbd from an init script and reboot the ultra 10
> 2) apply the patch, rebuild and restart
>
> did either of these help? if (1), then try manually stopping and starting
> smbd. still ok?
>
> --
> Todd Pfaff \ Email: pfaff@mcmaster.ca
> Computing and Information Services \ Voice: (905) 525-9140 x22920
> ABB 132 \ FAX: (905) 528-3773
> McMaster University \
> Hamilton, Ontario, Canada L8S 4M1 \
>
> On Sun, 24 Oct 1999, Kevin Van Der Hart wrote:
>
> > I just installed the 8/99 release of Solaris 7 on three Sun Ultra
10's
and> > it seems to have broken Samba. I am running Samba 2.0.5a and it works
fine> > on an Ultra 10 running the 5/99 release of Solaris 7. All of the Ultra
10's> > are using the 64 bit kernel. This is the errors that I am getting.
> >
> > [1999/10/22 21:09:56, 0] locking/shmem_sysv.c:sysv_shm_open(597)
> > ERROR: root did not create the semaphore
> > [1999/10/22 21:09:56, 0] locking/locking.c:locking_init(174)
> > ERROR: Failed to initialise share modes
> >
> > I used abd to compare the kernel settings for shminfo and seminfo and
they> > are indentical between the 2 releases. I also verified the samba
install. I> > am running smbd and nmbd as a daemon not through inetd. Thanks in
advance.> >
> > Kevin Van Der Hart
> > LAN Administrator
> > Vermeer Mfg Co
> > kvanderhart@vermeermfg.com
>
>
> ------------------------------
>
> Date: Mon, 25 Oct 1999 00:52:23 -0700
> From: "Roeland M.J. Meyer" <rmeyer@mhsc.com>
> To: <cartegw@Eng.Auburn.EDU>,
> "'Multiple recipients of list SAMBA'"
<samba@samba.org>
> Subject: RE: PDC ability
> Message-ID: <002701bf1ebd$e02bc3c0$ecaf6cc7@lvrmr.mhsc.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> I heard a nasty rumor that W2K was supposed to use Kerberos
authentication.> However, knowing MS, it would probably be an incompatible proprietary
verion> of Kerberos.
>
> > -----Original Message-----
> > From: samba@samba.org [mailto:samba@samba.org]On Behalf Of
> > Gerald Carter
> > Sent: Sunday, October 24, 1999 2:20 PM
> > To: Multiple recipients of list SAMBA
> > Subject: Re: PDC ability
> >
> >
> > mwernig wrote:
> > >
> > > well, folks, here are two questions that will show
> > > that i`m not really up to date:
> > > 1) Can samba act as PDC already?
> >
> > Unofficially, this is a 'Yes.' See the Samba NT Domain
> > FAQ linked under the documentation page on the Samba
> > site.
> >
> > > 2) Can samba serve Win2K clients?
> >
> > For file serving, this would also be a 'Yes'. If you
> > mean serving in the sense of a domain controller, this
> > would be a 'no'
> >
> >
> >
> >
> >
> > Cheers,
> > jerry
> > ______________________________________________________________
> > __________
> > Gerald ( Jerry ) Carter
> > Engineering Network Services Auburn
> > University
> > jerry@eng.auburn.edu
> > http://www.eng.auburn.edu/users/cartegw
> >
> > "...a hundred billion castaways looking for a home."
> > - Sting "Message in a
> > Bottle" ( 1979 )
> >
>
>
> ------------------------------
>
> Date: Mon, 25 Oct 1999 13:53:37 +0200
> From: Lars Martin <lars@softwarebuero.de>
> To: samba@samba.org
> Subject: Corrupted files with applications using Samba/NetaTalk-Server
> Message-ID: <99102514051600.00544@mohammed>
> Content-Type: text/plain
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8BIT
>
>
> Hi all,
>
> I?ve read some mailings regarding corrupted files with application
> using a Samba-Box as a File-Server. We?ve the same problem with
> SolidWorks (a CAD-System) under NT4.0 Client and FreeHand under
> MacOS (using NetaTalk). I?ve installed Samba 2.0.3 from SuSE 6.1.
> The solutions I read were:
> 1. upgrade Samba to at least 2.0.5
> 2. switch off the NT-registrykey for fs-caching
> Does anybody else have some experiences with that problem?
>
> Regards,
> Lars
> --
> ________________________________________________________________
> Lars Martin lars@softwarebuero.de
> softwarebuero m&b (SMB) http://www.softwarebuero.de
>
> ------------------------------
>
> End of SAMBA Digest 2283
> ************************
>
