From getnag at rediffmail.com Thu May 2 11:10:54 2002 From: getnag at rediffmail.com (Naag Mummaneni) Date: Fri Feb 13 23:41:28 2004 Subject: Winbind-Solaris Documentation Message-ID: <20020502111054.22040.qmail@webmail9.rediffmail.com> Hi, I just configured my Solaris box to logon to my Windows 2k Domain after working on it for three days.I am sorry to say that I have found no documentation for setting up Samba-winbind on solaris.And I feel that a Prestigious opensource project like Samba shouldnt be blamed for this.So I modified the documentation that come with samba & prepared this one for "solaris" so that no other administrator will face problems that I did. I hope the Samba group will put this documentation part in the distribution.Please find the attached doc file for the documentation. Thanks Naag Mummaneni(getnag@rediffmail.com) -------------------------------------------------------- Installation and Configuration of Winbind on Solaris. This HOWTO describes how to get winbind services up and running to control access and authenticate users on your Solaris box using the winbind services which come with SAMBA 2.2.x latest CVS Checkout.Make sure you are using the latest Samba 2.2.x cvs checkout as other versions come with a lots of bugs regarding winbind .And even the Latest Samba Stable Release is also not an exception to this. Introduction This HOWTO describes the procedures used to get winbind up and running on a Solaris system. Winbind is capable of providing access and authentication control for Windows Domain users through an NT or Win2K PDC for 'regular' services, such as telnet and ftp, as well for SAMBA services. Why should I to this? ?h?n This allows the SAMBA administrator to rely on the authentication mechanisms on the NT/Win2K PDC for the authentication of domain members. NT/Win2K users no longer need to have separate accounts on the SAMBA server. Who should be reading this document? ?h?n This HOWTO is designed for system administrators. If you are implementing SAMBA on a file server and wish to (fairly easily) integrate existing NT/Win2K users from your PDC onto the SAMBA server, this HOWTO is for you. Requirements If you have a samba configuration file that you are currently using... BACK IT UP! If your system already uses PAM, back up the /etc/pam.conf file ! If you haven't already made a boot disk, MAKEONE NOW! Messing with the pam configuration file can make it nearly impossible to log in to yourmachine. That's why you want to be able to boot back into your machine in single user mode and restore your /etc/pam.conf back to the original state they were in if you get frustrated with the way things are going. ;-) Please refer to the main SAMBA web page or, better yet, your closest SAMBA mirror site for instructions on downloading the source code of Samba 2.2.x from the SAMBA CVS repository. To allow Domain users the ability to access SAMBA shares and files, as well as potentially other services provided by your SAMBA machine, PAM (pluggable authentication modules) must be setup properly on your machine. In order to compile the winbind modules, you should have at least the pam libraries resident on your system. Solaris 7/8 has its pam modules coming with the distribution itself. Testing Things Out Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all smbd, nmbd, and winbindd processes that may be running. Configure and compile SAMBA The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon whether or not you have previously built the Samba binaries. root# autoconf root# make clean root# rm config.cache root# ./configure --with-winbind --with-pam root# make root# make install This will, by default, install SAMBA in /usr/local/samba. See the main SAMBA documentation if you want to install SAMBA somewhere else. It will also build the winbindd executable and libraries. Configure nsswitch.conf and the winbind libraries The libraries needed to run the winbindd daemon through nsswitch need to be copied to their proper locations, so root# cp ../samba/source/nsswitch/libnss_winbind.so /usr/lib I also found it necessary to make the following symbolic links: root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.2 root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2 Now, as root you need to edit /etc/nsswitch.conf to allow user and group entries to be visible from the winbindd daemon. My /etc/nsswitch.conf file look like this after editing: passwd: files winbind group: files winbind Configure smb.conf Several parameters are needed in the smb.conf file to control the behavior of winbindd. Configure smb.conf These are described in more detail in the winbindd(8) man page. My smb.conf file was modified to include the following entries in the [global] section: [global] <...> # The previous documentation says to as the "winbind seperator " #directive also but it is no longer supported. # use uids from 10000 to 20000 for domain users winbind uid = 10000-20000 # use gids from 10000 to 20000 for domain groups winbind gid = 10000-20000 # allow enumeration of winbind users and groups winbind enum users = yes winbind enum groups = yes # give winbind users a real shell (only needed if they have telnet access) template homedir = /home/winnt/%D/%U template shell = /bin/bash Join the SAMBA server to the PDC domain Enter the following command to make the SAMBA server join the PDC domain, where DOMAIN is the name of your Windows domain and Administrator is a domain user who has administrative privileges in the domain. root# /usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator The proper response to the command should be: "Joined the domain DOMAIN" where DOMAIN is your DOMAIN name. Start up the winbindd daemon and test it! Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of SAMBA start, but it is possible to test out just the winbind portion first. To start up winbind services, enter the following command as root: root# /usr/local/samba/bin/winbindd I'm always paranoid and like to make sure the daemon is really running... root# ps -ae | grep winbindd This command should produce output like this, if the daemon is running 3025 ? 00:00:00 winbindd Now... for the real test, try to get some information about the users on your PDC root# /usr/local/samba/bin/wbinfo -u This should echo back a list of users on your Windows users on your PDC. For example, I get the following response: CEO\Administrator CEO\burdell CEO\Guest CEO\jt-ad CEO\krbtgt CEO\TsInternetUser root# /usr/local/samba/bin/wbinfo -g CEO\Domain Admins CEO\Domain Users CEO\Domain Guests CEO\Domain Computers CEO\Domain Controllers CEO\Cert Publishers CEO\Schema Admins CEO\Enterprise Admins CEO\Group Policy Creator Owners The function 'getent' can now be used to get unified lists of both local and PDC users and groups. Try the following command: root# getent passwd You should get a list that looks like your /etc/passwd list followed by the domain users with their new uids, gids, home directories and default shells. The same thing can be done for groups with the command root# getent group Fix the /etc/rc.d/init.d/samba.server startup files The winbindd daemon needs to start up after the smbd and nmbd daemons are running. To accomplish this task, you need to modify the /etc/init.d/samba.server script to add commands to invoke this daemon in the proper sequence. My /etc/init.d/samba.server file starts up smbd, nmbd, and winbindd from the /usr/local/samba/bin directory directly. samba.server if [ ! -d /usr/bin ] then # /usr not mounted exit fi killproc() { # kill the named process(es) pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server case "$1" in 'start') # # Edit these lines to suit your installation (paths, workgroup, host) # echo Starting SMBD /usr/local/samba/bin/smbd -D #-s /usr/local/samba/smb.conf echo Starting NMBD /usr/local/samba/bin/nmbd -D #-l /usr/local/samba/var/log -s /usr/local/samba/smb.conf echo Starting Winbind Daemon /usr/local/samba/bin/winbindd ;; 'stop') killproc nmbd killproc smbd killproc winbindd ;; *) echo "Usage: /etc/init.d/samba.server { start | stop }" ;; esac If you restart the smbd, nmbd, and winbindd daemons at this point, you should be able to connect to the samba server as a domain member just as if you were a local user. Configure Winbind and PAM If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other services, keep reading. The pam configuration file need to be altered in this step. (Did you remember to make backups of your original /etc/pam.conf file? If not, do it now.) You will need a pam module to use winbindd with these other services. This module will be compiled in the ../source/nsswitch directory by default when we used ./configure --with-pam option. root# make nsswitch/pam_winbind.so from the ../source directory. The pam_winbind.so file should be copied to the location of your other pam security modules. On my Solaris 8, this was the /usr/lib/security directory. root# cp ../samba/source/nsswitch/pam_winbind.so /usr/lib/security The /etc/pam.conf need to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes that I made.You can customize the pam.conf file as per your requirements,but be sure of those changes because in the worst case it will leave your system nearly impossible to boot. # #ident "@(#)pam.conf 1.14 99/09/16 SMI" # # Copyright (c) 1996-1999, Sun Microsystems, Inc. # All Rights Reserved. # # PAM configuration # # Authentication management # login auth required /usr/lib/security/pam_winbind.so login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass # rlogin auth sufficient /usr/lib/security/pam_winbind.so rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1 rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass # dtlogin auth sufficient /usr/lib/security/pam_winbind.so dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass # rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1 other auth sufficient /usr/lib/security/pam_winbind.so other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass # # Account management # login account sufficient /usr/lib/security/pam_winbind.so login account requisite /usr/lib/security/$ISA/pam_roles.so.1 login account required /usr/lib/security/$ISA/pam_unix.so.1 # dtlogin account sufficient /usr/lib/security/pam_winbind.so dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1 dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1 # other account sufficient /usr/lib/security/pam_winbind.so other account requisite /usr/lib/security/$ISA/pam_roles.so.1 other account required /usr/lib/security/$ISA/pam_unix.so.1 # # Session management # other session required /usr/lib/security/$ISA/pam_unix.so.1 # # Password management # #other password sufficient /usr/lib/security/pam_winbind.so other password required /usr/lib/security/$ISA/pam_unix.so.1 dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1 # # Support for Kerberos V5 authentication (uncomment to use Kerberos) # #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1 #other account optional /usr/lib/security/$ISA/pam_krb5.so.1 #other session optional /usr/lib/security/$ISA/pam_krb5.so.1 #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass I also added a try_first_pass line after the winbind.so line to get rid of annoying double prompts for passwords. Now restart your Samba & try connecting through your application that you configured in the pam.conf. _________________________________________________________ Click below to visit monsterindia.com and review jobs in India or Abroad http://monsterindia.rediff.com/jobs From jerry at samba.org Thu May 2 23:00:55 2002 From: jerry at samba.org (Gerald Carter) Date: Fri Feb 13 23:41:28 2004 Subject: Winbind-Solaris Documentation In-Reply-To: <20020502111054.22040.qmail@webmail9.rediffmail.com> Message-ID: On 2 May 2002, Naag Mummaneni wrote: > Hi, > > I just configured my Solaris box to logon to my Windows 2k Domain after > working on it for three days.I am sorry to say that I have found no > documentation for setting up Samba-winbind on solaris.And I feel that a > Prestigious opensource project like Samba shouldnt be blamed for this.So > I modified the documentation that come with samba & prepared this one > for "solaris" so that no other administrator will face problems that I > did. I hope the Samba group will put this documentation part in the > distribution.Please find the attached doc file for the documentation. > > Thanks > Naag Mummaneni(getnag@rediffmail.com) Thanks. I've included this as a text file for the 2.2.4 release. I'll incorporate it into the SGML docs later. cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From anthony at netcourrier.com Mon May 6 10:58:43 2002 From: anthony at netcourrier.com (Anthony Leste) Date: Fri Feb 13 23:41:28 2004 Subject: Connection Reset by peers Message-ID: <3CD661E3.FDE3F5DB@netcourrier.com> Hi all, I have a problem with samba and it stops the service. I think that this problem happens when big files are being transfered to or from the server. Or simply when there are high traffic on the server. Please find bellow a sample of a samba logs that appears in the samba users log file. [2002/04/09 14:45:50, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer I'm running Samba onto a RH 7.2 server and i've upgrade the samba after i've start having the problem but the probem persists with the latest version 2.2.3a. Any help to solve this problem are most welcome. Thanks, Anthony From aleste at netcourrier.com Mon May 6 11:01:05 2002 From: aleste at netcourrier.com (Anthony Leste) Date: Fri Feb 13 23:41:28 2004 Subject: Problem with samba shutting down Message-ID: <3CD66271.17722446@netcourrier.com> Hi all, I have a problem with samba and it stops the service. I think that this problem happens when big files are being transfered to or from the server. Or simply when there are high traffic on the server. Please find bellow a sample of a samba logs that appears in the samba users log file. [2002/04/09 14:45:50, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer I'm running Samba onto a RH 7.2 server and i've upgrade the samba after i've start having the problem but the probem persists with the latest version 2.2.3a. Any help to solve this problem are most welcome. Thanks, Anthony Sorry my return e-mail was wrong From edm32 at email.com Sat May 11 07:49:43 2002 From: edm32 at email.com (edm) Date: Fri Feb 13 23:41:28 2004 Subject: MY INHERITANCE Message-ID: <20020510235613.0F00442A5@lists.samba.org> Date:May 10,2002. Email:edm32@email.com Dear Sir, I am Mr.Eduado De Mello, one of the Principal Commanders of the Union for the Total Independence of Angola,UNITA. Well needless telling a very long story here for our story is indeed interwoven with the history of the world and the liberation struggle in the Southern African region of the African continent. The bubble burst just some weeks ago when my supreme commander, the late Dr.Jonas Savimbi was killed in an encounter with the government forces of the MPLA government of my country.The rest is now history but suffice it to say that I am tired of the unfortunate role of waging a war against my fatherland. I have therefore decided to pull out my troupes from the bush even if the other field commanders decide otherwise I am therefore poised to effect a new beginning in my life and I have decided to make South Africa my new home at least for the interim period until I am sufficiently sure that I would be welcome home whole heartedly by the MPLA government in Luanda the capital of Angola. Needles to say I was the single most important commander who was very close to the late supreme commander; Dr.Jonas Savimbi.Indeed because I am a brother to one of his wives,he confided in me a great deal. The result of such trust is my reason for contacting you. I was the commander whom he sent to deposit the sum of Thirty two million USD ($32million) with a security/finance company in South Africa.This was immediately after the events of September 11,2001 in the United States of America.Indeed it had become increasingly difficult to move large volumes of money around the world particularly for a liberation movement like UNITA hence the recourse to keeping themoney with the security company in South Africa. Ihave decided to inherit this money which was taken out and deposited with the said security/finance company as cash in Hundred dollar denominations.The money is kept in my signature and would have been used in the purchase of arms and ammunition for the purposes of continuing the civil war in Angola.The supreme commander is dead and as already stated I have decided to quite the whole thing and this is without regard to the fact that other commanders may wish to continue ! I want to cooperate with you in my decision to inherit the $32million.I am still in the bush here but I have been able to establish contact with the company in South Africa to the effect that I would soon come to take possession of the money that I kept with them. Note also that I deposited the money as a foreign national who is the head of a Mining company in Angola (Never as a commander of UNITA). If you are able to cooperate with me over this am willing to give you 20% of the $32million.Please come back to me through email: edm32@email.com The security/finance company is standing by to receive my instructions on this and I will link you up with them as soon as you are ready to take possession of the $32million. Finally you are to note that in you reply, you are to state your residential or company address and if possible send a copy of your international passport so as to assure me that my money is safe in your hands. Yours truly, Eduado de Mello From mike2000jan at hotmail.com Tue May 14 23:01:15 2002 From: mike2000jan at hotmail.com (Mike Davis) Date: Fri Feb 13 23:41:28 2004 Subject: How can I help make the docs better? (When I'm too green to know how?) Message-ID: I want to start off by saying thank you to all those who are responsible for Samba. It is a fantastic application which I'm sure has only been made possible by a lot of hard work with not much to show in return accept for some personal satisfaction and the occasional word of praise and thanks. Kudos to all. I am new to Samba and not a programmer, but want to help, and have 20 years of computer experience. Since I am new to Unix/Linux , I AM reading lots of books, man pages, docs and reading them slowly. While doing this, I am finding the odd typo or spelling error. Now the dilema is: on the one hand I am probably a good source for catching errors because I NEED to go through the documentation slowly and repetitively to understand it while those in the know only scan the docs as reference material. On the other hand, it is consuming a lot of my time just to learn about Samba and how to configure Linux so I don't have time (yet) to learn about CVS, 'diff', etc. (I'm not even sure that these are the preferred methods for notifying someone of a correction) Or put another way, I still don't have enough experience to know how to inform the people who work on a project that I have found an error (and there are many projects which I have been introduced to over the last year, presumably each group having their own prefered method of contact). I don't want to wast anyones time (yours or mine) by reporting things that have already been fixed, but I went to www.samba.org and it wasn't apparent (to someone new that is since its always easy once you've been shown how to do something) where I could find the work-in-progress files (ie. the MOST up-to-date files). I assumed if I could find these then I could see if someone else has already corrected the mistakes I have found. The documents themselves, while giving credit to those who worked on them, did NOT have a contact email address which actually surprised me (two examples noted below are 'man' pages). I did find http://samba.org/samba-patches/ and looked at a few of the messages to see if this was the right place but it seemed like it was more for programmers who had patches that would correct code not a simple grammer or spelling error (which is all I have to offer). To be honest I was hesitant because I don't honestly know what the programming term "patch" means and if it applies to correcting grammar or spelling. I only continued with this editorial comment because I found the errors intact in the http://www.samba.org/samba/docs/ documents. Bottom line, if it isn't quite obvious how to report a document mistake, then the people who are mostly reading them - the neophytes, like me - are not going to help out in the small way that we can. Having said that, this post got sent here, because I read the following: "If you have an idea for a patch but can't write the code for some reason then discuss it on the Samba mailing list and try to find someone else who can work up a patch. If you send your idea here it will be deleted. " mind you the link is to http://lists.samba.org/ and does not explicitly say which of the 27 possible lists a message should be sent to - most of them are of course not candidates. If I am sending this to the wrong list, I appoligize for the intrusion. My intentions were not only good, but I believe that others may be willing to help if it was easy enough for them to do so. I spent quite some trying to figure out what was the prefered way to report the few little mistakes that I have found -- including contacting a programming friend who suggested "don't worry about it" -- and short of learning about 'diff' could not find the answer to my question. Suggestions: 1) Make it clear where the active documents are (those that are eligable for correction). 2) In the appropriate place add a page that gives a link to more detailed instructions about how to help (I know easier said then done isn't it :-) ) ; I appreciate that you are bound to get all sorts of wacky emails that don't pertain to the material at hand, or are staring the user right in the face, or tell you what the mistake was but not in which document (I'm hoping that this post doesn't fall into ALL of these pitfalls ;-) )... I could go on -- about how I'm sure you have better things to spend your time on rather than a missing letter here or there, and how its not worth lossing ones shit over ... oops I mean shirt ... but I think I have said enough. Keep up the good work one and all. Love that Samba!! Mike Davis :-)) PS. Please forgive any typos or spelling erors ;-) you may find in this message. --- Minor corrections I have found 1) http://www.samba.org/samba/docs/man/smbpasswd.5.html "Each field ithin each line" should be "Each field within each line" 2) http://www.samba.org/samba/docs/man/smbpasswd.8.html "password will beed to be manually" should be "password will need to be manually" 3)UNIX_INSTALL.txt and the HTML version (eg http://de.samba.org/samba/ftp/docs/textdocs/UNIX_INSTALL.txt) (and http://samba.org/samba/ftp/docs/htmldocs/Samba-HOWTO-Collection.html) "Your should get back a list of" should be "You should get back a list of" [This one is dated Apr 2002 and specifically mention Jerry Carter jerry@samba.org, so I will CC him a copy of this note -- especially since his name seems to be everywhere within the Samba Doc stuff that I found -- where do you get the time? Keep up the excellent work.] _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com From jra at samba.org Tue May 14 23:27:00 2002 From: jra at samba.org (Jeremy Allison) Date: Fri Feb 13 23:41:28 2004 Subject: How can I help make the docs better? (When I'm too green to know how?) In-Reply-To: ; from mike2000jan@hotmail.com on Tue, May 14, 2002 at 11:01:15PM +0000 References: Message-ID: <20020514162700.P13545@va.samba.org> On Tue, May 14, 2002 at 11:01:15PM +0000, Mike Davis wrote: > If I am sending this to the wrong list, I appoligize for the intrusion. Don't worry - this list is fine ! > --- Minor corrections I have found > 1) http://www.samba.org/samba/docs/man/smbpasswd.5.html > "Each field ithin each line" should be "Each field within each line" > 2) http://www.samba.org/samba/docs/man/smbpasswd.8.html > "password will beed to be manually" should be "password will need to be > manually" > 3)UNIX_INSTALL.txt and the HTML version > (eg http://de.samba.org/samba/ftp/docs/textdocs/UNIX_INSTALL.txt) > (and http://samba.org/samba/ftp/docs/htmldocs/Samba-HOWTO-Collection.html) > "Your should get back a list of" should be "You should get back a list of" I've applied these changes to the SAMBA_2_2 tree - they'll be fixed in 2.2.5. Thanks a lot ! Jeremy. From k.blin at gmx.net Thu May 16 13:46:09 2002 From: k.blin at gmx.net (Kai Blin) Date: Fri Feb 13 23:41:28 2004 Subject: How can I help make the docs better? (When I'm too green to know how?) In-Reply-To: References: Message-ID: <20020516134609.GA11988@molgen-1.iah.medizin.uni-tuebingen.de> * Mike Davis [14/05/02, 23:01:15]: > I am new to Samba and not a programmer, but want to help, and have 20 > years of computer experience. Since I am new to Unix/Linux , I AM > reading lots of books, man pages, docs and reading them slowly. Congrats, this really shows you're an old school computer user. It's hard to find those nowadays. > While doing this, I am finding the odd typo or spelling error. Now the > dilema is: on the one hand I am probably a good source for catching > errors because I NEED to go through the documentation slowly and > repetitively to understand it while those in the know only scan the > docs as reference material. On the other hand, it is consuming a lot > of my time just to learn about Samba and how to configure Linux so I > don't have time (yet) to learn about CVS, 'diff', etc. (I'm not even > sure that these are the preferred methods for notifying someone of a > correction) Or put another way, I still don't have enough experience > to know how to inform the people who work on a project that I have > found an error (and there are many projects which I have been > introduced to over the last year, presumably each group having their > own prefered method of contact). This is only too true. *sic* I've not been around for a while, but IIRC not everybody gets developers access to the cvs repository. I recall that I learned how to use diff just to send some corrections for typos on the web page, too. ;) > > I don't want to wast anyones time (yours or mine) by reporting things > that have already been fixed, but I went to www.samba.org and it > wasn't apparent (to someone new that is since its always easy once > you've been shown how to do something) where I could find the > work-in-progress files (ie. the MOST up-to-date files). I assumed if I > could find these then I could see if someone else has already > corrected the mistakes I have found. The documents themselves, while > giving credit to those who worked on them, did NOT have a contact > email address which actually surprised me (two examples noted below > are 'man' pages). I did find http://samba.org/samba-patches/ and > looked at a few of the messages to see if this was the right place but > it seemed like it was more for programmers who had patches that would > correct code not a simple grammer or spelling error (which is all I > have to offer). To be honest I was hesitant because I don't honestly > know what the programming term "patch" means and if it applies to > correcting grammar or spelling. I only continued with this editorial > comment because I found the errors intact in the > http://www.samba.org/samba/docs/ documents. Well, this might be an issue. The samba-docs mailing list should be mentioned in there I think, since it's the place where these things should be done. > Bottom line, if it isn't quite obvious how to report a document > mistake, then the people who are mostly reading them - the neophytes, > like me - are not going to help out in the small way that we can. > > Having said that, this post got sent here, because I read the > following: "If you have an idea for a patch but can't write the code > for some reason then discuss it on the Samba mailing list and try to > find someone else who can work up a patch. If you send your idea here > it will be deleted. " mind you the link is to http://lists.samba.org/ > and does not explicitly say which of the 27 possible lists a message > should be sent to - most of them are of course not candidates. > > If I am sending this to the wrong list, I appoligize for the > intrusion. My intentions were not only good, but I believe that others > may be willing to help if it was easy enough for them to do so. I > spent quite some trying to figure out what was the prefered way to > report the few little mistakes that I have found -- including > contacting a programming friend who suggested "don't worry about it" > -- and short of learning about 'diff' could not find the answer to my > question. Well, thanks anyway. It's more work than others would have put into it, since it's "just a spelling/grammar error". See some programmers, they will second your friend. ;) > Suggestions: 1) Make it clear where the active documents are (those > that are eligable for correction). > 2) In the appropriate place add a page that gives a link to more > detailed instructions about how to help (I know easier said then done > isn't it :-) ) ; I appreciate that you are bound to get all sorts of > wacky emails that don't pertain to the material at hand, or are > staring the user right in the face, or tell you what the mistake was > but not in which document (I'm hoping that this post doesn't fall into > ALL of these pitfalls ;-) )... I could go on -- about how I'm sure > you have better things to spend your time on rather than a missing > letter here or there, and how its not worth lossing ones shit over ... > oops I mean shirt ... but I think I have said enough. We get worse here, like people sending mail that should go to the samba list to this list here.. We'll survive that, I guess. (Flame /dev/null if you think different) > [This one is dated Apr 2002 and specifically mention Jerry Carter > jerry@samba.org, so I will CC him a copy of this note -- especially > since his name seems to be everywhere within the Samba Doc stuff that > I found -- where do you get the time? Keep up the excellent work.] It's said he's using clones.. but don't tell anybody.. ;) People like him are the driving force of free software development. Cheers, Kai -- Kai Blin, private email One organism, one vote. From fredrikv at biochem.kth.se Fri May 17 07:15:02 2002 From: fredrikv at biochem.kth.se (Fredrik Viklund) Date: Fri Feb 13 23:41:28 2004 Subject: How can I help make the docs better? (When I'm too green to know how?) In-Reply-To: <20020516134609.GA11988@molgen-1.iah.medizin.uni-tuebingen. de> References: Message-ID: <5.1.0.14.2.20020517090805.03830040@kiev.biotech.kth.se> At 15:46 2002-05-16 +0200, Kai Blin wrote: >* Mike Davis [14/05/02, 23:01:15]: > > On the other hand, it is consuming a lot > > of my time just to learn about Samba and how to configure Linux so I > > don't have time (yet) to learn about CVS, 'diff', etc. (I'm not even > > sure that these are the preferred methods for notifying someone of a > > correction) > >This is only too true. *sic* I've not been around for a while, but IIRC >not everybody gets developers access to the cvs repository. I recall >that I learned how to use diff just to send some corrections for typos >on the web page, too. ;) One way could be to have a web interface to diff the docs for easy submission of typos and similar. I could request any doc file, get it in a text box in a form, make my changes (or copy/paste them), press the Diff button and *ta da* get the diff back to submit. ? /Fredrik From jerry at samba.org Mon May 20 15:18:41 2002 From: jerry at samba.org (Gerald Carter) Date: Fri Feb 13 23:41:28 2004 Subject: How can I help make the docs better? (When I'm too green to know how?) In-Reply-To: <5.1.0.14.2.20020517090805.03830040@kiev.biotech.kth.se> Message-ID: On Fri, 17 May 2002, Fredrik Viklund wrote: > At 15:46 2002-05-16 +0200, Kai Blin wrote: > >* Mike Davis [14/05/02, 23:01:15]: > > > On the other hand, it is consuming a lot > > > of my time just to learn about Samba and how to configure Linux so I > > > don't have time (yet) to learn about CVS, 'diff', etc. (I'm not even > > > sure that these are the preferred methods for notifying someone of a > > > correction) > > > >This is only too true. *sic* I've not been around for a while, but IIRC > >not everybody gets developers access to the cvs repository. I recall > >that I learned how to use diff just to send some corrections for typos > >on the web page, too. ;) > > One way could be to have a web interface to diff the docs for easy submission > of typos and similar. > > I could request any doc file, get it in a text box in a form, make my changes > (or copy/paste them), press the Diff button and *ta da* get the diff back > to submit. It is just as easy to download a copy of the cvs tree and run diff -u locally IMO. :-) cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From jerry at samba.org Mon May 20 15:44:11 2002 From: jerry at samba.org (Gerald Carter) Date: Fri Feb 13 23:41:28 2004 Subject: How can I help make the docs better? (When I'm too green to know how?) In-Reply-To: Message-ID: On Tue, 14 May 2002, Mike Davis wrote: > so I don't have time (yet) to learn about CVS, 'diff', etc. This docs list is a good point of contact. I generally act as the CVS check in point, but there are several others working on updates, correcttions, etc... CVS is not perfect, but probably very simple for what you need to be able to do. See http://samba.org/samba/cvs/html for details on obtaining Samba cvs code. Diff's against release code is also ok because the docs don't tend to be a moving target as much as the source code is. For submitting patches, mt preferred method is diff -u oldfile newfile > newfile.diff and send as an attachment. It is better IMO to place the diff on an FTP server so as to save bandwidth on the list but its not a strict rule. Also I like patches as attachments better than inline because the latter notmally converts tabs to spaces and is annoying when trying to apply the patch. > I don't want to wast anyones time (yours or mine) by reporting things that > have already been fixed, but I went to www.samba.org and it wasn't apparent > (to someone new that is since its always easy once you've been shown how to > do something) where I could find the work-in-progress files (ie. the MOST > up-to-date files). I assumed if I could find these then I could see if Anything that is wrong jis fair game :-) > someone else has already corrected the mistakes I have found. The documents > themselves, while giving credit to those who worked on them, did NOT have a > contact email address which actually surprised me (two examples noted below > are 'man' pages). I did find http://samba.org/samba-patches/ and looked at a > few of the messages to see if this was the right place but it seemed like it > was more for programmers who had patches that would correct code not a > simple grammer or spelling error (which is all I have to offer). To be Our patch submission/bug tracking system could use some more maintaince. Simo has been doing a good job, but it is really bigger than one person. What you did here weas fine (and appreciated). > Bottom line, if it isn't quite obvious how to report a document mistake, > then the people who are mostly reading them - the neophytes, like me - > are not going to help out in the small way that we can. That's probably our fault then. We should provide more helpful information to encourage people to correct mistakes in our docs. > Suggestions: > 1) Make it clear where the active documents are (those that are eligable for > correction). Everything except for textdocs/outdated/ should be up for grabs. > 2) In the appropriate place add a page that gives a link to more detailed > instructions about how to help (I know easier said then done isn't it :-) ) Duely noted. Will look into this. > Keep up the good work one and all. Love that Samba!! Thanks for the updates Mike. :-) cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From dcimaro at ipruniv.cce.unipr.it Thu May 23 12:19:10 2002 From: dcimaro at ipruniv.cce.unipr.it (Diego Cimarosa) Date: Fri Feb 13 23:41:28 2004 Subject: W2K can't join samba pdc domain : "Interface unknown" Message-ID: <002501c20254$0cc460a0$655d4ea0@giurisp.unipr.it> I have a lab with 27 Windows 98 clients perfectly working with samba 2.2.4 and Linux Read Hat 5.2 (!!!) But I can't join with Windows 2000 client ... The strange thing is that I can browse and use shared directories with no problems (Windows 2000 prompt with a user and password "Login as " box and i can access as a normal user) but when I try to change from workgroup to domain in Network Proprierties and login as root I got, after 50seconds : "Interface unknown". I've traced the error "samr_io_userinfo_ctr: unknown switch level 0x1a" and the patch in rpc_server/srv_samr.c seems working because it exit with a TRUE value ... On client side, in the event logger, I see an error (more or less ... translated from italian W2K version): Network Service Access ended with error : Network access is not a valid Win32 application I think is something related to lmss.exe ... but nothing more ... PLEASE PLEASE PLEASE PLEASE .... HH EE LL PP !!!!! thanks everybody! ciao! (i've been trying for two weeks ... more or less 3/4 hours per day ... so many configurations ... !!!) @@@@@@@@@ LOG.NMBD @@@@@@@@ [2002/05/23 13:33:09, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.4 started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2002/05/23 13:33:09, 0] lib/debug.c:debug_message(259) INFO: Debug class all level = 2 (pid 23855 from pid 23855) [2002/05/23 13:33:09, 2] nmbd/nmbd.c:main(832) Becoming a daemon. [2002/05/23 13:33:09, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 23858 [2002/05/23 13:33:09, 2] lib/interface.c:add_interface(81) added interface ip=160.78.93.100 bcast=160.78.93.255 nmask=255.255.255.0 [2002/05/23 13:33:09, 2] nmbd/nmbd_subnetdb.c:make_subnet(192) making subnet name:160.78.93.100 Broadcast address:160.78.93.255 Subnet mask:255.255.255.0 [2002/05/23 13:33:09, 2] nmbd/nmbd_subnetdb.c:make_subnet(192) making subnet name:UNICAST_SUBNET Broadcast address:160.78.93.100 Subnet mask:160.78.93.100 [2002/05/23 13:33:09, 2] nmbd/nmbd_subnetdb.c:make_subnet(192) making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0 [2002/05/23 13:33:09, 2] nmbd/nmbd_subnetdb.c:make_subnet(192) making subnet name:WINS_SERVER_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0 [2002/05/23 13:33:09, 2] nmbd/nmbd_winsserver.c:initialise_wins(184) initialise_wins: Can't open wins database file wins.dat. Error was No such file or directory [2002/05/23 13:33:09, 0] nmbd/nmbd_logonnames.c:add_logon_names(155) add_domain_logon_names: Attempting to become logon server for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:09, 2] nmbd/nmbd_logonnames.c:become_logon_server(126) become_logon_server: Atempting to become logon server for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:09, 0] nmbd/nmbd_logonnames.c:add_logon_names(155) add_domain_logon_names: Attempting to become logon server for workgroup LABGIURI on subnet UNICAST_SUBNET [2002/05/23 13:33:09, 2] nmbd/nmbd_logonnames.c:become_logon_server(126) become_logon_server: Atempting to become logon server for workgroup LABGIURI on subnet UNICAST_SUBNET [2002/05/23 13:33:09, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(339) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup LABGIURI, subnet UNICAST_SUBNET. [2002/05/23 13:33:09, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(354) become_domain_master_browser_wins: querying WINS server at IP 160.78.93.100 for domain master browser name LABGIURI<1b> on workgroup LABGIURI [2002/05/23 13:33:09, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(114) become_logon_server_success: Samba is now a logon server for workgroup LABGIURI on subnet UNICAST_SUBNET [2002/05/23 13:33:09, 2] nmbd/nmbd_become_dmb.c:become_domain_master_stage1(178) become_domain_master_stage1: Becoming domain master browser for workgroup LABGIURI on subnet UNICAST_SUBNET [2002/05/23 13:33:09, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(114) ***** Samba server LINUX is now a domain master browser for workgroup LABGIURI on subnet UNICAST_SUBNET ***** [2002/05/23 13:33:09, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(291) become_domain_master_browser_bcast: Attempting to become domain master browser on workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:09, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(305) become_domain_master_browser_bcast: querying subnet 160.78.93.100 for domain master browser on workgroup LABGIURI [2002/05/23 13:33:13, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(114) become_logon_server_success: Samba is now a logon server for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:13, 2] nmbd/nmbd_become_dmb.c:become_domain_master_stage1(178) become_domain_master_stage1: Becoming domain master browser for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:13, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 19849 received with no matching record. [2002/05/23 13:33:13, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 19850 received with no matching record. [2002/05/23 13:33:13, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:13, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:15, 2] nmbd/nmbd_elections.c:send_election_dgram(43) send_election_dgram: Sending election packet for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:17, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:17, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:17, 2] nmbd/nmbd_elections.c:send_election_dgram(43) send_election_dgram: Sending election packet for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:17, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(114) ***** Samba server LINUX is now a domain master browser for workgroup LABGIURI on subnet 160.78.93.100 ***** [2002/05/23 13:33:17, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:17, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:17, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x7 [2002/05/23 13:33:18, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:18, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 [2002/05/23 13:33:20, 2] nmbd/nmbd_elections.c:send_election_dgram(43) send_election_dgram: Sending election packet for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:22, 2] nmbd/nmbd_elections.c:send_election_dgram(43) send_election_dgram: Sending election packet for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:24, 2] nmbd/nmbd_elections.c:send_election_dgram(43) send_election_dgram: Sending election packet for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:24, 2] nmbd/nmbd_elections.c:run_elections(208) run_elections: >>> Won election for workgroup LABGIURI on subnet 160.78.93.100 <<< [2002/05/23 13:33:24, 2] nmbd/nmbd_become_lmb.c:become_local_master_browser(549) become_local_master_browser: Starting to become a master browser for workgroup LABGIURI on subnet 160.78.93.100 [2002/05/23 13:33:32, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) ***** Samba name server LINUX is now a local master browser for workgroup LABGIURI on subnet 160.78.93.100 ***** [2002/05/23 13:33:32, 2] nmbd/nmbd_browsesync.c:announce_local_master_browser_to_domain_master_browse r(118) announce_local_master_browser_to_domain_master_browser: We are both a domain and a local master browser for workgroup LABGIURI. Do not announce to ourselves. [2002/05/23 13:33:32, 2] nmbd/nmbd_browsesync.c:sync_with_dmb(157) sync_with_dmb: Initiating sync with domain master browser LINUX<20> at IP 160.78.93.100 for workgroup LABGIURI [2002/05/23 13:34:21, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 @@@@@@@@ IS THIS A BUG ??? [2002/05/23 13:34:21, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x12 @@@@@@@@ IS THIS A BUG ??? [2002/05/23 13:34:21, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_logon_packet: Logon from 160.78.93.131: code = 0x7 @@@@@@@ /usr/local/samba/private/smbpasswd EXTRACT @@@@@@@ root:0:D088F6514A6B6E68E68AA26A841A86FA:467FBBB5C266F912DB3E8045C9BAA7CC:[UX ]:LCT-3CECD083: pclabgiuri23$:1723:10332205BFE3C612E98C3945F928AE1E:0E1E921277BE6A6403480CBC 23AB67FF:[DW ]:LCT-3CECD3FE: @@@@@@@@@@@@@ LOG.WINDOWS 2000 CLIENT @@@@@@@ [2002/05/23 13:33:19, 2] lib/access.c:check_access(329) Allowed connection from (160.78.93.131) [2002/05/23 13:33:19, 2] rpc_server/srv_samr_nt.c:_samr_lookup_domain(2050) Returning domain sid for domain LABGIURI -> S-1-5-21-462040359-1077694541-2412441076 [2002/05/23 13:33:20, 2] rpc_parse/parse_samr.c:samr_io_userinfo_ctr(6300) samr_io_userinfo_ctr: unknown switch level 0x1a [2002/05/23 13:33:20, 0] rpc_server/srv_samr.c:api_samr_set_userinfo(670) api_samr_set_userinfo: Unable to unmarshall SAMR_Q_SET_USERINFO. [2002/05/23 13:35:27, 2] smbd/server.c:exit_server(461) Closing connections @@@@@@@@@@@ SMB.CONF @@@@@@@@@? #======================= Global Settings ===================================== [global] add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u domain logons = Yes domain master = yes encrypt passwords = Yes guest ok = No guest only = No hosts allow = 160.78.93. 160.78.92. 127. local master = Yes lock dir = /usr/local/samba/var/locks log file = /usr/local/samba/var/log.%m log level = 2 logon drive = H: logon home = \\%N\%U logon path = \\%N\%U logon script = %m.bat name resolve order = host wins lmhosts bcast netbios name = linux pid directory = /usr/local/samba/var/locks preferred master = yes security = user security mask = 0777 server string = Linux Red Hat - Samba Server %v smb passwd file = /usr/local/samba/private/smbpasswd wins proxy = No wins support = Yes workgroup = labgiuri #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = yes writable = yes create mask = 0700 directory mask = 0700 guest ok = no # Un-comment the following and create the netlogon directory for Domain Logons [netlogon] comment = Network Logon Service path = /usr/local/samba/netlogon/scripts guest ok = no writable = no share modes = no root preexec = "/root/dologin %u C %m" root postexec = "/root/dologin %u D %m" [shared] comment = Directory condivisa sul Server Linux path = /shared public = yes read only = no writable = yes [ftp] comment = FTP Pubblico path = /ftp public = yes read only = yes writable = yes From min.yang at intel.com Thu May 23 18:16:46 2002 From: min.yang at intel.com (Yang, Min) Date: Fri Feb 13 23:41:28 2004 Subject: (no subject) Message-ID: <3D386AED1B47D411A94300508B11F18702860A4F@fmsmsx116.fm.intel.com> I have just installed samba server on Solaris 7. Each time there is a connection from NT/Window, SAMBA has following error: Anybody konw why? Thank you Min smbd version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/05/23 11:03:23, 0] tdb/tdbutil.c:tdb_log(475) tdb(/usr/local/samba/private/secrets.tdb): tdb_reopen: failed to obtain active lock Following is my smb.conf file: [global] workgroup = LOCERD01 netbios name = js1 server string = Samba Server load printers = yes printcap name = /etc/printers.conf log file = /usr/local/samba/var/log.%m max log size = 50 security = server password server = xxxxxx encrypt passwords = yes socket options = TCP_NODELAY local master = no domain master = no domain logons = yes wins support = yes wins server = xxxxxxxxxx dns proxy = no kernel oplocks = yes #============================ Share Definitions ============================== [homes] guest ok = no comment = Home Directories writable = yes # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /usr/local/samba/lib/netlogon ; guest ok = yes ; writable = no ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles] ; path = /usr/local/samba/profiles ; browseable = no ; guest ok = yes # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/lp/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = yes writable = no printable = yes comment = Temporary file space path = /proj/u15/tmp read only = no public = yes # This one is useful for people to share files [whitney] comment = project whitney directory path = /proj/whitney writable = yes valid users = @whitney create mode = 0664 directory mode = 1775 case sensitive = yes strict locking = yes From jerry at samba.org Tue May 28 15:23:56 2002 From: jerry at samba.org (Gerald (Jerry) Carter) Date: Fri Feb 13 23:41:28 2004 Subject: W2K can't join samba pdc domain : "Interface unknown" In-Reply-To: <002501c20254$0cc460a0$655d4ea0@giurisp.unipr.it> Message-ID: On Thu, 23 May 2002, Diego Cimarosa wrote: > I've traced the error "samr_io_userinfo_ctr: unknown switch level 0x1a" > and the patch in rpc_server/srv_samr.c seems working because it exit > with a TRUE value ... Don't do this. The client should back down to a lower info level. cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--