On 11 Feb 2003 at 21:13, [EMAIL PROTECTED] wrote: > Send samba-technical mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.samba.org/mailman/listinfo/samba-technical > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of samba-technical digest..." > > > Today's Topics: > > 1. Unable to change password from win2k with a samba pdc > (Day, Michael A (Contractor-UAH)) > 2. Re: Samba 3.0: vfs_netatalk.c (Christopher R. Hertel) > 3. Re: Samba 3.0: vfs_netatalk.c (Anthony Liguori) > 4. Re: Samba 3.0: vfs_netatalk.c (Andrew Bartlett) > 5. Re: Samba 3.0: vfs_netatalk.c (Christopher R. Hertel) > > > ---------------------------------------------------------------------- > > Date: Tue, 11 Feb 2003 14:26:58 -0600 > From: "Day, Michael A (Contractor-UAH)" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Unable to change password from win2k with a samba pdc > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; > charset="iso-8859-1" > MIME-Version: 1.0 > Precedence: list > Message: 1 > > Howdy > > I've searched mailing lists and have not found anyone with the same problem > (as far as I can tell). > > I've setup a samba pdc (samba-2.2.7-2 rpm for RedHat 8.0) following the > instructions on the samba PDC HOWTO: > > http://us3.samba.org/samba/ftp/docs/htmldocs/Samba-PDC-HOWTO.html > > I've successfully setup the samba PDC and have joined a test client running > win2k to a domain called "VTC." Roaming profiles and login scripts work > fine. > > However, when I attempt to change the password from the win2k box I get the > following alert box: > > The system cannot change your password now because the domain VTC is not > available. > > Obviously the domain is available, since I just authenticated to it!! I am > fairly certain that this is not a problem with the passwd chat parameter, > since people on the newsgroup with that problem got an "incorrect password" > error (rather than a "domain not avaliable" error). > > In order to solve this problem I've: > > 1) brought down my firewall, > 2) tried to change passwords with and without the password chat parameter > being enabled > 3) enabled and disabled pam control over passwords > > all to no avail. > > Please help! -- log file and smb.conf are after my signature > > Mike Day > > Samba log file looks like this after a password change attempt: > -------------------------------------------------------------------- > > [2003/02/11 14:06:50, 2] lib/access.c:check_access(329) > Allowed connection from (136.205.103.37) > [2003/02/11 14:06:50, 0] rpc_server/srv_pipe.c:api_pipe_auth_process(1092) > api_pipe_auth_process: NTLMSSP check failed. > [2003/02/11 14:06:50, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(486) > process_request_pdu: failed to do auth processing. > [2003/02/11 14:06:50, 2] lib/access.c:check_access(329) > Allowed connection from (136.205.103.37) > [2003/02/11 14:06:50, 0] lib/util_sec.c:assert_gid(114) > Failed to set gid privileges to (0,99) now set to (0,-1) uid=(0,99) > [2003/02/11 14:06:50, 0] lib/util.c:smb_panic(1094) > PANIC: failed to set gid > > [2003/02/11 14:06:50, 2] lib/access.c:check_access(329) > Allowed connection from (136.205.103.37) > [2003/02/11 14:06:50, 0] lib/util_sec.c:assert_gid(114) > Failed to set gid privileges to (0,99) now set to (0,-1) uid=(0,99) > [2003/02/11 14:06:50, 0] lib/util.c:smb_panic(1094) > PANIC: failed to set gid > > END LOG FILE > --------------------------------------------------------------------- > > > smb.conf looks like this: > #---------------------------------------------------------------------- > # This is the main Samba configuration file. You should read the > # smb.conf(5) manual page in order to understand the options listed > # here. Samba has a huge number of configurable options (perhaps too > # many!) most of which are not shown in this example > # > # Any line which starts with a ; (semi-colon) or a # (hash) > # is a comment and is ignored. In this example we will use a # > # for commentry and a ; for parts of the config file that you > # may wish to enable > # > # NOTE: Whenever you modify this file you should run the command "testparm" > # to check that you have not made any basic syntactic errors. > # > #======================= Global Settings > ===================================== > [global] > > # workgroup = NT-Domain-Name or Workgroup-Name > workgroup = VTC > > #netbios name - name of host (PDC) -- which is this machine > netbios name = MX11 > > # server string is the equivalent of the NT Description field > server string = Samba PDC running %v > > # This option is important for security. It allows you to restrict > # connections to machines which are on your local network. The > # following example restricts access to two C class networks and > # the "loopback" interface. For more examples of the syntax see > # the smb.conf man page > hosts allow = 127.0.0.1 136.205.103.0/255.255.255.0 > > # if you want to automatically load your printer list rather > # than setting them up individually then you'll need this > printcap name = /etc/printcap > load printers = yes > > # It should not be necessary to spell out the print system type unless > # yours is non-standard. Currently supported print systems include: > # bsd, sysv, plp, lprng, aix, hpux, qnx > printing = lprng > > # Uncomment this if you want a guest account, you must add this to > /etc/passwd > # otherwise the user "nobody" is used > ; guest account = pcguest > > # this tells Samba to use a separate log file for each machine > # that connects > log file = /var/log/samba/%m.log > > # amount of detail in logs: > log level = 2 > > # Put a capping on the size of the log files (in Kb). > max log size = 100 > > # Security mode. Most people will want user level security. See > # security_level.txt for details. > security = user > > # Use password server option only with security = server > # The argument list may include: > # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] > # or to auto-locate the domain controller/s > # password server = * > ; password server = <NT-Server-Name> > > # Password Level allows matching of _n_ characters of the password for > # all combinations of upper and lower case. > ; password level = 8 > ; username level = 8 > > # You may wish to use password encryption. Please read > # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation. > # Do not enable this option unless you have read those documents > encrypt passwords = yes > smb passwd file = /etc/samba/smbpasswd > > # The following is needed to keep smbclient from spouting spurious errors > # when Samba is built with support for SSL. > ; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt > > > #add user script to simplify adding machines to the domain > #(creates UNIX trust accounts automatically) > # add user script = /usr/sbin/useradd -d /dev/null -g machines -s > /bin/false -M %u > > # The following are needed to allow password changing from Windows to > # update the Linux system password also. > # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above. > # NOTE2: You do NOT need these to allow workstations to change only > # the encrypted SMB passwords. They allow the Unix password > # to be kept in sync with the SMB password. > # unix password sync = Yes > # passwd program = /usr/bin/passwd %u > # passwd chat = *New*password* %n\n *Retype*new*password* %n\n > *passwd:*all*authentication*tokens*updated*successfully* > > # You can use PAM's password change control flag for Samba. If > # enabled, then PAM will be used for password changes when requested > # by an SMB client instead of the program listed in passwd program. > # It should be possible to enable this without changing your passwd > # chat parameter for most setups. > pam password change = yes > > # Unix users can map to different SMB User names > ; username map = /etc/samba/smbusers > > # Using the following line enables you to customise your configuration > # on a per machine basis. The %m gets replaced with the netbios name > # of the machine that is connecting > ; include = /etc/samba/smb.conf.%m > > # This parameter will control whether or not Samba should obey PAM's > # account and session management directives. The default behavior is > # to use PAM for clear text authentication only and to ignore any > # account or session management. Note that Samba always ignores PAM > # for authentication in the case of encrypt passwords = yes > obey pam restrictions = yes > > # Most people will find that this option gives better performance. > # See speed.txt and the manual pages for details > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > > # Configure Samba to use multiple interfaces > # If you have multiple network interfaces then you must list them > # here. See the man page for details. > ; interfaces = 192.168.12.2/24 192.168.13.2/24 > > # Configure remote browse list synchronisation here > # request announcement to, or browse list sync from: > # a specific host or from / to a whole subnet (see below) > ; remote browse sync = 192.168.3.25 192.168.5.255 > # Cause this host to announce itself to local subnets here > ; remote announce = 192.168.1.255 192.168.2.44 > > # Browser Control Options: > # set local master to no if you don't want Samba to become a master > # browser on your network. Otherwise the normal election rules apply > local master = yes > > # OS Level determines the precedence of this server in master browser > # elections. The default value should be reasonable > > # when changed to PDC, changed from 31 to 64 > os level = 64 > > # Domain Master specifies Samba to be the Domain Master Browser. This > # allows Samba to collate browse lists between subnets. Don't use this > # if you already have a Windows NT domain controller doing this job > domain master = yes > > # Preferred Master causes Samba to force a local browser election on startup > # and gives it a slightly higher chance of winning the election > preferred master = yes > > # Enable this if you want Samba to be a domain logon server for > # Windows95 workstations. > domain logons = yes > > # if you enable domain logons then you may want a per-machine or > # per user logon script > # run a specific logon batch file per workstation (machine) > ; logon script = %m.bat > # run a specific logon batch file per username > ; logon script = %U.bat > > # Where to store roving profiles (only for Win95 and WinNT) > # %L substitutes for this servers netbios name, %U is username > # You must uncomment the [Profiles] share below > > #user profiles and home directory > #logon home was removed because it's only needed for > #Windows 9x / ME clients (which we don't have) > #logon home = \\%L\%U\.profile > logon drive = H: > logon path = \\%L\profiles\%U > > #sync samba and UNIX passwords when the samba password is changed > > # Windows Internet Name Serving Support Section: > # WINS Support - Tells the NMBD component of Samba to enable it's WINS > Server > ; wins support = yes > > # WINS Server - Tells the NMBD components of Samba to be a WINS Client > # Note: Samba can be either a WINS Server, or a WINS Client, but NOT > both > # wins server = 136.205.60.2 > > # WINS Proxy - Tells Samba to answer name resolution queries on > # behalf of a non WINS capable client, for this to work there must be > # at least one WINS Server on the network. The default is NO. > ; wins proxy = yes > > # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names > # via DNS nslookups. The built-in default for versions 1.9.17 is yes, > # this has been changed in version 1.9.18 to no. > dns proxy = no > > # Case Preservation can be handy - system default is _no_ > # NOTE: These can be set on a per share basis > ; preserve case = no > ; short preserve case = no > # Default case is normally upper case for all DOS files > ; default case = lower > # Be very careful with case sensitivity - it can break things! > ; case sensitive = no > > #domain admininstrator group > domain admin group = mike.day > > #============================ Share Definitions > ============================== > [homes] > comment = Home Directories > browseable = no > writable = yes > valid users = %S > create mode = 0664 > directory mode = 0775 > # If you want users samba doesn't recognize to be mapped to a guest user > ; map to guest = bad user > > > # Un-comment the following and create the netlogon directory for Domain > Logons > [netlogon] > comment = Network Logon Service > ; path = /usr/local/samba/lib/netlogon > path = /home/netlogon > ; guest ok = yes > writable = no > read only = yes > write list = mike.day > ; 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/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 people in > # the "staff" group > ;[public] > ; comment = Public Stuff > ; path = /home/samba > ; public = yes > ; writable = yes > ; printable = no > ; write list = @staff > > # Other examples. > # > # A private printer, usable only by fred. Spool data will be placed in > fred's > # home directory. Note that fred must have write access to the spool > directory, > # wherever it is. > ;[fredsprn] > ; comment = Fred's Printer > ; valid users = fred > ; path = /home/fred > ; printer = freds_printer > ; public = no > ; writable = no > ; printable = yes > > # A private directory, usable only by fred. Note that fred requires write > # access to the directory. > ;[fredsdir] > ; comment = Fred's Service > ; path = /usr/somewhere/private > ; valid users = fred > ; public = no > ; writable = yes > ; printable = no > > # a service which has a different directory for each machine that connects > # this allows you to tailor configurations to incoming machines. You could > # also use the %U option to tailor it by user name. > # The %m gets replaced with the machine name that is connecting. > ;[pchome] > ; comment = PC Directories > ; path = /usr/local/pc/%m > ; public = no > ; writable = yes > > # A publicly accessible directory, read/write to all users. Note that all > files > # created in the directory by users will be owned by the default user, so > # any user with access can delete any other user's files. Obviously this > # directory must be writable by the default user. Another user could of > course > # be specified, in which case all files would be owned by that user instead. > ;[public] > ; path = /usr/somewhere/else/public > ; public = yes > ; only guest = yes > ; writable = yes > ; printable = no > > # The following two entries demonstrate how to share a directory so that two > # users can place files there that will be owned by the specific users. In > this > # setup, the directory should be writable by both users and should have the > # sticky bit set on it to prevent abuse. Obviously this could be extended to > # as many users as required. > ;[myshare] > ; comment = Mary's and Fred's stuff > ; path = /usr/somewhere/shared > ; valid users = mary fred > ; public = no > ; writable = yes > ; printable = no > ; create mask = 0765 > > [webroot] > comment = MX11 Webroot > path = /var/www > valid users = jerome mike.day colby.pitts kniphfer > public = no > writable = yes > printable = no > create mask = 0765 > browseable = yes > > [mysql_databases] > comment = mysql databases > path = /var/lib/mysql > valid users = jerome > public = no > writable = no > printable = no > browseable = yes > > [profiles] > path = /home/samba/profiles > writeable = yes > browseable = no > create mask = 0600 > directory mask = 0700 > #----------------------------------------------------------------------
I once had the same problem. With 2.2.7a and Win2k client. I noticed that after I removed "passwd chat" I could change my password client-side. I let the default "password chat" take affect. unix passwd sync = yes pam password change = no passwd program = /usr/bin/passwd %u encrypt passwords = yes Andrew Kennerly > ------------------------------ > > Date: Tue, 11 Feb 2003 14:52:57 -0600 > From: "Christopher R. Hertel" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Samba 3.0: vfs_netatalk.c > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > MIME-Version: 1.0 > Precedence: list > Message: 2 > > Paul Green wrote: > > Anthony Liguori [mailto:aliguor at us.ibm.com] wrote: > > > > > > scandir() (and it's [alpha|version]sort() brethren) is a BSD/Linux-ism > > > and therefore isn't very portable. Since this is in a VFS module (and > > > therefore only optional) I guess this is ok. > > > > then Herb Lewis [mailto:herb at sgi.com] found this info: > > > IRIX: scandir, scandir64, alphasort, alphasort64 > > > BSD: scandir, alphasort > > > > I just checked and neither scandir* nor alphasort* are in POSIX-1996 or > > POSIX-2001. I'm not trying to build vfs_netatalk here on VOS, but if I > > was, it looks like I'd be writing some code first. I don't consider > > these functions portable either. My vote is for sticking with functions > > in POSIX if at all possible. > > > > PG > > I have not been following this thread closely, but it occurs to me that we > have tools that would make this easy to implement by hand. If I > understand the docs, the goal is to create an array of pointers to > directory entry structures (the latter allocated via malloc()). > > One catch is that there is a difference between BSD and System V > implementations, but that's something that should be handle-able with > ./configure. It seems to me that in either case the data could be sorted > using the binary tree stuff or by qsort(). This should be fairly do-able. > > Chris -)----- > > -- > Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel > jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. > ubiqx Team -- http://www.ubiqx.org/ -)----- [EMAIL PROTECTED] > OnLineBook -- http://ubiqx.org/cifs/ -)----- [EMAIL PROTECTED] > ------------------------------ > > Date: Tue, 11 Feb 2003 14:00:18 -0700 > From: Anthony Liguori <[EMAIL PROTECTED]> > To: "Christopher R. Hertel" <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Samba 3.0: vfs_netatalk.c > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII > MIME-Version: 1.0 > Precedence: list > Message: 3 > > > > > > > One catch is that there is a difference between BSD and System V > > implementations, but that's something that should be handle-able with > > ./configure. It seems to me that in either case the data could be sorted > > using the binary tree stuff or by qsort(). This should be fairly > do-able. > > On some systems, scandir() doesn't even exist. I think the only reason why > there's been any discussion as to whether this is a problem is because of > the fact that it's a module. I think the general sentiment has been that > even modules need to be concerned about portability unless there's good > reason. > > Anthony Liguori > Linux/Active Directory Interoperability > Linux Technology Center (LTC) - IBM Austin > E-mail: [EMAIL PROTECTED] > Phone: (512) 838-1208 > Tie Line: 678-1208 > > > > > "Christopher R. Hertel" <[EMAIL PROTECTED]> > > Sent by: To: > [EMAIL PROTECTED] > samba-technical-bounces+aliguor=us.ibm.com@list cc: > > s.samba.org >Subject: Re: Samba 3.0: vfs_netatalk.c > > > > > 02/11/2003 02:52 PM > > > > > > > > > Paul Green wrote: > > Anthony Liguori [mailto:aliguor at us.ibm.com] wrote: > > > > > > scandir() (and it's [alpha|version]sort() brethren) is a BSD/Linux-ism > > > and therefore isn't very portable. Since this is in a VFS module (and > > > therefore only optional) I guess this is ok. > > > > then Herb Lewis [mailto:herb at sgi.com] found this info: > > > IRIX: scandir, scandir64, alphasort, alphasort64 > > > BSD: scandir, alphasort > > > > I just checked and neither scandir* nor alphasort* are in POSIX-1996 or > > POSIX-2001. I'm not trying to build vfs_netatalk here on VOS, but if I > > was, it looks like I'd be writing some code first. I don't consider > > these functions portable either. My vote is for sticking with functions > > in POSIX if at all possible. > > > > PG > > I have not been following this thread closely, but it occurs to me that we > have tools that would make this easy to implement by hand. If I > understand the docs, the goal is to create an array of pointers to > directory entry structures (the latter allocated via malloc()). > > One catch is that there is a difference between BSD and System V > implementations, but that's something that should be handle-able with > ./configure. It seems to me that in either case the data could be sorted > using the binary tree stuff or by qsort(). This should be fairly do-able. > > Chris -)----- > > -- > Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel > jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. > ubiqx Team -- http://www.ubiqx.org/ -)----- [EMAIL PROTECTED] > OnLineBook -- http://ubiqx.org/cifs/ -)----- [EMAIL PROTECTED] > > > > ------------------------------ > > Date: 12 Feb 2003 08:11:42 +1100 > From: Andrew Bartlett <[EMAIL PROTECTED]> > To: "Christopher R. Hertel" <[EMAIL PROTECTED]> > Cc: Multiple recipients of list SAMBA-TECHNICAL <[EMAIL PROTECTED]> > Subject: Re: Samba 3.0: vfs_netatalk.c > Message-ID: <1044997902.27042.113.camel@piglett> > In-Reply-To: <[EMAIL PROTECTED]> > References: <[EMAIL PROTECTED]> > Content-Type: multipart/signed; micalg=pgp-sha1; > protocol="application/pgp-signature"; > boundary="=-NFnYjtgvxlJMd/tyPKcN" > MIME-Version: 1.0 > Precedence: list > Message: 4 > > > --=-NFnYjtgvxlJMd/tyPKcN > Content-Type: text/plain > Content-Transfer-Encoding: quoted-printable > > On Wed, 2003-02-12 at 07:52, Christopher R. Hertel wrote: > > Paul Green wrote: > > > Anthony Liguori [mailto:aliguor at us.ibm.com] wrote: > > > >=20 > > > > scandir() (and it's [alpha|version]sort() brethren) is a BSD/Linux-is= > m=20 > > > > and therefore isn't very portable. Since this is in a VFS module (an= > d > > > > therefore only optional) I guess this is ok. > > > > > > then Herb Lewis [mailto:herb at sgi.com] found this info: > > > > IRIX: scandir, scandir64, alphasort, alphasort64 > > > > BSD: scandir, alphasort > > > > > > I just checked and neither scandir* nor alphasort* are in POSIX-1996 or > > > POSIX-2001. I'm not trying to build vfs_netatalk here on VOS, but if I= > =20 > > > was, it looks like I'd be writing some code first. I don't consider=20 > > > these functions portable either. My vote is for sticking with function= > s > > > in POSIX if at all possible. > > > > > > PG > >=20 > > I have not been following this thread closely, but it occurs to me that w= > e > > have tools that would make this easy to implement by hand. If I > > understand the docs, the goal is to create an array of pointers to > > directory entry structures (the latter allocated via malloc()). > >=20 > > One catch is that there is a difference between BSD and System V > > implementations, but that's something that should be handle-able with > > ./configure. It seems to me that in either case the data could be sorted > > using the binary tree stuff or by qsort(). This should be fairly do-able= > . > > If you read the code, then it's pretty obvious that we just need the > entries in the directory - unsorted and one at a time. As such, my > understanding it that we can re-implement as readdir(). > > Andrew Bartlett > > --=20 > Andrew Bartlett [EMAIL PROTECTED] > Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] > Student Network Administrator, Hawker College [EMAIL PROTECTED] > http://samba.org http://build.samba.org http://hawkerc.net > > --=-NFnYjtgvxlJMd/tyPKcN > Content-Type: application/pgp-signature; name=signature.asc > Content-Description: This is a digitally signed message part > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQA+SWcOw6AkmCjZ77cRArRzAJ45DdlJ0MGjP8Yx3mQtE3fdE4Fe/QCfRs9G > dgFMgBsi0PiV1NIAy1JLCt8= > =d9r4 > -----END PGP SIGNATURE----- > > --=-NFnYjtgvxlJMd/tyPKcN-- > > ------------------------------ > > Date: Tue, 11 Feb 2003 15:13:05 -0600 > From: "Christopher R. Hertel" <[EMAIL PROTECTED]> > To: Anthony Liguori <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Samba 3.0: vfs_netatalk.c > Message-ID: <[EMAIL PROTECTED]> > In-Reply-To: <[EMAIL PROTECTED]> > References: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > MIME-Version: 1.0 > Precedence: list > Message: 5 > > On Tue, Feb 11, 2003 at 02:00:18PM -0700, Anthony Liguori wrote: > > > > > > > > > > > One catch is that there is a difference between BSD and System V > > > implementations, but that's something that should be handle-able with > > > ./configure. It seems to me that in either case the data could be sorted > > > using the binary tree stuff or by qsort(). This should be fairly > > do-able. > > > > On some systems, scandir() doesn't even exist. I think the only reason why > > there's been any discussion as to whether this is a problem is because of > > the fact that it's a module. I think the general sentiment has been that > > even modules need to be concerned about portability unless there's good > > reason. > > Thus my thinking that it might be worth writing a replacement that would > be platform-independent. The only hitch, I *believe*, is that there may > be differences in the dirent structure between systems, but surely this is > something we've solved elsewhere. > > Chris -)----- > > -- > Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel > jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. > ubiqx Team -- http://www.ubiqx.org/ -)----- [EMAIL PROTECTED] > OnLineBook -- http://ubiqx.org/cifs/ -)----- [EMAIL PROTECTED] > ------------------------------ > > _______________________________________________ > samba-technical mailing list > [EMAIL PROTECTED] > http://lists.samba.org/mailman/listinfo/samba-technical > > > End of samba-technical Digest, Vol 2, Issue 46 > **********************************************