Unsubsribe
Mike Garver
sales at deerfield.com
Tue May 11 16:04:17 GMT 1999
Best Regards,
Mike Garver
_________________________
Marketing Associate
Deerfield.com
http://www.deerfield.com/
sales at deerfield.com
----------------------------------------------------------------------
Please download and try our other exciting software products:
----------------------------------------------------------------------
WinGate - http://www.wingate.com/
FTP Voyager - http://www.ftpvoyager.com/
InterQuick - http://www.interquick.com
FTP Serv-U - http://www.ftpserv-u.com/
MDaemon - http://www.mdaemon.com/
WebPOP for MDaemon - http://www.mdaemon.com/webpop
RelayFax - http://www.relayfax.com/
On Tue May 11 12:02:45 EDT 1999 you wrote:
> SAMBA Digest 2086
>
>For information on unsubscribing see http://samba.org/listproc/
>Topics covered in this issue include:
>
> 1) Re: Performance (?) problem with Samba and NT
> by David Collier-Brown <davecb at canada.sun.com>
> 2) RE: netbios server failing
> by Timothy Demarest <demarest at arraycomm.com>
> 3) Samba 2 on Solaris 7 MAJOR performance problems.
> by "Hight, Steve - SBS" <shight at chw.edu>
> 4) Problem mapping drive names on Win95
> by "Dr Hugh Nelson" <hugh.nelson at ausinfo.com.au>
> 5) Re: Performance (?) problem with Samba and NT
> by "Brian Ginter" <brg at southern-air.com>
> 6) Samba Performance - Slow writes to 95 - Slow "puts" - etc.
> by Steve Arntzen <sjarntzen at esi-il.com>
> 7) Re: Performance (?) problem with Samba and NT
> by "Stephen L Arnold" <arnold.steve at ensco.com>
> 8) Re: Collision Lights go Crazy
> by Cris Wade <quade at therim.net>
> 9) SAMBA printing Win98 -> Redhat printer server
> by "Duy_An Nguyen-Khanh" <citgo_sg at hotmail.com>
> 10) Re: Advice on Samba for large site
> by Peter Polkinghorne <Peter.Polkinghorne at brunel.ac.uk>
> 11) Re: questions about HD size; and daemon.
> by Michal <heja at xox.pl>
> 12) Re: Advice needed for samba for school use (SAMBA digest 2083)
> by "Ludek Babor" <Babor at Glavunion.cz>
> 13) Security related bug/issue ... or mis-configuration?
> by The Hermit Hacker <scrappy at hub.org>
> 14) Samba's movin' SLOW! (fwd)
> by "Kevin A. Pieckiel" <kapieckiel at harding.edu>
>
>---------------------------------------------------------------------
>-
>
>Date: Mon, 10 May 1999 16:01:19 -0400
>From: David Collier-Brown <davecb at canada.sun.com>
>To: "Hall, Ken (ECCS)" <KeHall at exchange.ml.com>
>Subject: Re: Performance (?) problem with Samba and NT
>Message-ID: <37373B0F.F19188C3 at canada.sun.com>
>
>Ken Hall wrote:
>| On the NT machine, however, it takes up to a minute to open the
>Samba
>Server
>| in Network Neighborhood. It takes up to another minute to open any
>of
>the
>| shares.
>
> This sounds a lot like the NT machine has several protocols
> configured: if you have TCP/IP, Novell and NetBlooie turned
> on, bit only one is responding, you get several 30-second timeouts
> as the client machine tries NetBEUI, Novell and then IP for
> some of its operations.
>
>--dave
>--
>David Collier-Brown, | Always do right. This will gratify some
>people
>185 Ellerslie Ave., | and astonish the rest. -- Mark Twain
>Willowdale, Ontario | http://java.science.yorku.ca/~davecb
>Work: (905) 477-0437 Home: (416) 223-8968 Email:
>davecb at canada.sun.com
>
>------------------------------
>
>Date: Mon, 10 May 1999 13:23:00 -0700
>From: Timothy Demarest <demarest at arraycomm.com>
>To: samba at samba.org
>Subject: RE: netbios server failing
>Message-ID: <199905102023.NAA20653 at mabel>
>
>
>>Hi,
>
>>I got such message:
>
>>hostname inetd[111]: netbios-ns/udp server failing (looping),
>service
>>terminated
>
>>What does it mean ? How can I correct it ?
>
>This can happen if inetd is trying to handle too many requests for
>that
>particular service in a specific time interval. Under Solaris 2.5.1
>inetd
>considers any service that invokes itself more than 40 times in 60
>seconds
>as "broken". From the man page:
>
> -r Allows inetd to detect and then suspend ``broken''
> servers. The -r flag has the form:
>
> -r count interval
>
> count and interval are decimal numbers that
> represent the maximum count of invocations per
> interval of seconds a service may be started
> before the service is considered ``broken''.
>
> Once considered ``broken'', a server is suspended
> for ten minutes. After ten minutes, inetd again
> enables service, hoping the server behaves
> correctly.
>
> If the -r flag is not specified, inetd behaves as
> though -r40 60 was specified.
>
>To override this behavior you need to start inetd with
>the -r option (Solaris) like this:
>
> /usr/sbin/inetd -s -r 300 60
>
>This will allow up to 300 invocations in 60 seconds. To permanently
>make
>the change edit /etc/init.d/inetsvc.
>
>We had to do this in our environment because when the Samba servers
>are
>rebooted they receive about 200 requests for remounts from all of the
>active PCs.
>
>Good luck.
>
>Tim
>
>--
>Timothy Demarest ArrayComm, Inc.
>demarest at arraycomm.com 3141 Zanker Road
>http://www.arraycomm.com San Jose, CA 95134
>
>
>
>------------------------------
>
>Date: Mon, 10 May 1999 13:26:13 -0700
>From: "Hight, Steve - SBS" <shight at chw.edu>
>To: "'SAMBA at SAMBA.org'" <SAMBA at SAMBA.org>
>Subject: Samba 2 on Solaris 7 MAJOR performance problems.
>Message-ID:
><82B241B34652D21184F900A0C9C74A8B017CEA79 at SBS-MSG-01.sbs.chw.edu>
>
>I have a Solaris 7 server with a fresh install of Samba 2.0. The
>server is
>a Dell 2300 Pentium 3 500MHZ Zeon. I have the fastest RAID
>controller Dell
>makes. Intel Pro 100 card, hard set to 100 meg full duplex.
>
>Solaris performance is fantastic. FTP is really fast. Samba
>connectivity
>is unusable. I read everything I could find and this is the best
>setup I
>could find so far:
>
>I really appreciate any help!
>
>Steve Hight
>
>
># Samba config file created using SWAT
># from 10.4.11.50 (10.4.11.50)
># Date: 1999/05/10 15:13:33
># Global parameters
> workgroup = CHWSBS
> netbios name = SBSDPL01
> server string = Wininstall Samba Server
> interfaces = iprb0
> security = DOMAIN
> encrypt passwords = Yes
> password server = sbs-pdc-01 sbs-bdc-02
> log file = /var/log/samba/log.%m
> max log size = 50
> deadtime = 10
> socket options = TCP_NODELAY
> dns proxy = No
> wins server = 10.4.3.60
> guest account = www
>
>[homes]
> comment = Home Directories
> read only = No
> browseable = No
>
>[printers]
> comment = All Printers
> path = /var/spool/samba
> print ok = Yes
> browseable = No
>
>[wininstall]
> path = /wininstall
> guest ok = Yes
>
>[apps]
> comment = Application Source Binaries
> path = /apps
> read only = No
> guest ok = Yes
>
>[webpub]
> path = /usr/local/apache/share/htdocs
> read only = No
> guest ok = Yes
> browseable = No
>
>
>------------------------------
>
>Date: Tue, 11 May 1999 06:59:22 +1000
>From: "Dr Hugh Nelson" <hugh.nelson at ausinfo.com.au>
>To: samba at samba.org
>Subject: Problem mapping drive names on Win95
>Message-ID: <19990510210540Z12858193-4231+1955 at samba.anu.edu.au>
>
>> Date: Sun, 9 May 1999 16:50:55 -0400
>> From: Wolfgang Albrecht <Wolfgang_Albrecht at compuserve.com>
>> To: Samba <Samba at Samba.org>
>> Subject: Problem mapping drive names on Win95
>>
>> in my Office, I'm trying to replace a Novell-server by a
>Linux-server. On
>> the Novell-server, there is the SYS: volume. On this volume is a
>directory
>> named DriveT. I did a map on it, so this SYS:DriveT was used as T:
>. If
>> you link Excel sheets, which are stored on T:, to Word documents,
>Word
>> unfortunately saves the UNC path, which is \\SERVER1\SYS\DRIVET
>instead of
>> T:
>>
>> On my new Samba server, I`m trying to keep the same paths, because
>> there are many hundred Word documents with thousands of links to
>Excel
>> sheets. So I named the Linux server SERVER1, I created directory
>/SYS and
>> a directory DriveT in SYS. In this way, the UNC path is still the
>same.
>
>This is the mistake. Create a directory and call it /DILBERT
>
>in your smb.conf have the section
>
>[SYS]
>comment = shared folder on Server1
>path = /DILBERT
>browseable = yes
>writable = yes
>public = yes
>
>Then from Windoze Network Neighborhood you will see
>\\SERVER1\SYS
>
>Then from Network Neighborhood, you can right click on this folder
>and Map Network Drive to T:
>
>cheers,
>
>
>----------------------------------------------------
>Dr Hugh Nelson <hugh.nelson at ausinfo.com.au>
>3 Sir John Overall Dr, Helensvale, QLD 4210, Australia Ph:+61 7 5573
>2122
>
>
>------------------------------
>
>Date: Mon, 10 May 1999 17:20:04 -0400
>From: "Brian Ginter" <brg at southern-air.com>
>To: samba at samba.org
>Subject: Re: Performance (?) problem with Samba and NT
>Message-ID: <199905101719.RAA16890 at eeyore.southern-air.com>
>
>> Date: Mon, 10 May 1999 09:24:38 -0400
>> From: "Hall, Ken (ECCS)" <KeHall at exchange.ml.com>
>> To: Multiple recipients of list <samba at samba.org>
>> Subject: Performance (?) problem with Samba and NT
>> Message-ID:
><59523CAF2AA3D111A8AB00805FE67F2E6F3BBA at ewst03.exchange.ml.com>
>>
>> I've seen this question asked on the list, but never answered.
>I've tried
>> searching the archives, etc., but don't find anything relevant.
>>
>> I have a network with several Win95 and 98 client machines and one
>NT4
>> machine (NT Workstation, not Server). It's currently using Novell,
>but I've
>> been testing a Samba server as a replacement. The 95 and 98
>clients work
>> fine. When I browse the network, the server appears, I can open
>it, look at
>> the shares, etc. Everything is quick and correct. Even printing
>works
>> fine.
>>
>> On the NT machine, however, it takes up to a minute to open the
>Samba Server
>> in Network Neighborhood. It takes up to another minute to open any
>of the
>> shares. If I run "NET USE" from a command-line window, it takes
>the same
>> amount of time to complete. Once the share is mapped to a drive,
>it works
>> fine for a while, but after a time, you can't open "My Computer"
>without
>> another long wait, and can't access the mapped drives without
>another long
>> wait.
>>
>> This is Samba 2.0.3 on RedHat 5.2, but I'm having a similar problem
>on a
>> test box running 5.1 and an older version of Samba. The NT system
>was at
>> SP3, and is now at SP4. The upgrade had no effect on the
>operation.
>> Defining a WINS server on the NT system had no effect, other than
>to make
>> the "Workstation" service fail to start most of the time. I'm
>using
>> SECURITY=USER, and everything else seems to be working fine.
>>
>> I had tested this setup with NT Server a while back, and I vaguely
>recall
>> having similar problems with it, but I gave up on it for other
>reasons
>> before I had a chance to figure out what was wrong. Because of
>this, I
>> suspect the problem is on the client side.
>>
>> Anyone have any ideas?
>
>Do you have Novell Client 32 installed on the NT machine? I have
>this problem on my NT machine which does use Client 32. Several
>other NT boxes with MS client work just fine.
>Coincidence??
>BRG
>
>------------------------------
>
>Date: Mon, 10 May 1999 16:23:10 -0500
>From: Steve Arntzen <sjarntzen at esi-il.com>
>To: "'samba at samba.org'" <samba at samba.org>
>Subject: Samba Performance - Slow writes to 95 - Slow "puts" - etc.
>Message-ID: <01BE9B01.658944C0 at sjarntzen.esi-il.com>
>
>This is in response to a large number of you having
>similar problems with Samba performance as I.
>
>I have tracked these symptoms back to Digest 1709!
>(I didn't go back any further)
>
>I have created a few entries in the digest myself.
>Only one person ever responded to me (Thanks Jan K.),
>but that suggestion didn't help.
>
>After many late hours of tweaking last Friday night,
>with little benefit, and re-reading the digests I
>finally succeeded. I thought I would share this with
>all of you.
>
>My Samba problem was with slow writes to the network
>(slow "puts" as some of you may call it, or slow reads
>from the server). I have learned many things about
>Samba performance. Some of these affected 95 clients
>but not NT clients. These problems existed using a
>533 Mhz. Alpha server and 450 Mhz. Intel clients
>running directly through a fast switch. On an idle
>network (i.e.. late Friday night) you wouldn't expect
>performance problems. Maybe some of these problems
>aren't noticed on standard ethernet.
>
>First make sure you get good network performance using
>other tools (ftp, NFS, etc.). I found that my SMC
>switch and some of my fast ethernet cards were set to
>auto-negotiate and were actually negotiating the type
>of link on the fly (thanks to the folks at SMC).
>
>Read your log files! One of the first things I learned
>is the permissions on your lock dir tree must be set
>properly. I have seen a lot of performance complaints
>with certain applications that are most likely file
>locking problems.
>
>Check your config with testparm to see what's going on.
>
>READ RAW and READ BMPX on my systems were set to true
>by default (which is good). Setting either one to
>false would add almost 10 minutes to the read time of
>a 10 MB file with a 95 client. Setting both would
>double that time!
>
>I have played with READ SIZE, READ PREDICTION, MAX XMIT,
>TCP_NODELAY and READ PREDICTION with minor performance
>changes. I even tried IPTOS_LOWDELAY and variations
>of SO_SNDBUF and SO_RCVBUF.
>
>The final and best advice was from Juan Carlos Castro
>in a recent mailing (digest 2069) not so obviously
>named "Open Letter to the Samba Team". In this mailing
>Juan suggested :
>socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
>
>That did it! As many values as I tried (in powers of 2),
>I didn't try 8K. Thank you Juan!
>
>Although setting the debug value to zero didn't help (mine
>defaulted to 2), I think if your done diagnosing, it's a
>good idea.
>
>Misc. notes:
>
>One thing I have noticed on a 200 Mhz. pentium NT
>client with Samba or ftp was that NT would start
>writing to disk while the file is still being transferred
>over the network noticeably slowing down the network task.
>Linux, FreeBSD etc. clients would cache the entire file,
>then write to disk, thus achieving full network bandwidth.
>Although I could get full network bandwidth with NT, It
>was on files less than 2MB.
>
>I have disabled ALL WINS at our site and run strictly
>DNS (on Linux of course).
>
>As I stated in digest 2042, "This is the final snag in
>replacing our last NT server with a Samba machine".
>Bye-bye NT!
>
>Thank you to all of the Samba team for a great product
>for the "open" software industry.
>
>Thank you to all who use (and respond) to this list.
>
>I hope my this helps some of you to overcome what I
>fought with for months.
>
>I am not trying to be an authority on Samba, but have
>found what works for me. If any of the Samba team see
>errors in what I have done, or good reasons not to do
>something I have done, please correct me.
>
>Sorry for the large mailing.
>
>Although I always hate reading through them on the
>mailing list, I thought somebody might benefit...
>
>My abbreviated smb.conf (some things obviously changed):
>;======================= Global Settings
>=====================================
>[global]
>
> debug level = 0
>
> config file = /etc/smb.conf
> workgroup = mydomain.com
> comment = Samba Server
>
> hosts allow = 192.168.0. 127.0.0.1
>
> security = user
> smb passwd file = /etc/smbpasswd
> password level = 1
> encrypt passwords = yes
>
> printing = bsd
> printcap name = /etc/printcap
> load printers = yes
>
> log file = /var/log/samba/%m
> max log size = 50
>
> short preserve case = yes
> preserve case = yes
>
> lock directory = /var/lock/samba
> locking = yes
> share modes = yes
>
> read prediction = yes
> socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
>
> os level = 32
> domain master = yes
>
> name resolve order = host bcast
>
> dead time = 15
>
>;============================ Share Declarations
>==============================
>[database]
> comment = Access Database
> path = /mnt/drive2/database
> public = no
> read only = no
> create mask = 0777
>
>[public]
> comment = Public Data
> path = /mnt/drive2/public
> public = yes
> read only = no
> users = @users
> force group = users
> write list = @users
> map archive = yes
> map hidden = yes
> map system = yes
> create mask = 0777
> directory mask = 777
> force create mode = 444
> force directory mode = 444
>
>[graphics]
> comment = graphics drive
> path = /mnt/drive2/graphics
> public = no
> writeable = yes
> users = @users
> force group = users
> write list = @users
> map archive = yes
> map hidden = yes
> map system = yes
> create mask = 0777
> directory mask = 777
> force create mode = 444
> force directory mode = 444
> valid users = user1, user2, user3, user4
>
>[HP3D]
> comment = Tech area HP IIID
> printer name = HP3D
> printable = yes
> browseable = yes
> writeable = no
> postscript = no
>
>[FieryXJ]
> comment = Color Xerox on EFI Fiery
> printer name = FieryXJ
> printable = yes
> browseable = yes
> writeable = no
> postscript = yes
>
>
>------------------------------
>
>Date: Mon, 10 May 1999 13:33:26 -0700
>From: "Stephen L Arnold" <arnold.steve at ensco.com>
>To: samba at samba.org
>Subject: Re: Performance (?) problem with Samba and NT
>Message-ID: <199905102233.SAA13942 at devonshire.cnchost.com>
>
>When the world was young, "Hall, Ken (ECCS)"
><KeHall at exchange.ml.com> carved some runes like this:
>
>> I have a network with several Win95 and 98 client machines and one
>NT4
>> machine (NT Workstation, not Server). It's currently using Novell,
>but
>> I've been testing a Samba server as a replacement. The 95 and 98
>clients
>> work fine. When I browse the network, the server appears, I can
>open it,
>> look at the shares, etc. Everything is quick and correct. Even
>printing
>> works fine.
>>
>> On the NT machine, however, it takes up to a minute to open the
>Samba
>> Server in Network Neighborhood. It takes up to another minute to
>open any
>> of the shares. If I run "NET USE" from a command-line window, it
>takes
>> the same amount of time to complete. Once the share is mapped to a
>drive,
>> it works fine for a while, but after a time, you can't open "My
>Computer"
>> without another long wait, and can't access the mapped drives
>without
>> another long wait.
>>
>> This is Samba 2.0.3 on RedHat 5.2, but I'm having a similar problem
>on a
>> test box running 5.1 and an older version of Samba. The NT system
>was at
>> SP3, and is now at SP4. The upgrade had no effect on the
>operation.
>> Defining a WINS server on the NT system had no effect, other than
>to make
>> the "Workstation" service fail to start most of the time. I'm
>using
>> SECURITY=USER, and everything else seems to be working fine.
>
>You could try having the NT box use an lmhosts file instead of
>WINS; I use the #PRE option for the samba server. It might also be
>related to the specific services running under NT (they won't let
>me near an NT admin account, 'cause I'm a linux dude :)
>
>We have a similar setup here (mostly win95, 1 win98, 1 NT4SP3
>workstation, 1 linux/samba box) but NT seems to access the samba
>shares just as fast as the win95 clients (even faster on the linux
>/usr/doc tree, but the NT box is our fastest machine - PII-450).
>We don't use WINS, we have no PDC, and only a simple LAN with no
>subnets. I have samba running as the master browser, with most of
>the win clients disabled (as far as browse master competition).
>All machines use lmhosts for NetBIOS names, and hosts for internal
>DNS names. The samba box is a lowly 486 with 32 megs RAM, but
>performance is fine (it also runs apache, MySQL, VNC sessions, etc).
>
>Even with all the system updates, win95 still can't Net View the NT
>box (but it works with samba):
>
>C:\WINDOWS>net view \\rama
>Shared resources at \\RAMA
>
>Sharename Type Comment
>--------------------------------------------------
>arnold Disk Your Home Directory
>docs Disk Linux docs
>public Disk HTML Document Tree
>smb Print lp
>smbps Print lp0
>source Disk Source Code
>tmp Disk Temporary file space
>The command was completed successfully.
>
>C:\WINDOWS>net view \\mothra
>
>Error 234: Additional data is available.
>
>Obviously, the M$ networking stuff is hosed from one platform or
>service pack to another (or, How do you say in your country... It's
>completely FUBAR'd).
>
>If you really want to alleviate these headaches, I think the only
>option is to bail NT and get linux on those clients. The
>development tools are much better, and there are numerous open
>source packages (depending on your requirements) that can fill most
>needs.
>
>Never miss a chance to evangelize...
>
>Steve
>
>
>******************************************************************
>Stephen L Arnold http://www.rain.org/~sarnold
>#include <std_disclaimer.h>
>******************************************************************
>
>------------------------------
>
>Date: Mon, 10 May 1999 22:49:35 -0500 (CDT)
>From: Cris Wade <quade at therim.net>
>To: E Irvine <eirvine at tpgi.com.au>
>Subject: Re: Collision Lights go Crazy
>Message-ID: <Pine.LNX.4.05.9905102241220.7059-100000 at therim.net>
>
>
>
>On Tue, 11 May 1999, E Irvine wrote:
>
>> OK. Is one of your network cards set to "Full Duplex"?
>> Full duplex is only for where a nic is plugged
>> directly into a switch.
>>
>
>all the NICs are set to half duplex 10Mbit
>
>ok, here are the type of network cards..
>
>Server Intel EtherExpress Pro 10/100 +
>Cliant 3Com 905b
>
>> Also, try the FTP speed. Is that slow as well?
>
>FTP speed is good, as I said, if I am at the server and initiate the
>data
>transfer from the server, it is fast.
>
>I think I have tracked down the problem though. even though it may
>not
>look like it, I think that the 3com NIC is bad. I put a 10 baseT
>only
>Realtek card in a cliant, and it works fine.. Is there any known
>problems
>with 3COM 905b's running at 10 Mbits and SAMBA. anyway, I think I
>will
>buy Intel NICs from now on.. I have had good luck with them in the
>past.
>Dont know what got into me to get the 3Com stuff, but anyway.
>
>Thanks for the help
>
>Jon C Wade
>
>Quade
>
>
>------------------------------
>
>Date: Tue, 11 May 1999 00:05:07 PDT
>From: "Duy_An Nguyen-Khanh" <citgo_sg at hotmail.com>
>To: samba at samba.org
>Subject: SAMBA printing Win98 -> Redhat printer server
>Message-ID: <19990511070509.92301.qmail at hotmail.com>
>
>I'm having problem with printing from win98 to my printer which is
>connected
>to my Red Hat machine. I can see lp from Network Neighbourhood and
>printer
>is set up as \\REDHATMACHINE\lp
>however nothing would come out of the printer. Windows doesn't give
>any error message.
>My Red Hat machine prints fine however. I've included a portion of
>my smb.conf below.
>
>
>[global]
> printcap name = /etc/printcap
> load printers = yes
> security = user
>
>
>[printers]
> comment = HP Deskjet 500
> path = /var/spool/lpd
> valid users = myusername
> print ok = yes
> printable = yes
> browseable = no
> public = no
> guest ok = no
> writable = no
>
>My shared directories have very similar configurations and I can use
>them in Windows just fine. Any help would be much appreciated.
>
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
>------------------------------
>
>Date: Tue, 11 May 1999 09:54:52 +0200
>From: Peter Polkinghorne <Peter.Polkinghorne at brunel.ac.uk>
>To: Mike Richardson <doctor at kira.mcc.ac.uk>
>Subject: Re: Advice on Samba for large site
>Message-ID: <94.199905110854 at moomin.brunel.ac.uk>
>
>
>Mike Richardson said:
>> I've been asked to research the possibility of changing our site
>from
>> Novell to Samba. We've got 10,000+ client machines with about
>30,000
>> users and currently use about 200-300 novell servers. I'm
>reasonably
>> familiar with Samba but not on this scale. If anyone can point me
>> towards a similar site then I'd be grateful.
>
>Well we are not so big - around half the size and currently only have
>around
>500 active client machines (out of a possible 4,000) - but this is
>growing
>plus we are a UK academic site.
>
>> Currently we have a accouting system for each user for printing
>> services, access to home directories and installed software (some
>> licenced), mail delivered to the Novell server using mercury and
>read
>> using pegasus (normally).
>
>We use a separate UNIX MTA for mail (PP) and have IMAP & POP servers
>for
>access from PC. For printing accounting is an area were we are
>looking at the
>Aegis PALMS system - commercial.
>
>However we do use Samba for file and print services.
>
>> Questions I need answered are general ones such as:
>
>> What problems were encountered initially, and subsequently? How
>much
>> can samba do out the box and how much custom software is needed?
>How
>> can we retain the print accounting services? How good is samba with
>
>> licenced software? Will it scale to this number of machines/users?
>> What spec of hardware will we need for the servers? How well does
>> samba handle user filestore quotas?
>
>We found that Samba worked pretty much out of the box - although we
>have
>already got a set of UNIX (Sun) file servers using NFS and AMD -
>which also
>provides user quotas. Licensing is handled separately from Samba.
>I have posted appplication server loading figures - in Summary we
>think that
>1 Sun Ultra 5 can serve applications to around 60 classroom and 400
>office
>machines.
>
>Do contact me if you want more details ...
>
>--
>---------------------------------------------------------------------
>--------
>| Peter Polkinghorne, Computer Centre, Brunel University, Uxbridge,
>UB8 3PH,|
>| Peter.Polkinghorne at brunel.ac.uk +44 1895 274000 x2561 UK
>|
>---------------------------------------------------------------------
>--------
>
>
>
>------------------------------
>
>Date: Tue, 11 May 1999 13:51:08 +0000
>From: Michal <heja at xox.pl>
>To: Multiple recipients of list <samba at samba.org>
>Subject: Re: questions about HD size; and daemon.
>Message-ID: <373835CC.32C2A56D at xox.pl>
>
>Laurent Bardi wrote:
>>
>> -why the smbd daemon does not run as <user> and run as root
>(perhaps it is
>> unsecure to ask for that?) but it will be more easy for admin to
>see who is
>> connected (ps) ?
>>
>
>Well, because it accesses other shares apart from \homes, and it
>changes
>effective UID depending on this and settings in smb.conf. It is quite
>easy to admin, though, because we have smbstatus command :-)
>
>As for the rest of questions, maybe some more experienced guru will
>anwer ? ;-)
>
>Michal
>
>------------------------------
>
>Date: Tue, 11 May 1999 14:52:22 +0200
>From: "Ludek Babor" <Babor at Glavunion.cz>
>To: Michael Anderson <mka at gto1.telmex.net.mx>, samba at samba.org
>Subject: Re: Advice needed for samba for school use (SAMBA digest
>2083)
>Message-ID: <28751EAF4505 at Glavunion.cz>
>
>> Date: Fri, 07 May 1999 18:36:52 +0000
>> From: Michael Anderson <mka at gto1.telmex.net.mx>
>> To: samba at samba.org
>> Subject: Advice needed for samba for school use
>> Message-ID: <37333257.7850176F at gto1.telmex.net.mx>
>>
>> Hi:
>>
>> I'm setting-up samba 2.0.0 on linux 2.2.1 as a file/print server
>> for a group of 24 Win98 machines in a mixed-age (K-12) school
>> lab in Mexico. There are approx. 200 students and every hour the
>users
>> change. The users do not often use the same machine they last used.
>>
>> I need to automate the process as much as possible; I'm sure
>> this is being done elswhere and I hate to reinvent the wheel.
>> What I need to happen is this:
>>
>> 1. All login info. and user profiles stored on the samba server
>> and only on the samba server. If local copies are made, over time
>> every machine will have password and profile information (likely
>> out-of-date) for every student. I have the profiles being stored
>> correctly on the samba server, how can I eliminate the copies
>> on the client machines?
>
>It's possible only via network policy on WindowsNT.
>
>> 2. Each user should connect automatically to his home directory
>> upon login at the Win98 machine, and disconnect automatically
>> upon logout. The user's home directory should become the current
>> working directory for the user, so that, by default, all user
>> files are kept there. I've tried putting "net use z: /HOME" in
>> the %U.bat for each user, but it fails because "netlogon" is
>> always mounted on z:.
>
>You can try this:
>Net Use Y: \\Server\Homes
>
>in smb.conf:
>[homes]
> path = /usr/users/%S
> comment = Home directory of user %S
> guest ok = no
> read only = no
> browseable = no
> create mode = 0700
>
>> 3. Users should not be able to see (browse) the directories of
>> any other user.
>
>in smb.conf:
>[global]
> browseable = no
>and [homes] section as above
>
>> 4. The Win98 logon screen fields should always be blank (not
>> contain the name of the last user) for new logins.
>
>In PolEdit:
>Local Computer - Windows 98 Network - Logon - Dont show last user on
>logon
>
>> 5. Users should not be able to "share" their home directory
>> across the network.
>>
>> 6. Does a tool exist for batch entry of login/passwords? I'm
>> not using password encryption.
>
>If you want automatic logon to Windows, you can use TweakUI.
>
>Best regards
> Ludek Babor E-Mail: Babor at Glavunion.cz
> operation manager E-Mail: Ludek.Babor at cz.glaverbel.com
> Glaverbel Czech, a.s., Teplice Tel: +420-417-503085
>(+420-602-388003)
> Sklarska 450 Fax: +420-417-508085
> 416 74 Teplice FIDO: 2:423/74.13
>
> PGP key available from PGP key servers (http://www.pgp.net/pgpnet)
>
> I use MIME ISO-8859-2 friendly software.
>
>------------------------------
>
>Date: Tue, 11 May 1999 10:52:57 -0300 (ADT)
>From: The Hermit Hacker <scrappy at hub.org>
>To: samba at samba.org
>Subject: Security related bug/issue ... or mis-configuration?
>Message-ID: <Pine.BSF.4.05.9905111049340.47191-300000 at thelab.hub.org>
>
> This message is in MIME format. The first part should be readable
>text,
> while the remaining parts are likely unreadable without MIME-aware
>tools.
> Send mail to mime at docserver.cac.washington.edu for more info.
>
>--0-159320483-926430777=:47191
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
>Morning...
>
> Attached are two files. The first (smb.session) shows one user
>connecting to two different shares on a remote server using *no*
>password...
>
> The second is the smb.conf file found on that remote server,
>running Solaris 2.6, and Samba 2.0.3 ...
>
> I'm *really* hoping that its something that we're overlooking as
>far as configuration is concerned...or else there is one helluva
>large
>hole in Samba :(
>
> Authentication, as shown, is to thor.acadiau.ca, which is an NT
>server...
>
> Any help *much* appreciated...
>
>Thanks...
>
>Marc G. Fournier ICQ#7615664 IRC
>Nick: Scrappy
>Systems Administrator @ hub.org
>primary: scrappy at hub.org secondary:
>scrappy@{freebsd|postgresql}.org
>
>--0-159320483-926430777=:47191
>Content-Type: TEXT/PLAIN; charset=US-ASCII; name="smb.session"
>Content-Transfer-Encoding: BASE64
>Content-ID: <Pine.BSF.4.05.9905111052570.47191 at thelab.hub.org>
>Content-Description:
>Content-Disposition: attachment; filename="smb.session"
>
>c2FuZG1hbjp+JCBzbWJjbGllbnQgXFxcXHJlbGF5XFxkY3VycmllIC1VIGRj
>dXJyaWUNClVuYWJsZSB0byBvcGVuIGNvbmZpZ3VyYXRpb24gZmlsZSAiL29w
>dC9zYW1iYS9saWIvc21iLmNvbmYiIQ0KcG1fcHJvY2VzcyByZXR1bmVkIGZh
>bHNlDQpDYW4ndCBsb2FkIC9vcHQvc2FtYmEvbGliL3NtYi5jb25mIC0gcnVu
>IHRlc3RwYXJtIHRvIGRlYnVnIGl0DQpBZGRlZCBpbnRlcmZhY2UgaXA9MTMx
>LjE2Mi4xMjkuMTExIGJjYXN0PTEzMS4xNjIuMTM1LjI1NSBubWFzaz0yNTUu
>MjU1LjI0OC4wDQpTZXJ2ZXIgdGltZSBpcyBUdWUgTWF5IDExIDEwOjE3OjUz
>IDE5OTkNClRpbWV6b25lIGlzIFVUQy0zLjANClBhc3N3b3JkOiANCkRvbWFp
>bj1bQUNBRElBXSBPUz1bVW5peF0gU2VydmVyPVtTYW1iYSAyLjAuM10NCnNt
>YjogXD4gbHMNCiAgbG9jYWwubG9naW4gICAgICAgICAgICAgICAgICAgICAg
>ICAgICAgICAgICA1NzUgIEZyaSBKdWwgMTAgMTA6NDg6NDQgMTk5OA0KICBs
>b2NhbC5wcm9maWxlICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDU2
>MCAgRnJpIEp1bCAxMCAxMDo0ODo0NCAxOTk4DQogIC5wcm9maWxlICAgICAg
>ICAgICAgICAgICAgICAgICAgICAgIEggICAgICAgMTQ0ICBGcmkgSnVsIDEw
>IDEwOjQ4OjQ0IDE5OTgNCiAgbG9jYWwuY3NocmMgICAgICAgICAgICAgICAg
>ICAgICAgICAgICAgICAgICAxMjQgIEZyaSBKdWwgMTAgMTA6NDg6NDQgMTk5
>OA0KICAuZm9yd2FyZCAgICAgICAgICAgICAgICAgICAgICAgICAgICBIICAg
>ICAgICAyOCAgV2VkIEp1bCAxNSAxMToyOTowNyAxOTk4DQogIHB1YmxpY19o
>dG1sICAgICAgICAgICAgICAgICAgICAgICAgIEQgICAgICAgICAwICBUaHUg
>T2N0ICA4IDEzOjI2OjI3IDE5OTgNCiAgd3d3ICAgICAgICAgICAgICAgICAg
>ICAgICAgICAgICAgICAgRCAgICAgICAgIDAgIE1vbiBPY3QgMjYgMTE6MTQ6
>NTEgMTk5OA0KICB0ZXN0LmNnaSAgICAgICAgICAgICAgICAgICAgICAgICAg
>ICBBICAgICAgIDczOCAgU3VuIE9jdCAyNSAxNToyMDowMiAxOTk4DQogIHRl
>c3QudHh0ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAxNTMw
>ICBNb24gRmViICA4IDA5OjUxOjI3IDE5OTkNCg0KICAgICAgICAgICAgICAg
>IDU3MTEyIGJsb2NrcyBvZiBzaXplIDEzMTA3Mi4gMjA4MzIgYmxvY2tzIGF2
>YWlsYWJsZQ0Kc21iOiBcPiBleGl0DQpzYW5kbWFuOn4kIHNtYmNsaWVudCBc
>XFxccmVsYXlcXGNodGF5bG9yIC1VIGNodGF5bG9yDQpVbmFibGUgdG8gb3Bl
>biBjb25maWd1cmF0aW9uIGZpbGUgIi9vcHQvc2FtYmEvbGliL3NtYi5jb25m
>IiENCnBtX3Byb2Nlc3MgcmV0dW5lZCBmYWxzZQ0KQ2FuJ3QgbG9hZCAvb3B0
>L3NhbWJhL2xpYi9zbWIuY29uZiAtIHJ1biB0ZXN0cGFybSB0byBkZWJ1ZyBp
>dA0KICAuaGlzdG9yeSAgICAgICAgICAgICAgICAgICAgICAgICAgICBIICAg
>ICAgIDQ3NyAgTW9uIE1heSAxMCAxNToxMTo1MiAxOTk5DQogIHhyZWxheSAg
>ICAgICAgICAgICAgICAgICAgICAgICAgICAgIEEgICAgICAgIDk5ICBGcmkg
>SnVsIDI1IDE0OjQ3OjU4IDE5OTcNCiAgLmxvY2FsICAgICAgICAgICAgICAg
>ICAgICAgICAgICAgICBESCAgICAgICAgIDAgIEZyaSBTZXAgMTIgMTM6NDQ6
>NTQgMTk5Nw0KICAudmFjYXRpb24uZGlyICAgICAgICAgICAgICAgICAgICAg
>ICBIICAgICAgICAgMCAgTW9uIEp1bCAyOCAxMDowMTowOSAxOTk3DQogIC52
>YWNhdGlvbi5wYWcgICAgICAgICAgICAgICAgICAgICAgIEggICAgICAgICAw
>ICBNb24gSnVsIDI4IDEwOjAxOjA5IDE5OTcNCiAgTWFpbCAgICAgICAgICAg
>ICAgICAgICAgICAgICAgICAgICAgRCAgICAgICAgIDAgIEZyaSBTZXAgMTIg
>MTM6NDQ6NTQgMTk5Nw0KICB3d3cgICAgICAgICAgICAgICAgICAgICAgICAg
>ICAgICAgICBEICAgICAgICAgMCAgTW9uIE1heSAxMCAxNTowOTo0NCAxOTk5
>DQogIC5YYXV0aG9yaXR5ICAgICAgICAgICAgICAgICAgICAgICAgIEggICAg
>ICAgMTAxICBNb24gTWF5IDEwIDE1OjEwOjM2IDE5OTkNCg0KICAgICAgICAg
>ICAgICAgIDU3MTEyIGJsb2NrcyBvZiBzaXplIDEzMTA3Mi4gMjA4MzIgYmxv
>Y2tzIGF2YWlsYWJsZQ0Kc21iOiBcPiBleGl0DQpzYW5kbWFuOn4kIA0KDQoN
>Cg==
>--0-159320483-926430777=:47191
>Content-Type: TEXT/PLAIN; charset=US-ASCII; name="smb.conf"
>Content-Transfer-Encoding: BASE64
>Content-ID: <Pine.BSF.4.05.9905111052571.47191 at thelab.hub.org>
>Content-Description:
>Content-Disposition: attachment; filename="smb.conf"
>
>W2dsb2JhbF0NCg0KICAgZGVhZHRpbWUgPSA1DQogICB3b3JrZ3JvdXAgPSBB
>Q0FESUENCiAgIHNlcnZlciBzdHJpbmcgPSBTYW1iYSBTZXJ2ZXIgb24gUmVs
>YXkNCiAgIGhvc3RzIGFsbG93ID0gMTMxLjE2Mi4NCiAgIGxvYWQgcHJpbnRl
>cnMgPSB5ZXMNCiAgIHByaW50Y2FwIG5hbWUgPSBscHN0YXQNCiAgIGxvZyBs
>ZXZlbCA9IDENCiAgIGxvZyBmaWxlID0gL3Vzci9sb2NhbC92YXIvc2FtYmEv
>bG9nLiVtDQogICBtYXggbG9nIHNpemUgPSA1MA0KICAgc2VjdXJpdHkgPSBz
>ZXJ2ZXINCiAgIHBhc3N3b3JkIHNlcnZlciA9IHRob3IuYWNhZGlhdS5jYSAN
>CiAgIGVuY3J5cHQgcGFzc3dvcmRzID0geWVzDQogICBzb2NrZXQgb3B0aW9u
>cyA9IFRDUF9OT0RFTEFZIA0KICAgZG5zIHByb3h5ID0gbm8gDQoNCltob21l
>c10NCiAgIGNvbW1lbnQgPSBIb21lIERpcmVjdG9yaWVzDQogICBtYXAgYXJj
>aGl2ZSA9IHllcw0KICAgbWFwIHN5c3RlbSA9IHllcw0KICAgbWFwIGhpZGRl
>biA9IHllcw0KICAgcGF0aCA9ICVIDQogICBicm93c2VhYmxlID0gbm8NCiAg
>IHdyaXRhYmxlID0geWVzDQoNClt3d3ddDQogICBjb21tZW50ID0gUGVyc29u
>YWwgV1dXIERpcmVjdG9yaWVzDQogICBicm93c2VhYmxlID0gbm8NCiAgIHdy
>aXRhYmxlID0geWVzDQogICBwYXRoID0gJUgvd3d3DQoNClthaWNzXQ0KICAg
>Y29tbWVudCA9IEFjYWRpYSBJbnN0aXR1dGUgb2YgQ2FzZSBTdHVkaWVzDQog
>ICBwYXRoID0gL3Vzci9sb2NhbC9saWIvd3d3L2Zwcy9idXNpbmVzcy9haWNz
>DQogICBwdWJsaWMgPSBubw0KICAgd3JpdGFibGUgPSB5ZXMNCiAgIHZhbGlk
>IHVzZXJzID0gbWFyYywgZm9sbG93cywgMDI4MjE5Yw0KDQpbYnVzaW5lc3Nn
>cmFkc10NCiAgIGNvbW1lbnQgPSBTY2hvb2wgb2YgQnVzaW5lc3MgR3JhZHVh
>dGVzIFdlYiBTaXRlDQogICBwYXRoID0gL3Vzci9sb2NhbC9saWIvd3d3L2J1
>c2luZXNzZ3JhZHMNCiAgIHB1YmxpYyA9IG5vDQogICB3cml0YWJsZSA9IHll
>cw0KICAgdmFsaWQgdXNlcnMgPSBtYXJjLCBoYXJlLCAwMTg5MTZmLCAwMTkw
>NjZiDQogICBmb3JjZSB1c2VyID0gaGFyZQ0KDQpbY3NjbHViXQ0KICAgY29t
>bWVudCA9IENvbXB1dGVyIFNjaWVuY2UgQ2x1Yg0KICAgcGF0aCA9IC91c3Iv
>bG9jYWwvbGliL3d3dy9jbHVicy9jc2NsdWINCiAgIHB1YmxpYyA9IG5vDQog
>ICB3cml0YWJsZSA9IHllcw0KICAgdmFsaWQgdXNlcnMgPSAwMjAzMzJkDQog
>ICBmb3JjZSB1c2VyID0gMDIwMzMyZA0KDQpbcHJpbnRlcnNdDQogICBjb21t
>ZW50ID0gQWxsIFByaW50ZXJzDQogICBwYXRoID0gL3RtcA0KICAgYnJvd3Nl
>YWJsZSA9IG5vDQogICBndWVzdCBvayA9IG5vDQogICB3cml0YWJsZSA9IG5v
>DQogICBwcmludGFibGUgPSB5ZXMNCiAgIGNyZWF0ZSBtb2RlID0gMDcwMA0K
>ICAgcHJpbnQgY29tbWFuZCA9IC91c3IvdWNiL2xwciAtaCAtUCVwIC90bXAv
>JXMgOyBybSAvdG1wLyVzICYNCiAgIGxwcSBjb21tYW5kID0gL2Jpbi9scHN0
>YXQgLW8gJXAgJg0KICAgbHBybSBjb21tYW5kID0gL3Vzci9iaW4vY2FuY2Vs
>ICVwLSVqICYNCg0K
>--0-159320483-926430777=:47191--
>
>------------------------------
>
>Date: Tue, 11 May 1999 09:36:24 -0500 (CDT)
>From: "Kevin A. Pieckiel" <kapieckiel at harding.edu>
>To: samba at samba.org
>Subject: Samba's movin' SLOW! (fwd)
>Message-ID: <Pine.GSO.4.10.9905110935370.992-100000 at taz.harding.edu>
>
>Can anyone shed some light on this subject? I don't have a clue
>where to
>begin looking. It's RHL 6.0, Samba 2.0.3, stock kernel.
>
>Kevin
>
>---
> |\ _,,,---,,_
> ZZZzz /,`.-'`' -. ;-;;,_
> |,4- ) )-,_. ,\ ( `'-' Kevin Alan Pieckiel
> '---''(_/--' `-'_) kapieckiel at harding.edu
>
>(This message was written with vi)
>
>---------- Forwarded message ----------
>Date: Tue, 11 May 1999 00:33:58 -0500
>Subject: Samba's movin' SLOW!
>
>Kevin,
>
> I'm pleased to report that Samba's working reliably now, but I'm
>terribly concerned about its performance. I'm trying to copy an
>eleven meg
>file, and it's taken ten minutes! I'm definately thinking it's a
>client
>configuration problem, but I can't seem to think of anything to
>adjust on
>this thing. Got any ideas? Or any refrences to other sources of
>info?
>
> Thanks,
> Jason
>
>
>
>------------------------------
>
>End of SAMBA Digest 2086
>************************
More information about the samba
mailing list