SAMBA digest 2018
neud
neud at zv.fhg.de
Fri Mar 12 19:18:14 GMT 1999
Mr. Kuehn never works by us. Please actualize your Mail-Listings.
(kuehn at zv.fhg.de)
Thank you
samba at samba.org schrieb:
> SAMBA Digest 2018
>
> For information on unsubscribing see http://samba.org/listproc/
> Topics covered in this issue include:
>
> 1) Re: SAMBA digest 2017
> by neud <neud at zv.fhg.de>
>
> ----------------------------------------------------------------------
>
> Date: Fri, 12 Mar 1999 16:46:17 +0100
> From: neud <neud at zv.fhg.de>
> To: samba at samba.org
> Subject: Re: SAMBA digest 2017
> Message-ID: <36E936C9.8CEDF5D9 at zv.fhg.de>
>
> Mr. Kuehn never works by us. Please actualize your Mail-Listings.
>
> Thank you
>
> samba at samba.org schrieb:
>
> > SAMBA Digest 2017
> >
> > For information on unsubscribing see http://samba.org/listproc/
> > Topics covered in this issue include:
> >
> > 1) Re: I really need help with SAMBA!!
> > by "Stephen L Arnold" <arnold.steve at ensco.com>
> > 2) Re: Unable to Browse or Connect From Win98 to Samba 2.0.3
> > by CLIFFORD ILKAY <clifford_ilkay at dinamis.com>
> > 3) Re: I really need help with SAMBA!!
> > by Paul Sherwin <psherwin at telinco.co.uk>
> > 4) RE: guest connection to non-public shares
> > by "Sanders, Peter" <Peter.Sanders at dsto.defence.gov.au>
> > 5) Having to be explicit about IPC$
> > by "Sanders, Peter" <Peter.Sanders at dsto.defence.gov.au>
> > 6) problems with smbpasswd in samba-2.0.2+
> > by Tom Lieuallen <toml at ENGR.ORST.EDU>
> > 7) Samba and DNS, the relation?
> > by "Cary T. Conrad" <conrad at messagesecure.com>
> > 8) attachment problem
> > by "Stephen L Arnold" <arnold.steve at ensco.com>
> > 9) Re: SAMBA digest 2016
> > by "Stephen L Arnold" <arnold.steve at ensco.com>
> > 10) File permissions/ownership lost?
> > by David Bullock <davidb at loftuscomp.com.au>
> > 11) Re: Linux Samba almost setup
> > by "Tom Roche" <tom_roche at ncsu.edu>
> > 12) RE: ERROR:set_share_mode shmops->shm_alloc fail!
> > by Terry Dwyer 61 8 9491 5161 <tdwyer at io.telstra.com.au>
> > 13) USENIX/SAGE Conferences of Interest to System/Network Admins
> > by Cynthia Deno <cynthia at usenix.org>
> > 14) smbclient 2.0.(2|3) with WfWg Looping in FIND_NEXT?
> > by Jim Tittsler <jwt at dskk.co.jp>
> > 15) RE : Problems installing ORACLE products for Win95 on a Samba Network Drive.
> > by "=?iso-8859-1?Q?David_Scarlatti_Jim=E9nez?=" <scarla at BDE-sa.es>
> > 16) Remote browsing
> > by Patrick Harrold <patrickh at nasco-inc.com>
> > 17) share mode locking: behaviour inconsistency.
> > by Paul Jakma <paul.jakma at compaq.com>
> >
> > ----------------------------------------------------------------------
> >
> > Date: Thu, 11 Mar 1999 11:42:31 -0800
> > From: "Stephen L Arnold" <arnold.steve at ensco.com>
> > To: samba at samba.org
> > Subject: Re: I really need help with SAMBA!!
> > Message-ID: <199903111936.OAA06924 at devonshire.cnchost.com>
> >
> > When the world was young, Alex Yu <ayu1 at nycap.rr.com> carved some
> > runes like this:
> >
> > > I don't want smb to send clear text passwd, because there might be a
> > > chance that people will sniff my subnet. BUT I don't want to have 2
> > > seperate passwds. I want samba to share /etc/passwd passwords. All I
> > > need is SPEED and get PASSWORD share working. PLEASE HELP ME!!!
> >
> > The basic samba settings should be fine (speed-wise) unless
> > something else is hosed (network setup, flaky NIC, etc). On a 10
> > Mbs ethernet, I get 750-900 k/sec on both SMB and ftp transfers.
> > SMB is fastest between win95 boxes, and slowest between NT4 and
> > samba. ftp transfers are pretty consistent (about 850 k/sec)
> > across platforms. Also, our network has very little traffic.
> > Another guy said (a while back) that Netblooie was sucking up about
> > 70% of the available bandwidth on his network... I'll attach my
> > smb.conf, but you'll have to adjust yourself if you're using 2.x
> > (I'm still running 1.9.18p8). I suppose you've played with the
> > read-raw and other settings. Also, strict locking can slow things
> > down quite a bit. Check the speed.txt docs for more ideas.
> >
> > Encrypted passwords should work fine; just make sure you create
> > smbpasswd in the right place for your setup and either add each
> > user manually, or use the update encrypted switch (while using
> > plaintext passwords) until all passwords have been updated in
> > smbpasswd. You can use the unix-passwd-sync option as well.
> >
> > Here is my setup:
> >
> > [global]
> > #==================Shortened for the list==================
> > name resolve order = lmhosts host bcast
> > guest account = ftp
> > log file = /var/log/samba/log.%m
> > max log size = 50
> > security = user
> > username map = /etc/smbusers
> >
> > socket options = TCP_NODELAY
> >
> > local master = yes
> > os level = 65
> > domain master = yes
> > preferred master = yes
> > wins support = no
> > dns proxy = no
> > preserve case = yes
> > short preserve case = yes
> > mangle case = yes
> >
> > #================== Share Definitions ====================
> > [homes]
> > comment = Home Directory
> > browseable = no
> > writable = yes
> > alternate permissions = yes
> > force directory mode = 0755
> > create mode = 0644
> >
> > [printers]
> > comment = All Printers
> > path = /var/spool/samba
> > browseable = no
> > # Set public = yes to allow user 'guest account' to print
> > guest ok = no
> > writable = no
> > printable = yes
> >
> > # This one is useful for people to share files
> > [tmp]
> > comment = Temporary file space
> > path = /tmp
> > read only = no
> > public = yes
> >
> > # A publicly accessible directory, but read only, except for admin.
> > [public]
> > comment = HTML Document Tree
> > path = /home/httpd
> > public = yes
> > writable = yes
> > printable = no
> > write list = arnold, root, admin, sarnold
> >
> > # Publicly accessible directory, but read-only, except for admin.
> > # This is the /usr/doc tree
> > [docs]
> > comment = Linux docs
> > path = /usr/doc
> > public = yes
> > writable = yes
> > printable = no
> > write list = arnold, root, admin, sarnold
> >
> > [source]
> > comment = Source Code
> > path = /usr/src
> > valid users = [list of valid users]
> > public = no
> > writable = yes
> > printable = no
> >
> > ****************************************************************
> > Stephen L. Arnold Senior Systems Engineer
> > ENSCO Inc. email: arnold.steve at ensco.com
> > P.O. Box 5488 www: http://www.ensco.com
> > Vandenberg AFB, CA 93437 voice: 805.806.8838
> > fax: 805.734.4779
> > #include <std_disclaimer.h>
> > ****************************************************************
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 15:29:16 -0500
> > From: CLIFFORD ILKAY <clifford_ilkay at dinamis.com>
> > To: samba at samba.org
> > Subject: Re: Unable to Browse or Connect From Win98 to Samba 2.0.3
> > Message-ID: <3.0.6.32.19990311152916.00a9e780 at dinamis.com>
> >
> > Hi,
> >
> > I solved the problem with the inability to logon locally with a valid user.
> > I had the wrong permissions on the common directory. The user foo did not
> > have any permissions on /common. Once I granted permission, I could browse
> > /common using the smbclient program. However, I am still unable to browse
> > the server or connect from a Win 98 client. Typing the following at a DOS
> > prompt:
> >
> > net view \\kiwi\common
> >
> > returns, after a long time, the following message:
> >
> > Error 54: The network is currently busy processing other requests or is out
> > of resources. Try again later, or verify your network configuration to be
> > sure that enough network resources are specified.
> >
> > First, there are only two machines on this network, the Linux server
> > running Samba, and the Windows 98 client. Second, if I disconnect the Win
> > 98 machine from this network and connect it to another network where there
> > is an NT Server, the Win 98 machine behaves exactly as it should with the
> > NT Server. Finally, the Ethernet card in the Linux server is fine since I
> > have had it connected to a cable modem. My kingdom for a solution:)
> >
> > At 10:51 AM 3/11/99 -0500, I wrote:
> > >Configuration
> > >-------------
> > >Client workstation: Windows 98, encrypted passwords, netbios name = montreal
> > >Server: Red Hat 5.2, kernel 2.0.36, Samba 2.0.3, netbios name = kiwi
> > >I can connect locally as root as follows:
> > >
> > >smbclient \\\\kiwi\\common
> > >
> > >If I attempt to connect as a different user, by typing:
> > >
> > >smbclient \\\\kiwi\\common -U foo
> > >
> > >where foo is a user who has been added to the smbpasswd file by doing a
> > >smbpasswd -a foo, the server responds with:
> > >
> > >Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> > >Got a positive name query response from 192.168.1.1 (192.168.1.1)
> > >Server time is Wed Mar 10 01:55:35 1999
> > >Timezone is UTC-5.0
> > >Password:
> > >
> > >I typed in the correct password and the server returned:
> > >
> > >Domain=[UCBL] OS=[Unix] Server=[Samba 2.0.3] security=user
> > >SMBtconX failed. ERRSRV - ERRinvnetname (Invalid network name in tree
> > >connect.) Perhaps you are using the wrong sharename, username or password?
> > >
> > >I definitely have the right sharename, username, and password.
> >
> > Regards,
> >
> > Clifford Ilkay
> > Dinamis Corporation
> > 3266 Yonge Street, Suite 1419
> > Toronto, Ontario
> > Canada M4N 3P6
> >
> > Voice/Fax: 416-410-3326
> >
> > mailto:clifford_ilkay at dinamis.com
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 21:10:46 +0000
> > From: Paul Sherwin <psherwin at telinco.co.uk>
> > To: samba at samba.org
> > Cc: ayu1 at nycap.rr.com
> > Subject: Re: I really need help with SAMBA!!
> > Message-ID: <3.0.6.32.19990311211046.007a33a0 at mail.telinco.co.uk>
> >
> > At 19:03 11/03/99 +1100, you wrote:
> >
> > >I spent more than 20 hours and tried to get Samba work along with Winbloz
> > >"NT". But I failed many many many times. The speed is very slow. It
> > >takes more than 2 mins to login and change folder. If your configuration
> > >is what I need, would you please send me your configuration and tell me how
> > >to speed NT up?
> > >
> > If you are getting 2 minute delays connecting to a Samba share, You have
> > networking problems, not Samba problems. The most likely explanation is you
> > have a DNS lookup failure which is timing out. Try putting the IP address
> > of your NT workstation in /etc/hosts. If this doesn't fix things, you may
> > have a problem elsewhere in the network. If your Samba configuration is
> > wrong, the connection request will usually fail within a second or two.
> >
> > Best regards, Paul
> >
> > Paul Sherwin Consulting
> > 22 Monmouth Road, Oxford OX1 4TD, UK
> > Phone +44 (0)1865 721438
> > Fax +44 (0)1865 434331
> > Pager +44 (0)7666 797228
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 08:39:10 +1100
> > From: "Sanders, Peter" <Peter.Sanders at dsto.defence.gov.au>
> > To: "'samba at samba.org'" <samba at samba.org>
> > Subject: RE: guest connection to non-public shares
> > Message-ID: <F98649A5EE8ED11190160000F80275653EAFD1 at exchvic3.dsto.defence.gov.au>
> >
> > > [snip]
> > >> guest account = guest
> >
> > >Have you tried a different guest account (such as nobody or ftp)?
> >
> > >Just a thought, Steve
> >
> > Yes, I have tried setting the guest account to nobody. No change.
> > BTW. The user guest has a home directory, smbpasswd entry etc.
> > but a blank password. (ie NO PASSWORD in smbpasswd file).
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 08:47:17 +1100
> > From: "Sanders, Peter" <Peter.Sanders at dsto.defence.gov.au>
> > To: "'samba at samba.org'" <samba at samba.org>
> > Subject: Having to be explicit about IPC$
> > Message-ID: <F98649A5EE8ED11190160000F80275653EAFD2 at exchvic3.dsto.defence.gov.au>
> >
> > I'm running Linux 2.0.30 with versions of Samba from 1.9.18p4 on and
> > am now running 2.0.2.
> >
> > I have found that people on our network who do not have an entry in
> > the smbpasswd file on my Linux box cannot browse the Linux box. When
> > they make an attempt to do so, they are prompted:
> > "Password for IPC$" or similar.
> > I can overcome this by adding an entry to my smb.conf as follows.
> >
> > [IPC$]
> > public = yes
> >
> > Is this normal behaviour?
> >
> > =====================================
> > _--_|\ peter.sanders at dsto.defence.gov.au (Business)
> > / DSTO \ Combatant Protection & Nutrition Branch, AMRL.
> > \_.--._/ Defence Science & Technology Organisation
> > v Fax : 61-3-9626 8410 Voice: 61-3-9626 8411
> > Peter Sanders
> > sandersp at melbpc.org.au (Private)
> > Voice: 61-3-9337-6612
> > BMW K100RT (Brunnhilde the Blue)
> > =====================================
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 14:44:56 -0800
> > From: Tom Lieuallen <toml at ENGR.ORST.EDU>
> > To: samba at samba.org
> > Subject: problems with smbpasswd in samba-2.0.2+
> > Message-ID: <199903112244.OAA02068 at engr.orst.edu>
> >
> > I am having difficulties with smbpasswd in samba 2.0.2 and 2.0.3
> > on a Solaris 2.6 machine. The same config file and the smbpasswd
> > binary from samba 1.9.18p10 works just fine.
> >
> > order 26% ./smbpasswd -r hera -D 4
> > Old SMB password:
> > New SMB password:
> > Retype new SMB password:
> > resolve_name: Attempting wins lookup for name hera<0x20>
> > bind succeeded on port 0
> > nmb packet from 128.193.54.101(137) header: id=12269 opcode=Query(0) response=No
> > header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=No
> > header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
> > question: q_name=HERA<20> q_type=32 q_class=1
> > nmb packet from 128.193.54.101(137) header: id=12269 opcode=Query(0) response=Yes
> > header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
> > header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
> > answers: nmb_name=HERA<20> rr_type=32 rr_class=1 ttl=0
> > answers 0 char `...6e hex 600080C13665
> > Got a positive name query response from 128.193.54.101 ( 128.193.54.101 )
> > Connecting to 128.193.54.101 at port 139
> > machine hera rejected the password change: Error was : User has insufficient privilege.
> > Failed to change password for tomltest
> >
> > Here are the relevant portions of the config file:
> >
> > [global]
> > security = domain
> > encrypt passwords = true
> > guest account = samba
> > name resolve order = wins host
> > workgroup = ENGINEERING
> > password server = hera
> >
> > And the user certainly does have priveleges to change its password.
> > I was able to successfully change it with the older version.
> >
> > Password last set 3/11/99 2:11 PM
> > Password expires Never
> > Password changeable 3/11/99 2:11 PM
> > Password required Yes
> > User may change password Yes
> >
> > Thanks in advance for any ideas or help.
> >
> > ---------------------------------------------------------------------------
> > Tom Lieuallen Phone: 541.737.6784
> > Oregon State University Fax: 541.737.1805
> > College of Engineering Email: toml at engr.orst.edu
> > Network Research Assistant
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 18:03:02 +0500
> > From: "Cary T. Conrad" <conrad at messagesecure.com>
> > To: samba at samba.org
> > Subject: Samba and DNS, the relation?
> > Message-ID: <4.1.19990311170241.03a1da60 at 192.9.200.5>
> >
> > We recently experienced "loss of service" with our Internet provider and as
> > a result none of our PC's could log-on to Samba Shares. As soon as the
> > service was restored all was well.
> >
> > Questions:
> > Is DNS necessary to run samba?
> > If not, how should naming be setup?
> > Do all of the clients need forward and reverse entries?
> >
> > I guess what I am asking is there a definitive way to setup naming for
> > local operation?
> > I have the Blair book in front of me now, Hhhhmmmm.........
> >
> > Many thanks in advance.
> >
> > CC
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 16:27:59 -0800
> > From: "Stephen L Arnold" <arnold.steve at ensco.com>
> > To: samba at samba.org
> > Subject: attachment problem
> > Message-ID: <199903120021.TAA00319 at devonshire.cnchost.com>
> >
> > Yo Dudes and Dudettes:
> >
> > A binhex attachment caused the samba digest 2016 to truncate a few
> > lines into the attachment, thus losing the last five messages in
> > the digest. The listserv software is apparently a bit dated, and
> > can't handle much other than text. Until the samba guys have
> > updated the list software, please use inline text only. Thanks.
> >
> > Steve
> >
> > ****************************************************************
> > Stephen L. Arnold Senior Systems Engineer
> > ENSCO Inc. email: arnold.steve at ensco.com
> > P.O. Box 5488 www: http://www.ensco.com
> > Vandenberg AFB, CA 93437 voice: 805.806.8838
> > fax: 805.734.4779
> > #include <std_disclaimer.h>
> > ****************************************************************
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 16:27:59 -0800
> > From: "Stephen L Arnold" <arnold.steve at ensco.com>
> > To: samba at samba.org
> > Subject: Re: SAMBA digest 2016
> > Message-ID: <199903120021.TAA00329 at devonshire.cnchost.com>
> >
> > When the world was young, <clifford_ilkay at dinamis.com> carved some
> > runes like this:
> >
> > > Unfortunately, I am still not able to browse or connect from my
> > > Windows 98 client. I also cannot connect locally with smbclient
> > > with any user other than root.
> >
> > Everything looks okay, but I seem to recall a problem in the stock
> > RedHat 5.2 config where the localhost line in /etc/hosts was
> > screwed up (ie, I think you're having a name resolution problem).
> >
> > Questions:
> >
> > Why did you take the host file out of:
> >
> > > name resolve order = wins lmhosts bcast
> >
> > Do you have a local DNS? I'm running named and samba under RH52 at
> > home (but I don't have win98) with no trouble. I'm no expert, but
> > I think you need /etc/hosts (the fixed version). I'll send you
> > mine from home tonight.
> >
> > Steve
> >
> > ******************************************************************
> > Stephen L Arnold http://www.rain.org/~sarnold
> > #include <std_disclaimer.h>
> > ******************************************************************
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 12:19:14 +1030
> > From: David Bullock <davidb at loftuscomp.com.au>
> > To: "'T.D.Lee at durham.ac.uk'" <T.D.Lee at durham.ac.uk>, "'samba at samba.org'" <samba at samba.org>
> > Subject: File permissions/ownership lost?
> > Message-ID: <01BE6C82.8CF3F8A0 at SARAH>
> >
> > > Can samba be persuaded to maintain the owner/group-owner of the
> > > original file? Or is this a "feature" of the way WORD/Excel/etc work
> > > (create new file, delete old, with no owner/mode retention)?
> >
> > As mentioned in another reply, Word and Excel create new
> > files rather than overwrite the existing files, so Samba/Unix
> > correctly assign the new ownership to 'updated' files.
> >
> > By using chmod g+s for the directory in conjunction with
> > force create mode, you can get reasonable control for
> > access to all files in a directory.
> >
> > If it is of interest, we have a set of mods which we make
> > to Samba for our clients which allows us to set up certain
> > smb.conf settings (force create mode, admin user, and
> > a few others) per directory including newly created
> > directorie, rather than per share as in standard samba.
> >
> > Once set up, samba looks after itself without extra admin
> > for most business use, and the users access all their
> > documents, public, workgroup or private, through a single
> > share with the appropriate security supplied by Unix and
> > maintained by Samba.
> >
> > These mods have the potential to also maintain the same
> > file ownership for word docos etc, but I haven't needed to
> > do it.
> >
> > BTW, the g+s setting for a directory trick breaks with
> > Samba (with Unix really) when a file with a different group
> > ownership is moved into the directory. The moved file
> > retains its group ownership. I keep meaning to add a
> > mod for this, but in practice our clients have not hit that
> > problem.
> >
> > David Bullock
> > Loftus Computing Services
> > Adelaide, South Australia
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 22:36:14 -0500
> > From: "Tom Roche" <tom_roche at ncsu.edu>
> > To: <lug at csc.ncsu.EDU>, <samba at samba.org>
> > Subject: Re: Linux Samba almost setup
> > Message-ID: <s6e84583.041 at 152.7.128.36>
> >
> > I got a number of responses to my last post; thanks to all. I
> > implemented them in /etc/smb.conf as follows:
> >
> > * Change
> >
> > > workgroup = MYGROUP
> >
> > to
> >
> > > workgroup = SDL.CSC.NCSU
> >
> > (the group in which the client resides).
> >
> > * Change
> >
> > > ; hosts allow = 192.168.1. 192.168.2. 127.
> >
> > to
> >
> > > hosts allow = 152.1. 127.
> >
> > * Change
> >
> > > ; interfaces = 192.168.12.2/24 192.168.13.2/24
> >
> > to
> >
> > > interfaces = 152.1.61.159/255.255.0.0
> >
> > * By far the greatest number of responses said to change
> >
> > > ; encrypt passwords = yes
> >
> > to
> >
> > > encrypt passwords = yes
> >
> > * then, as described in .../samba-1.9.18p10/docs/ENCRYPTION.txt:
> >
> > > To generate the smbpasswd file from your /etc/passwd file use the
> > > following command :-
> >
> > > cat /etc/passwd | mksmbpasswd.sh >/usr/local/samba/private/smbpasswd
> >
> > > The mksmbpasswd.sh program is found in the Samba source directory. By
> > > default, the smbpasswd file is stored in :-
> >
> > > /usr/local/samba/private/smbpasswd
> >
> > > The owner of the /usr/local/samba/private directory should be set to
> > > root, and the permissions on it should be set <by> :-
> >
> > > chmod 500 /usr/local/samba/private
> >
> > > Likewise, the smbpasswd file inside the private directory should be
> > > owned by root and the permissions on is should be set by the command
> > :-
> >
> > > chmod 600 smbpasswd.
> >
> > killall -HUP inetd, and run the diagnostics. Retrogression: I don't
> > even pass all of test 7. From
> >
> > > smbclient '\\BACKPACK\TMP' -U guest
> >
> > I get
> >
> > > Added interface ip=152.1.61.159 bcast=152.1.255.255 nmask=255.255.0.0
> > > Server time is Thu Mar 11 22:00:15 1999
> > > Timezone is UTC-5.0
> > > Domain=[SDL.CSC.NCSU] OS=[Unix] Server=[Samba 1.9.18p10]
> > > connected as guest security=user
> >
> > as before. But
> >
> > > smbclient '\\BACKPACK\TMP' -U tlroche
> >
> > which worked previously, gets (broken for readability)
> >
> > > Added interface ip=152.1.61.159 bcast=152.1.255.255 nmask=255.255.0.0
> > > Server time is Thu Mar 11 22:00:31 1999
> > > Timezone is UTC-5.0
> > > Session setup failed for username=tlroche workgroup=SDL.CSC.NCSU
> > > myname=BACKPACK destname=BACKPACK ERRSRV - ERRbadpw
> > > (Bad password - name/password pair in a Tree Connect
> > > or Session Setup are invalid.)
> > > You might find the -U, -W or -n options useful
> > > Sometimes you have to use `-n USERNAME' (particularly with OS/2)
> > > Some servers also insist on uppercase-only passwords
> >
> > net view and net use also fail differently:
> >
> > > C:\WINNT\Profiles\tlroche\Desktop>net view \\BACKPACK
> > > System error 86 has occurred.
> > > The specified network password is not correct.
> >
> > Note that I'm logged into the client as 'tlroche', and that the
> > server
> > also has an account 'tlroche' (which can be seen in passwd and
> > smbpasswd)
> > using the same password.
> >
> > > C:\WINNT\Profiles\tlroche\Desktop>net use x: \\BACKPACK\TMP
> > /user:guest
> > > The password is invalid for \\BACKPACK\TMP.
> > > Type the password for \\BACKPACK\TMP:
> > > System error 86 has occurred.
> > > The specified network password is not correct.
> >
> > * So I'm now sure the passwords are the problem, though why this would
> > fail on a public share using 'guest' I can't begin to say.
> >
> > I note that /usr/doc/samba-1.9.18p10/docs/DIAGNOSIS.txt says
> >
> > > TEST 7: <snip>
> >
> > > If it says "bad password" then the likely causes are:
> >
> > > - you have shadow passords (or some other password system) but didn't
> > > compile in support for them in smbd
> >
> > How would I check to see if I have shadow passwords?
> >
> > > - your "valid users" configuration is incorrect
> >
> > [tmp] has "public = yes", but I add "valid users = guest tlroche
> > root" for the hell of it.
> >
> > > - you have a mixed case password and you haven't enabled the
> > "password
> > > level" option at a high enough level
> >
> > No mixed case ...
> >
> > > - the "path =" line in smb.conf is incorrect. Check it with testparm
> >
> > /tmp is correct (I'm not completely incompetent :-)
> >
> > > - you enabled password encryption but didn't create the SMB encrypted
> > > password file
> >
> > It's there in /usr/local/samba/private/smbpasswd
> >
> > > - your user does not have an entry in the smbpassword file
> >
> > ... and it has entries for guest, tlroche, root, etc.
> >
> > killall -HUP inetd, and run the diagnostics: no change.
> >
> > * I do
> >
> > > testparm smb.conf > testparm.out
> >
> > and see
> >
> > > smb passwd file = /etc/smbpasswd
> >
> > Hmm, that's not what the docs say. I add
> >
> > > smb passwd file = /usr/local/samba/private/smbpasswd
> >
> > to the [global] block, just under
> >
> > > encrypt passwords = yes
> >
> > killall -HUP inetd, and run the diagnostics: no change.
> >
> > OK, passwords are the problem !-) Can anyone suggest a solution?
> > I can send testparm.out and smb.conf as desired.
> >
> > Please note again that my objective is to provide my development group
> > with a more secure and usable way to access our Linux web/appserver
> > than FTP. I need _only_ to share disk on the Linux Samba server using
> > password encryption. Your assistance is appreciated; meanwhile I'm
> > gonna try my hand at ssh/scp (usability be damned :-)
> >
> > Tom_Roche at ncsu.edu
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 12:29:33 +0800 (WST)
> > From: Terry Dwyer 61 8 9491 5161 <tdwyer at io.telstra.com.au>
> > To: samba at samba.org
> > Subject: RE: ERROR:set_share_mode shmops->shm_alloc fail!
> > Message-ID: <Pine.BSF.3.91.990312120932.3607B-100000 at io.telecom.com.au>
> >
> > I had a problem similar to yours that I've recently solved. I'm running
> > Samba 2.0.2 under FreeBSD-2.2.8-Stable(11/03/1999)
> >
> > My error message was slightly different to yours, and only occured when
> > starting smbd and nmbd. It was to the effect that IPC$ services were
> > unavailable and identified a call to a routine that seemed to want to
> > allocate SysV Shared memory.
> >
> > I recompiled a new kernel with 1MB of Shared memory (SYSV_SHM) and the
> > problem went away.
> >
> > Considering that every version of Samba up to the most recent I had run
> > (1.9.18) was happy with 256KB of SYSV_SHM, needing to provide 1MB is a bit
> > of a jump!
> >
> > I hope this helps to point you in the right direction.
> >
> > > Date: Thu, 11 Mar 1999 09:32:25 -0600
> > > From: Chad Campbell <Chad.Campbell at innovision.com>
> > > To: Samba List <samba at samba.org>, samba-ntdom at samba.org
> > > Subject: ERROR:set_share_mode shmops->shm_alloc fail!
> > > Message-ID: <36E7E209.BD935859 at innovision.com>
> > >
> > > We're getting lots of error messages like "ERROR:set_share_mode
> > > shmops->shm_alloc fail!" in our logs. I suspect this might be the root
> > > cause of lots of other problems we've been seeing - like the "del *.*"
> > > problem I reported a couple of days ago, and network installed software
> > > like Word closing without reporting any errors. These errors are always
> > > preceded by another error related to locking shmem_sysv.c. Here is one
> > > sequence:
> > >
> > > [1999/03/11 08:19:00, 0] locking/shmem_sysv.c:shm_alloc(214)
> > > ERROR shm_alloc : alloc of 132 bytes failed
> > > [1999/03/11 08:19:00, 0] locking/locking_shm.c:shm_set_share_mode(435)
> > > ERROR:set_share_mode shmops->shm_alloc fail!
> > >
> > > I've attached a full log from this morning to give a broader view of
> > > what's going on. If anyone has some insight on this, let me know.
> > > We're running 2.0.0 on an Ultra 2 in Solaris 7.
> > >
> > > Thanks,
> > >
> > > Chad
> > >
> > > --
> > > Chad Campbell
> > > Software Engineer, Innovision Corporation
> > > Chad.Campbell at innovision.com
> > > (913)226-8700
> > >
> >
> > > [1999/03/11 08:19:00, 0] locking/shmem_sysv.c:shm_alloc(214)
> > > ERROR shm_alloc : alloc of 132 bytes failed
> >
> > _-_|\ Terry Dwyer E-Mail Work: tdwyer at io.telstra.com.au
> > / \ System Administrator Private: tdwyer at omen.com.au
> > *_.^\_/ Telstra Corporation Phone: +61 8 9491 5161
> > v Perth, Western Australia Fax: +61 8 9221 2631
> > (I do not speak for Telstra)
> >
> > ------------------------------
> >
> > Date: Thu, 11 Mar 1999 21:37:23 -0800
> > From: Cynthia Deno <cynthia at usenix.org>
> > To: samba at samba.anu.edu.au
> > Subject: USENIX/SAGE Conferences of Interest to System/Network Admins
> > Message-ID: <v04011731b30e5890c542@[208.201.152.17]>
> >
> > Co-sponsored by SAGE, the System Administrators Guild
> >
> > Conference on Network Administration
> > Wednesday and Thursday, April 7-8, 1999
> > Networking Tutorial Program
> > Friday and Saturday, April 9-10, 1999
> > Workshop on Intrusion Detection and Network Monitoring
> > Sunday and Monday, April 11-12, 1999
> >
> > Santa Clara Marriott Hotel in Santa Clara, California, USA.
> >
> > Interact with fellow network admins, share in expertise learned at sites of
> > all configurations, and gain mastery of the latest technologies and
> > solutions in network management.
> > =========================================
> > Programs and Call for Papers are always available at
> > http://www.usenix.org/events/sysadmin/
> > or telephone +1 949 588 8649.
> > =========================================
> > Call for papers available:
> >
> > LISA-NT--2nd Large Installation System Administration of Windows NT Conference
> > July 14-16, 1999, Seattle, Washington
> > Co-located with: 3rd USENIX Windows NT Symposium, July 12-14, 1999
> > Submission proposals due: February 23, 1999
> >
> > LISA '99--13th Systems Administration Conference
> > November 7-12, 1999, Seattle, Washington
> > Extended abstracts and Invited Talk Proposals due: May 25, 1999
> > Be a bigger part of LISA and play a role in shaping the program:
> > ===========================================================
> > The USENIX Association's international membership includes engineers,
> > scientists, and technicians working on the cutting edge of systems and
> > software. SAGE is the premiere membership society devoted to the
> > advancement and recognition of system administration as a profession.
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 17:23:47 +0900
> > From: Jim Tittsler <jwt at dskk.co.jp>
> > To: samba at samba.org
> > Subject: smbclient 2.0.(2|3) with WfWg Looping in FIND_NEXT?
> > Message-ID: <19990312172347.A29072 at mail.dskk.co.jp>
> >
> > I recently installed Samba 2.0.2 (and then 2.0.3) on a Linux 2.2 machine.
> > After using smbclient to connect to a Windows for Workgroups share, giving
> > the 'dir' command results in a delay followed by:
> > Error: Looping in FIND_NEXT??
> >
> > smbclient seems to have no problems with the Win95/98 shares I've
> > tried. An older smbclient (1.9.18p10) has no problem with the WfWg
> > shares.
> >
> > Have I missed some configuration requirement to allow use of my old
> > WfWg shares?
> >
> > Thanks!
> >
> > --
> > Jim Tittsler, Tokyo ICQ: 5981586
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 09:51:48 +0100
> > From: "=?iso-8859-1?Q?David_Scarlatti_Jim=E9nez?=" <scarla at BDE-sa.es>
> > To: <Peter.Lingen at wrh.acab.alcatel.de>
> > Cc: <samba at samba.org>
> > Subject: RE : Problems installing ORACLE products for Win95 on a Samba Network Drive.
> > Message-ID: <000f01be6c65$90515aa0$830100c0 at voyageur.bde-sa.es>
> >
> > This is a multi-part message in MIME format.
> >
> > ------=_NextPart_000_0010_01BE6C6D.F215C2A0
> > Content-Type: text/plain;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: 8bit
> >
> > Thanks for advise. We have both mount point and mounted filesystem 777 mode.
> > About directory mode, I think 700 should be enough, anyway, i've tried with
> > create force 755, and it still doesn't work.
> > Any other idea?
> > David Scarlatti Jiménez
> >
> > Base Documental de la Empresa S.A.
> >
> > Tel: +34915334753 Fax: +34915338853
> >
> > e-mail: scarla at bde-sa.es
> >
> > ------=_NextPart_000_0010_01BE6C6D.F215C2A0
> > Content-Type: text/html;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> > <HTML>
> > <HEAD>
> >
> > <META content=3D"text/html; charset=3Diso-8859-1" =
> > http-equiv=3DContent-Type>
> > <META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
> > </HEAD>
> > <BODY bgColor=3D#ffffff>
> > <DIV><SPAN class=3D350044808-12031999><FONT color=3D#000000 face=3DArial =
> > size=3D2>Thanks=20
> > for advise. We have both mount point and mounted filesystem 777 mode. =
> > About=20
> > directory mode, I think 700 should be enough, anyway, i've tried with =
> > create=20
> > force 755, and it still doesn't work.</FONT></SPAN></DIV>
> > <DIV><SPAN class=3D350044808-12031999><FONT color=3D#000000 face=3DArial =
> >
> > size=3D2></FONT></SPAN><SPAN class=3D350044808-12031999><FONT =
> > color=3D#000000=20
> > face=3DArial size=3D2>Any other idea?</FONT></SPAN></DIV>
> > <DIV><FONT size=3D2>
> > <P>David Scarlatti Jiménez</P>
> > <P><FONT face=3DArial>Base Documental de la Empresa S.A.</FONT></P>
> > <P><FONT face=3DArial>Tel:=20
> > +34915334753 =
> > Fax:=20
> > +34915338853</FONT></P>
> > <P><FONT face=3DArial>e-mail: <A=20
> > href=3D"mailto:scarla at bde-sa.es">scarla at bde-sa.es</A></FONT></P></FONT></=
> > DIV>
> > <DIV> </DIV></BODY></HTML>
> >
> > ------=_NextPart_000_0010_01BE6C6D.F215C2A0--
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 08:17:48 -0600
> > From: Patrick Harrold <patrickh at nasco-inc.com>
> > To: samba at samba.org
> > Subject: Remote browsing
> > Message-ID: <3.0.3.32.19990312081748.0069df1c at mail.nasco.asn>
> >
> > I have the newest Samba running on a RH5.2 box. Our network is 10bT, and
> > we run frame relay to 18 remote sights. All the ip addresses are in the
> > 172.16.x.x range, with a sm of 255.255.255.0. All of the clients that are
> > in the same physical location as the server can connect. However, all of
> > the remote clients can "see" the samba box in Network Neighborhood, but
> > when they attempt to browse it, they get an error message stating that the
> > computer name or share could not be found. Any ideas?
> >
> > TIA
> >
> > Patrick Harrold
> > Manager of Information Services
> > Nasco, Inc.
> > 651.780.2000
> > FAX 651.638.1803
> > patrickh at nasco-inc.com
> >
> > ------------------------------
> >
> > Date: Fri, 12 Mar 1999 16:06:17 +0000
> > From: Paul Jakma <paul.jakma at compaq.com>
> > To: samba at samba.anu.edu.au
> > Subject: share mode locking: behaviour inconsistency.
> > Message-ID: <36E93B79.639D3EE5 at compaq.com>
> >
> > Hi,
> >
> > I think there is an inconsistency between the way samba handles share
> > mode locking, and the way NT does.
> >
> > We're running samba 2.0.3 on linux 2.0.36. Which is used to share a
> > couple of files to a small windows application running on several
> > computers, which uses share mode locking to synchronise writes.
> >
> > we've noticed the following problem:
> >
> > [root at nldbd austria]# smbstatus
> >
> > Samba version 2.0.3
> > Service uid gid pid machine
> > ----------------------------------------------
> > easy user1 smbusers 27352 machine1 (ip_addr1) Fri Mar 12
> > 15:48
> > :23 1999
> >
> > Locked files:
> > Pid DenyMode R/W Oplock Name
> > --------------------------------------------------
> > 27352 DENY_WRITE RDWR EXCLUSIVE+BATCH /home/samba/share/loinf
> > Fri Mar 12 15:52:29 1999
> >
> > Share mode memory usage (bytes):
> > 12582384(99%) free + 408(0%) used + 120(0%) overhead = 12582912(100%)
> > total
> >
> > If another application tries to open file "loinf" read/write, it fails,
> > as it should.
> >
> > however if another application tries to open file "loinf" read only, it
> > fails! with error string "access denied". Under NT it is possible for a
> > second application to open the file read_only while the file is locked
> > DENY_WRITE.
> >
> > This is causing me problems as I need to serve files to an application
> > that depends on NT's share mode behaviour. I've tried disabling oplocks
> > and {dis,en}enabling {kernel,blocking,strict?} locks. it doesn't help.
> >
> > any ideas? bug in samba's behaviour or NT's behaviour? And are there any
> > work arounds?
> >
> > Regards,
> >
> > Paul Jakma.
> >
> > PS: please cc: me as I'm not on the list. (yet).
> >
> > PPS: samba's new domain member code works excellently, am using it to
> > transparently create home directories for NT users.. great work.
> >
> > ------------------------------
> >
> > End of SAMBA Digest 2017
> > ************************
>
> ------------------------------
>
> End of SAMBA Digest 2018
> ************************
More information about the samba
mailing list