Re: [Samba] Newbie: listing workgroups and hosts

2005-04-13 Thread Bruce Hohl
 Hello everybody,
 
 I think that this should a be a trivial task but I've
 already read the documentation but couldn't find out how
 to get a list of all workgroups and their hosts with
 smbclient. Could somebody give me a hint please(and
 sorry for that silly question)?
 
 Greetings,
 -Rainer Hahnekamp
 
try: # nmbstatus

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] SuSE 9.2 Firewall, Ports for Samba, XP Client and userprofile

2005-04-13 Thread Bruce Hohl
 Hello!
 
 i have some problems with my SuSE 9.2  and the samba
 ports: if the xp client wants to loggin in samba domain, I
 get the message at the  announcement - usersettings: the
 servercopy of the serverstored profile was  not found. No
 saving of the changed profile -. After the loggin there
 are no more problems  with the xp client in samba. After
 googling I collimated the ports in the  SuSE Firewall:
 137:139 445. But the same error message as before. If I 
 shutdown the firewall, there isn't this errormessage.
 Which ports have I to  configure in the firewall?
 
 Best regards
 Andreas 
 
This works for me:
Yast  System  /etc/sysconfig editor
network  firewall  SuSEfirewall2

SuseFW2 changes for Samba:
fw_services_ext_tcp = 137 138 139 445
fw_services_ext_udp = 137 138
fw_allow_incoming_highports_tcp = 137 445
fw_allow_incoming_highports_udp = 137 445
fw_allow_fw_broadcast = yes
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Mounting Samba shares under KDE 3.x

2005-04-04 Thread Bruce Hohl
 Hi,
 
 I'm trying to mount the samba shares into my SuSE 9.2
 workstation, with  no luck. Our server is in production,
 so there's nothing wrong in our  samba server. But I can't
 mount my shares under KDE.
 
 Doing it with mount -t smbfs gives me a lot of Time Out
 errors, and the  mount is unable to show any files. Seems
 that the smbfs module is broken  in the 2.6.8 kernel. I
 don't know if this is a kernel problem or SuSE  problem.
 
 Mounting with CIFS works flawlessly in console. But
 Konqueror hangs  solid when accessing the mounted
 directory. I've tested it with KDE 3.3  and KDE 3.4 and
 same problem. But using the smb:// functionality under 
 konqueror works fine. The problem with this approach is
 that KDE don't  let me mount (as far I know) these shares
 under my filesystem, and a lot  of apps don't like
 accessing docs in this way. I must copy the files,  work
 locally and return them in the samba server.
 
 Really I'm clueless with this issue. Anybody has succeeded
 mounting  samba shares under SuSE 9.2 and KDE 3.x?
 

This works for me with SuSE 9.1:
# smbmount //server/share /mnt/point -o
username=some_user

The user must have appropriate permissions in Samba and the
Linux file systems.

Also, for SuSE see /etc/samba/smbfstab.  This file has
instructions for mounting the shares during boot.

Bruce
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Re: Problem with pdf printing (SOLVED)

2005-03-31 Thread Bruce Hohl
 Luca Olivetti wrote:
  Vincent Mikalinis wrote:
  
   Hi all,
  
   Has anyone figured out why some people are not having
a
   problem with similar configurations, however some
   people require that we add the lpq command =
/bin/true 
   line?  It is a very good and simple solution. Should
all 
   pdf printers be set with this option for future
reference? 
  
  I don't know, but I bypassed the problem by using a pdf
  backend in cups  (which is really a simple shell script
  that I tailored to my needs), so  even the pdf printer
  is a normal cups printer. 
 
 Somebody called misty said the same thing in IRC #samba
 yesterday, but  they had to run before they could show me
 the contents of the file.  Would you mind sending this to
 the list? I think it is still at least  slighlty
 on-topic.
 
 The person on IRC said they then have another cron job
 that goes and  emails the so created pdf every 5 minutes
 to the users that created  them. For one situation here
 that would be THE ideal solution. So if  misty or anybody
 else that happens to have the same solution wouldn't  mind
 emailing me the details for that, that would be really
 appreciated.
 

There is a cups backend pdf creator tool by Volker Behr
which
can be set up to write the pdf file to the user's home
directory.  To do this the tool must be compiled with this
option (documentation is available).  Using this option
there is
no need to use a script + cron job to move the pdf to the
user's 
home directory.  The drawback of using this method is that
cups 
security must be relaxed a bit to include RunAsUser=No. 
The 
tool can be found at:  

http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] ADS member.

2005-03-22 Thread Bruce Hohl
 I have follow an example in samba-3 by example book,
 where it explain how to relocate a samba server as ADS
 member domain, in a sentence it said to delete all
 /var/lib/samba/*tdb files, so winbindd_cache.tdb and
 winbind_idmap.tdb files but when I start the samba
 server again in ADS new domain something's wrong. Because
 it is not able to map the same UID and GID as before, I
 don't use any id_map backend but only retrive users and
 group by winbind.
 Fortunately I have made a backup copy of tdb files so I
 can copy them over. How it doesn't work, it is normal?
 Thanks a lot.
 Marco.  
 -- 
Marco,
You may find the infomation at the following link useful:
http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/idmapper.html#id2559247
See topics:
Domain Member Server or Domain Member Client
IDMAP_RID with Winbind
Bruce
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] smbstatus question

2005-03-16 Thread Bruce Hohl
Hello All,
The following is partial output from smbstatus.  Please note
that under the Machine column some WinXP PC's are listed by
text name and some WinXP PC's are listed by IP.  What could
account for this difference?  Is this anything I should be
concerned about?  I am running winbind and joined to a Win2K
domain using security = ads.  Thanks for any comments,
suggestions, etc.
Bruce 


filesrv1:~ # smbstatus
Samba version 3.0.9-2.1.6-SUSE
PID Username  Group Machine
---
30652   aaukerDomain Users  aauker1 
(192.168.1.36)
24769   multidnc  Domain Users  multi-dnc   
(192.168.1.11)
25275   aschneiderDomain Users  192.168.1.27
(192.168.1.27)
25182   ups_user  Domain Users  192.168.1.40
(192.168.1.40)
25810   administrator  Domain Users  192.168.1.71
(192.168.1.71)
31498   mlindamoodDomain Users  mlindamood2 
(192.168.1.25)
25337   assembly  Domain Users  assembly
(192.168.1.127)
24930   apostal   Domain Users  192.168.1.49
(192.168.1.49)
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] User not reported on file locked message

2005-03-07 Thread Bruce Hohl
I have a very small problem.  Thanks for any suggestions.

Say user1 logs onto a Windows XP workstation and opens
file1.  Then, if user2 attempts to open the file from
another workstation the following message is displayed: 
file1 is locked for editing by '' 

Problem: *user1* is not displayed between the single quotes.

However, say user1 logs onto a Win98 workstation and opens
file1.  Then, if user2 attempts to open the file the
expected message is displayed:  file1 is locked for editing
by 'user1'.

Maybe (?) this is related to the above problem:
I have also noted that the smbstatus command always shows
the text Machine name for Win98 clients but for WinXP
clients only sometimes the text Machine name is shown, but
usually the IP address is shown:

filesrv1:~ # smbstatus

Samba version 3.0.9-2.1.6-SUSE
PID Username  Group Machine
-
27745   user1   Domain Users  192.168.1.49
(192.168.1.49)   XP box 
27739   user2   Domain Users  192.168.1.44
(192.168.1.44)   XP box
27753   user3   Domain Users  192.168.1.40
(192.168.1.40)   XP box
27880   user4   Domain Users  spickett98  
(192.168.1.207)  98 box
 1317   user5   Domain Users  darmc   
(192.168.1.14)   XP box
28480   user6   Domain Users  saw 
(192.168.1.251)  98 box


Environment:
SLES 9 + Samba 3.0.9 from SuSE update service joined to
Win2K domain.

[global]
workgroup = GROTECOMPANY
realm = GROTECOMPANY.COM
security = ADS
map to guest = Bad User
password server = visual1, filesrv2, *
log level = 1
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
preferred master = No
local master = No
domain master = No
wins server = 192.168.1.201 192.168.1.55
ldap ssl = no
idmap backend = idmap_rid:GROTECOMPANY=1-2
allow trusted domains = No
idmap uid = 1-2
idmap gid = 1-2
winbind separator = /
winbind use default domain = Yes
printer admin = GROTECOMPANY/administrator
admin users = GROTECOMPANY/administrator
log file = /var/log/samba/%M.log

I also get the same behavior on my Samba test box which is
running SuSE 9.1 with Samba 3.0.11.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] User not reported on file locked message

2005-03-07 Thread Bruce Hohl
I have a very small problem.  Thanks for any suggestions.

Say user1 logs onto a Windows XP workstation and opens
file1.  Then, if user2 attempts to open the file from
another workstation the following message is displayed: 
file1 is locked for editing by '' 

Problem: *user1* is not displayed between the single quotes.

However, say user1 logs onto a Win98 workstation and opens
file1.  Then, if user2 attempts to open the file the
expected message is displayed:  file1 is locked for editing
by 'user1'.

Maybe (?) this is related to the above problem:
I have also noted that the smbstatus command always shows
the text Machine name for Win98 clients but for WinXP
clients only sometimes the text Machine name is shown, but
usually the IP address is shown:

filesrv1:~ # smbstatus

Samba version 3.0.9-2.1.6-SUSE
PID Username  Group Machine
-
27745   user1   Domain Users  192.168.1.49
(192.168.1.49)   XP box 
27739   user2   Domain Users  192.168.1.44
(192.168.1.44)   XP box
27753   user3   Domain Users  192.168.1.40
(192.168.1.40)   XP box
27880   user4   Domain Users  spickett98  
(192.168.1.207)  98 box
 1317   user5   Domain Users  darmc   
(192.168.1.14)   XP box
28480   user6   Domain Users  saw 
(192.168.1.251)  98 box


Environment:
SLES 9 + Samba 3.0.9 from SuSE update service joined to
Win2K domain.

[global]
workgroup = GROTECOMPANY
realm = GROTECOMPANY.COM
security = ADS
map to guest = Bad User
password server = visual1, filesrv2, *
log level = 1
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
preferred master = No
local master = No
domain master = No
wins server = 192.168.1.201 192.168.1.55
ldap ssl = no
idmap backend = idmap_rid:GROTECOMPANY=1-2
allow trusted domains = No
idmap uid = 1-2
idmap gid = 1-2
winbind separator = /
winbind use default domain = Yes
printer admin = GROTECOMPANY/administrator
admin users = GROTECOMPANY/administrator
log file = /var/log/samba/%M.log

I also get the same behavior on my Samba test box which is
running SuSE 9.1 with Samba 3.0.11.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] User not reported on file locked message

2005-03-07 Thread Bruce Hohl
I have a very small problem.  Thanks for any suggestions.

Say user1 logs onto a Windows XP workstation and opens
file1.  Then, if user2 attempts to open the file from
another workstation the following message is displayed: 
file1 is locked for editing by '' 

Problem: *user1* is not displayed between the single quotes.

However, say user1 logs onto a Win98 workstation and opens
file1.  Then, if user2 attempts to open the file the
expected message is displayed:  file1 is locked for editing
by 'user1'.

Maybe (?) this is related to the above problem:
I have also noted that the smbstatus command always shows
the text Machine name for Win98 clients but for WinXP
clients only sometimes the text Machine name is shown, but
usually the IP address is shown:

filesrv1:~ # smbstatus

Samba version 3.0.9-2.1.6-SUSE
PID Username  Group Machine
-
27745   user1   Domain Users  192.168.1.49
(192.168.1.49)   XP box 
27739   user2   Domain Users  192.168.1.44
(192.168.1.44)   XP box
27753   user3   Domain Users  192.168.1.40
(192.168.1.40)   XP box
27880   user4   Domain Users  spickett98  
(192.168.1.207)  98 box
 1317   user5   Domain Users  darmc   
(192.168.1.14)   XP box
28480   user6   Domain Users  saw 
(192.168.1.251)  98 box


Environment:
SLES 9 + Samba 3.0.9 from SuSE update service joined to
Win2K domain.

[global]
workgroup = GROTECOMPANY
realm = GROTECOMPANY.COM
security = ADS
map to guest = Bad User
password server = visual1, filesrv2, *
log level = 1
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
preferred master = No
local master = No
domain master = No
wins server = 192.168.1.201 192.168.1.55
ldap ssl = no
idmap backend = idmap_rid:GROTECOMPANY=1-2
allow trusted domains = No
idmap uid = 1-2
idmap gid = 1-2
winbind separator = /
winbind use default domain = Yes
printer admin = GROTECOMPANY/administrator
admin users = GROTECOMPANY/administrator
log file = /var/log/samba/%M.log

I also get the same behavior on my Samba test box which is
running SuSE 9.1 with Samba 3.0.11.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] [homes] no accessible

2005-02-24 Thread Bruce Hohl
 On a server linuxbox using ADS security in a Windows
 2003 Active  directory, part of smb.conf is ...
 
 [srvbackup]
 force user = sambaa
 writeable = yes
 valid users = ADS-Name+Administrator,ADS-Name+dave
 path = /var/spool/samba/sambashares/srvbackup
 
 [homes]
 browseable = no
 writeable = yes
 
 from an XP professional client, srvbackup is usable but i
 cannot access  my home.
 error dialog shows \\linuxbox\dave is not accessible
 

On my system FileTest joined to a Win2K domain connections
to home work with following setup:

1 - check path for home in getent:
FileTest:~ # getent passwd | grep testuser
testuser:x:11053:10513:testuser:/home/TEST_WIN_DOMAIN/testuser:/bin/false

2 - note valid user parameter:
[homes]
comment = Home Directories
valid users = TEST_WIN_DOMAIN/%S
browseable = No
read only = No

3 - note location of home directory:
/home/TEST_WIN_DOMAIN/testuser

Hope this helps.
Bruce
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] winbind / idmap_rid

2005-02-20 Thread Bruce Hohl
 On Sat, Feb 19, 2005 at 03:42:27PM -1200, Bruce Hohl
  wrote: I am using winbind with the idmap_rid parameter.
  After each time I restart winbind I have to rejoin the
  domain in order for wbinfo -t to succeed.
  User connections also fail.
 
 This is not related to idmap_rid. Could you please try to
 use a netbios-name in the password server parameter and
 try again?
 
 Thanks,
 
 Guenther
 
Guenther,
Adding a netbios-name instead of any IP address for the
password server parameter has corrected the behavior noted
above on both my test and production systems.  Thank you for
this help.  Would it also be better to use a net-bios name
for the wins server parameter?
Bruce
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] winbind / idmap_rid

2005-02-19 Thread Bruce Hohl
Thanks in advance for any help in resolving this issue.
I am experiencing the following issue on both a test and 
production server.  Data from the test server follows:

I am using winbind with the idmap_rid parameter.
After each time I restart winbind I have to rejoin the
domain in order for wbinfo -t to succeed.
User connections also fail.

I am running:
samba-3.0.10-0.1  (SuSE 9.1 Pro)
heimdal-0.6.1rc3-55.9

My smb.conf globals are as follows:
[global]
# general #
workgroup = GROTECOMPANY
realm = GROTECOMPANY.COM
map to guest = Bad User
password server = 192.168.1.201
security = ADS
log level = 1
preferred master = no
local master = no
domain master = no
wins server = 192.168.1.201
ldap ssl = no
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
# winbind 
# IDMAP_RID with Winbind available with 3.0.8:
idmap backend = idmap_rid:GROTECOMPANY=1-2
allow trusted domains = no
##
idmap uid = 1-2
idmap gid = 1-2
winbind separator = /
winbind use default domain = yes
winbind enum users = yes
winbind enum groups = yes
# printing #
printing = cups
printcap name = cups
printer admin = administrator


LOG (log level = 3) MESSAGES FROM wbinfo -t COMMAND AFTER
RESTART OF WINBIND:
==
[2005/02/19 22:12:54, 3]
nsswitch/winbindd_misc.c:winbindd_interface_version(261)
  [ 7251]: request interface version
[2005/02/19 22:12:54, 3]
nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(297)
  [ 7251]: request location of privileged pipe
[2005/02/19 22:12:54, 3]
nsswitch/winbindd_misc.c:winbindd_check_machine_acct(41)
  [ 7251]: check machine account
[2005/02/19 22:12:54, 3]
nsswitch/winbindd_cm.c:cm_get_ipc_userpass(109)
  IPC$ connections done anonymously
[2005/02/19 22:12:54, 3]
libsmb/cliconnect.c:cli_session_setup_spnego(713)
  Doing spnego session setup (blob length=113)
[2005/02/19 22:12:54, 3]
libsmb/cliconnect.c:cli_session_setup_spnego(738)
  got OID=1 2 840 48018 1 2 2
[2005/02/19 22:12:54, 3]
libsmb/cliconnect.c:cli_session_setup_spnego(738)
  got OID=1 2 840 113554 1 2 2
[2005/02/19 22:12:54, 3]
libsmb/cliconnect.c:cli_session_setup_spnego(738)
  got OID=1 2 840 113554 1 2 2 3
[2005/02/19 22:12:54, 3]
libsmb/cliconnect.c:cli_session_setup_spnego(738)
  got OID=1 3 6 1 4 1 311 2 2 10
[2005/02/19 22:12:54, 3]
libsmb/cliconnect.c:cli_session_setup_spnego(745)
  got [EMAIL PROTECTED]
[2005/02/19 22:12:54, 2]
libsmb/cliconnect.c:cli_session_setup_kerberos(538)
  Doing kerberos session setup
[2005/02/19 22:12:54, 3]
libsmb/clikrb5.c:ads_cleanup_expired_creds(319)
  Ticket in ccache[MEMORY:cliconnect] expiration Sun, 20 Feb
2005 08:12:45 GMT
[2005/02/19 22:12:54, 0]
rpc_client/cli_netlogon.c:cli_nt_setup_creds(256)
  cli_nt_setup_creds: request challenge failed
[2005/02/19 22:12:54, 3]
nsswitch/winbindd_cm.c:cm_prepare_connection(384)
  schannel refused - continuing without schannel
(NT_STATUS_INVALID_COMPUTER_NAME)
[2005/02/19 22:12:54, 0]
rpc_client/cli_netlogon.c:cli_nt_setup_creds(256)
  cli_nt_setup_creds: request challenge failed
[2005/02/19 22:12:54, 3]
nsswitch/winbindd_misc.c:winbindd_check_machine_acct(68)
  could not open handle to NETLOGON pipe
[2005/02/19 22:12:54, 2]
nsswitch/winbindd_misc.c:winbindd_check_machine_acct(98)
  Checking the trust account password returned
NT_STATUS_INVALID_COMPUTER_NAME
  
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] winbind question

2005-02-17 Thread Bruce Hohl
After each time I restart winbind I have to rejoin the
domain in order for wbinfo -t to succeed or smbclient
//server/share -U user to succeed.

I am running:
samba-3.0.10-0.1  (SuSE 9.1 Pro)
heimdal-0.6.1rc3-55.9

The following error is returned from wbinfo -t:
FileTest:~ # wbinfo -t
checking the trust secret via RPC calls failed
error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc122)
Could not check secret

I also get a NT_STATUS_INVALID_COMPUTER_NAME error from
smbclient 

The following is written to the log:
/var/log/samba/log.winbindd
[2005/02/17 21:29:24, 0]
rpc_client/cli_netlogon.c:cli_nt_setup_creds(256)
  cli_nt_setup_creds: request challenge failed

Clock skew does not appear to be the cause:
FileTest:~ # net ads info
LDAP server: 192.168.1.201
LDAP server name: win_ads1
Realm: MYCOMPANY.COM
Bind Path: dc=MYCOMPANY,dc=COM
LDAP port: 389
Server time: Thu, 17 Feb 2005 21:32:19 GMT
KDC server: 192.168.1.201
Server time offset: 69

Thanks for any guidance in resolving this issue.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Prints ok, but says Access denied, unable to connect. win2k and samba 2.2.1a

2005-02-13 Thread Bruce Hohl
 Hi,
 
 I had the same problem and solved it by adding 
 
 use client driver = yes
 
 to the [printers] section.
 I'm not quite sure whether this option is available in
 Samba 2.2.1a
 

Loading the printer drivers onto the server will also
eliminate these error messages ... at leaset in version
3.0.9.

However, see the following from man smb.conf:

use client driver (S)

This parameter applies only to Windows NT/2000 clients. It
has no effect on   Windows 95/98/ME clients. When serving a
printer to Windows NT/2000 clients without first installing
a valid printer driver on the Samba host,  the  client will
be required  to  install a local printer driver. From this
point on, the client will treat the print as a local printer
and not a network printer connection.  This is much the same
behavior that will occur when disable spoolss = yes.

The differentiating factor is that under normal
circumstances, the NT/2000 client will attempt to open the
network  printer  using  MS-RPC.  The  problem  is  that
because  the  client  considers the printer to be local, it
will attempt to issue the OpenPrinterEx() call requesting
access rights associated with the  logged  on user.  If the
user possesses local administator rights but not root
privilegde on the Samba host (often the case), the
OpenPrinterEx() call will fail.  The  result is that the
client will now display an Access Denied; Unable to
connect message in the printer queue window (even though
jobs may successfully be printed).

If this parameter is enabled for a printer, then any attempt
to open the  printer with the PRINTER_ACCESS_ADMINISTER
right is mapped to PRINTER_ACCESS_USE instead. Thus allowing
the OpenPrinterEx() call to succeed. This  parameter  MUST 
not  be able enabled on a print share which has valid print
driver installed on the Samba server.

Default: use client driver = no


 Am Freitag, 11. Februar 2005 16:22 schrieb Ainsworth,
  Joshua B.: I have a small Samba 2.2.1a plus Win2k
  workgroup. Samba is running on Redhat
  7.2.
 
  There is a networked laserjet 5000 using a static IP
  which I can print to
  successfuly from the linux box, and from the win2k
  workstations via the queue
  on the linux box.
 
  The weird thing is that, on the win2k worksations, if I
  double click on the
  printer icon the status of the printer is reported as
  Access denied, unable to connect. Yet it works???
 
 https://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] smbprngenpdf documentation?

2005-01-14 Thread Bruce Hohl
I am looking for some documentation or instructions for
setup and use of smbprngenpdf by Windows clients.  Can
anyone point me in the proper direction.  Thanks.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba