[Samba] swat cann't start

[Jimmy]

Hi everyone!
 i used slackware version 12.1 and kernel version 2.6.24.5.
When i upgrade samba to version 3.2.4.
i want to use swat to configure my samba server,
and i got the message "swat cann't load share file libtalloc.so.1:no such file 
or directory" 
How can i soultion thih problme？ thanks
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Samba builtin groups and LDAP

[Loren M. Lang]

I just set up a fresh Samba PDC using OpenLDAP as the passdb.  When I
start smbd, I notice some log messages about failing to create some
builtin groups: Administrators and Users.  Is Samba trying to run a
group add script which I have not setup or to create posixGroups in LDAP
which it does not have permission to do?  I turned up debugging output
and saw that it complained about not getting gids from winbind.  I have
not set up and idmaps as it's only one domain and users exists in both
Windows and Linux.
-- 
Loren M. Lang
[EMAIL PROTECTED]
http://www.alzatex.com/


Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: 10A0 7AE2 DAF5 4780 888A  3FA4 DCEE BB39 7654 DE5B


smime.p7s
Description: S/MIME cryptographic signature
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] heimdal/AD documentation

[Andrei Mikhailovsky]

I have no idea what this guide does as I am not a french speaker. Would
it anable AD to authenticate users against LDAP directory?

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

Re: [Samba] AD to authenticate users against Samba + LDAP

[Guillaume Rousse]

Andrei Mikhailovsky a écrit :

Hi all,

I was wondering if it is possible to make MS Active Directory to
authenticate against Samba + LDAP? I have a working Samba + LDAP setup
in the data centre and need to have MS Active Directory to authenticate
against the userbase which has been already setup on Samba + LDAP.
No way current, as AD relies on Kerberos. You have to wait for samba 4. 
Or alternatively, look at previous post 'Heimdal/AD documentation' if 
you're ready to setup a Kerberos database alongside your LDAP server.


--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] samba member of workgroup

[David C. Rankin]

Fernando wrote:
> Hello,
> 
> I want to setup a samba server as
> a member of a workgroup, for example MYWORKGROUP. I want to share a folder,
> for example /share.
> This share should be available to example.com domain clients only.
> 
> Can someone give me a smb.conf for that?
> 
> Would that do it?
> 
> [global]
> workgroup = MYWORKGROUP
> server string = Samba Server Version %v
> security = domain
> hosts allow = .example.com
> 
> [share]
> comment = Public Stuff
> path = /share
> public = no
> writable = no
> printable = no
> 
> Thank you.

Here is what I have used without any problems for the past 8 years.

[global]
use sendfile = No
workgroup = rb_law
server string = Samba %v
printcap name = cups
load printers = yes
printing = cups
show add printer wizard = no
disable spoolss = yes
log file = /var/log/samba/log.%m
max log size = 100
time server = yes
admin users = thomas
smb ports = 139
hosts allow = 192.168.7. 192.168.6. 192.168.8. 192.168.5. 127.
domain logons = yes
map to guest = bad user
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY
local master = yes
os level = 69
domain master = yes
preferred master = yes
name resolve order = wins lmhosts bcast
wins support = yes
dns proxy = no
usershare allow guests = No
[homes]
comment = Home Directories
browseable = no
writable = yes
[samba]
comment = SambaShares - Pictures, Law
path = /home/samba
valid users = @shoreline, anna
force group = shoreline
admin users = thomas
browseable = Yes
writeable = Yes
inherit permissions = yes


-- 
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] netlogon script not running...(upgrade from 3.0.25b to 3.2.4)

[Adam Williams]

i have the same problem and filled out a bug report 
https://bugzilla.samba.org/show_bug.cgi?id=5627 and it never went 
anywhere.  my only work around was to create a shortcut in the user's 
startup folder to their netlogon script.


Johan Landerholm wrote:

Hi all,

I have been using samba for a very long time and have just upgraded my 
3.0.25b servers to 3.2.4.


I have a bunch of BDC's located in different areas of the country and 
a PDC running at HQ.
I'm using LDAP as the user directory and I replicate the tree to every 
site. Samba looks up users using the replicas.
I also use netlogon scripts to mount drives and set the time when the 
clients log on.


But,
The last machine upgraded (Novell SLES10 x86_64) refuses to "serve" 
the netlogon script anymore.
I have another exactly the same machine and smb.conf that does work, 
but this one does not.
I can see it the log.smbd that when the client logs on, the netlogon 
share is mapped and disconnected, but I can't understand why it 
refuses to run the netlogon script.


I have compared file permissions and configuration files, but I can't 
find any difference.


Can someone give me a hint on how to go on debugging this problem and 
perhaps find the reason ?


Best regards,
Johan Landerholm

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

Re: [Samba] Server Maps by IP but not by Name for Domain Users

[Adam Williams]

add in your [global] section:

msdfs root = yes

restart samba, and then try connecting to your shares by server name again.

Matthew Lind wrote:

Hey all,

I've got an issue with my Samba server.  I can't seem to get file shares
to map using Server Name, but I can get them to map using IP Address. 


Here is my smb.conf:

[global]
  workgroup = ADMIN
  server string = Snap Server
  timestamp logs = yes
  dos filetimes = yes
  dos filemode = yes
  inherit acls = yes
  name cache timeout = 0
  winbind uid = 101-600
  winbind gid = 101-600
  local master = No
  guest account = guest
  map to guest = Never
  unix charset = CP1252
  dos charset = CP850
  allow trusted domains = no
  security = ADS
  disable netbios = no
  password server = *
  encrypt passwords = Yes
  username level = 5
  debug level = 0
  load printers = no
  utmp directory = /var/run
  utmp = yes
  name resolve order = host lmhosts wins bcast
  ldap timeout = 5
  restrict anonymous = 2
  include = /etc/smb.conf.perm
  include = /etc/smb.conf.extra
  include = /etc/smb.conf.dm
  include = /etc/smb_shares.conf

Here is my smb_shares.conf: *Note All shares follow this format and all seem 
affected I am just truncating *
..snip..
[bordway]
path = /shares/bordway
read only = no
comment = 
follow symlinks = no

printable = no
browseable = yes
map acl inherit = yes
create mask = 0777
security mask = 0777
directory mask = 0777
directory security mask = 0777
create mask_ext = 0777
directory mask_ext = 0777
guest ok = No
valid users = \ 
 "admin"   \  
 "ADMIN\bordway" 

write list = \ 
  "admin"   \   
  "ADMIN\bordway"  
..snip..


Here is my smb.conf.perm:
panic action = /usr/bin/backtrace %d > /tmp/segv_samba_%d.out 2>&1
#  root preexec = /usr/local/samba/bin/log_connect.sh '%u' '%m' '%I' '%S'
#  root postexec = /usr/local/samba/bin/log_disconnect.sh '%u' '%m' '%I' '%S'
  username level = 0
 realm = ADMIN.NHTI

smb.conf.dm and smb.conf.extra are empty.

When a client tries to connect using the Server Name this is the error in the 
log:

[2008/10/13 11:51:54, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:51:54, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:51:54, 0] lib/util_sock.c:write_socket_data(388)
  write_socket_data: write failure. Error = Connection reset by peer
[2008/10/13 11:51:54, 0] lib/util_sock.c:write_socket(413)
  write_socket: Error writing 4 bytes to socket 19: ERRNO = Connection reset by 
peer
[2008/10/13 11:51:54, 0] lib/util_sock.c:send_smb(585)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2008/10/13 11:53:00, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:53:01, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:53:01, 0] lib/util_sock.c:write_socket_data(388)
  write_socket_data: write failure. Error = Connection reset by peer
[2008/10/13 11:53:01, 0] lib/util_sock.c:write_socket(413)
  write_socket: Error writing 4 bytes to socket 19: ERRNO = Connection reset by 
peer
[2008/10/13 11:53:01, 0] lib/util_sock.c:send_smb(585)
  Error writing 4 bytes to client. -1. (Connection reset by peer)

On the Windows side if I try by name the user is presented with a Login Box.  
When the credentials are entered the map fails.
If I try with IP no login box is presented and the mapping succeeds.

Things I have tried:

I have tried adding the following to smb.conf (individually and in combination)

smb ports = 139
smb ports = 445
netbios name = admin1

The clients can ping the server by name and the server can ping the clients by 
name.
The clients use the Domain Controller as their DNS server and it can map to the 
server by name.

wbinfo -u and wbinfo -g come back with the correct group and user information.

Any help would be appreciated!

Thanks




  

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

Re: [Samba] Print server communications back to the client during printing

[Gerald (Jerry) Carter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ryan Novosielski wrote:

> I didn't really mean "is there a benefit to supporting this," I meant
> more that if my clients are currently blocking the traffic coming back
> from the server, is there a tangible benefit I could expect from getting
> that fixed (perhaps the "your document has printed" message, or more
> speed, etc.), or is it a minor thing?

Configure the firewall to reject the packets instead of
dropping them to [prevent the lag.  You will probably see some
issues with enumerating print jobs in the Windows print manager.
But tghe jobs should come out just fine.





jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI85DsIR7qMdg1EfYRAk6rAKDtjBtFbLsNUb1emn0WRMVjmbFoJACgnq3z
7ueMc+hiRxpoy+vE2Xk3bIM=
=M1tb
-END PGP SIGNATURE-
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Print server communications back to the client during printing

[Ryan Novosielski]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jeremy Allison wrote:
> On Mon, Oct 13, 2008 at 01:39:30PM -0400, Ryan Novosielski wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jeremy Allison wrote:
>>> On Mon, Oct 13, 2008 at 11:57:45AM -0400, Gerald (Jerry) Carter wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Taylor, Marc wrote:
> Hello All,
>
> I was wondering if anyone knows why a print server needs to talk back on
> the submitting client's ports 139 or 445?
 It's Microsoft's async print change notification protocol.  Jeremy
 had talked about adding a separate timetou for the back channel connect,
 but I don't remember if this was ever done.
>>> Like the man said, it's Microsoft's doing :-). No, we don't have
>>> a separate timeout in spoolss_connect_to_client()
>>> (rpc_server/srv_spoolss_nt.c) but we could add one.
>> How does this actually work in the case of Samba? Does the Samba server
>> attempt to contact the NT machine, and is there a benefit to allowing
>> this to happen?
> 
> We do *exactly* what the Windows server does. Yes, we attemt to contact
> the Windows client, as that's what Windows does. The benefit is it
> correctly implements the Windows printing change-notify protocol.

I didn't really mean "is there a benefit to supporting this," I meant
more that if my clients are currently blocking the traffic coming back
from the server, is there a tangible benefit I could expect from getting
that fixed (perhaps the "your document has printed" message, or more
speed, etc.), or is it a minor thing?

- --
  _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI840cmb+gadEcsb4RAkZNAJ9/zhfK9YErQub6SKB3B2ScZjPDnwCeLOWI
vri44UM1BMR8o+q/yAoYIfU=
=SD5O
-END PGP SIGNATURE-
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Print server communications back to the client during printing

[Jeremy Allison]

On Mon, Oct 13, 2008 at 01:39:30PM -0400, Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Jeremy Allison wrote:
> > On Mon, Oct 13, 2008 at 11:57:45AM -0400, Gerald (Jerry) Carter wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> Taylor, Marc wrote:
> >>> Hello All,
> >>>
> >>> I was wondering if anyone knows why a print server needs to talk back on
> >>> the submitting client's ports 139 or 445?
> >> It's Microsoft's async print change notification protocol.  Jeremy
> >> had talked about adding a separate timetou for the back channel connect,
> >> but I don't remember if this was ever done.
> > 
> > Like the man said, it's Microsoft's doing :-). No, we don't have
> > a separate timeout in spoolss_connect_to_client()
> > (rpc_server/srv_spoolss_nt.c) but we could add one.
> 
> How does this actually work in the case of Samba? Does the Samba server
> attempt to contact the NT machine, and is there a benefit to allowing
> this to happen?

We do *exactly* what the Windows server does. Yes, we attemt to contact
the Windows client, as that's what Windows does. The benefit is it
correctly implements the Windows printing change-notify protocol.

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

Re: [Samba] Print server communications back to the client during printing

[Ryan Novosielski]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jeremy Allison wrote:
> On Mon, Oct 13, 2008 at 11:57:45AM -0400, Gerald (Jerry) Carter wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Taylor, Marc wrote:
>>> Hello All,
>>>
>>> I was wondering if anyone knows why a print server needs to talk back on
>>> the submitting client's ports 139 or 445?
>> It's Microsoft's async print change notification protocol.  Jeremy
>> had talked about adding a separate timetou for the back channel connect,
>> but I don't remember if this was ever done.
> 
> Like the man said, it's Microsoft's doing :-). No, we don't have
> a separate timeout in spoolss_connect_to_client()
> (rpc_server/srv_spoolss_nt.c) but we could add one.

How does this actually work in the case of Samba? Does the Samba server
attempt to contact the NT machine, and is there a benefit to allowing
this to happen?

- --
  _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI84fSmb+gadEcsb4RAofUAJ4xOyWnLtdrj2yI3ZrzDviEWVv8pwCgqweW
GmR+wQR1UJ/DWSW/AG6ut28=
=wWMa
-END PGP SIGNATURE-
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Print server communications back to the client during printing

[Jeremy Allison]

On Mon, Oct 13, 2008 at 11:57:45AM -0400, Gerald (Jerry) Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Taylor, Marc wrote:
> > Hello All,
> > 
> > I was wondering if anyone knows why a print server needs to talk back on
> > the submitting client's ports 139 or 445?
> 
> It's Microsoft's async print change notification protocol.  Jeremy
> had talked about adding a separate timetou for the back channel connect,
> but I don't remember if this was ever done.

Like the man said, it's Microsoft's doing :-). No, we don't have
a separate timeout in spoolss_connect_to_client()
(rpc_server/srv_spoolss_nt.c) but we could add one.

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

[Samba] Server Maps by IP but not by Name for Domain Users

[Matthew Lind]

Hey all,

I've got an issue with my Samba server.  I can't seem to get file shares
to map using Server Name, but I can get them to map using IP Address. 

Here is my smb.conf:

[global]
  workgroup = ADMIN
  server string = Snap Server
  timestamp logs = yes
  dos filetimes = yes
  dos filemode = yes
  inherit acls = yes
  name cache timeout = 0
  winbind uid = 101-600
  winbind gid = 101-600
  local master = No
  guest account = guest
  map to guest = Never
  unix charset = CP1252
  dos charset = CP850
  allow trusted domains = no
  security = ADS
  disable netbios = no
  password server = *
  encrypt passwords = Yes
  username level = 5
  debug level = 0
  load printers = no
  utmp directory = /var/run
  utmp = yes
  name resolve order = host lmhosts wins bcast
  ldap timeout = 5
  restrict anonymous = 2
  include = /etc/smb.conf.perm
  include = /etc/smb.conf.extra
  include = /etc/smb.conf.dm
  include = /etc/smb_shares.conf

Here is my smb_shares.conf: *Note All shares follow this format and all seem 
affected I am just truncating *
..snip..
[bordway]
path = /shares/bordway
read only = no
comment = 
follow symlinks = no
printable = no
browseable = yes
map acl inherit = yes
create mask = 0777
security mask = 0777
directory mask = 0777
directory security mask = 0777
create mask_ext = 0777
directory mask_ext = 0777
guest ok = No
valid users = \ 
 "admin"   \  
 "ADMIN\bordway" 

write list = \ 
  "admin"   \   
  "ADMIN\bordway"  
..snip..

Here is my smb.conf.perm:
panic action = /usr/bin/backtrace %d > /tmp/segv_samba_%d.out 2>&1
#  root preexec = /usr/local/samba/bin/log_connect.sh '%u' '%m' '%I' '%S'
#  root postexec = /usr/local/samba/bin/log_disconnect.sh '%u' '%m' '%I' '%S'
  username level = 0
 realm = ADMIN.NHTI

smb.conf.dm and smb.conf.extra are empty.

When a client tries to connect using the Server Name this is the error in the 
log:

[2008/10/13 11:51:54, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:51:54, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:51:54, 0] lib/util_sock.c:write_socket_data(388)
  write_socket_data: write failure. Error = Connection reset by peer
[2008/10/13 11:51:54, 0] lib/util_sock.c:write_socket(413)
  write_socket: Error writing 4 bytes to socket 19: ERRNO = Connection reset by 
peer
[2008/10/13 11:51:54, 0] lib/util_sock.c:send_smb(585)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2008/10/13 11:53:00, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:53:01, 0] lib/util_sock.c:get_socket_addr(926)
  getpeername failed. Error was Transport endpoint is not connected
[2008/10/13 11:53:01, 0] lib/util_sock.c:write_socket_data(388)
  write_socket_data: write failure. Error = Connection reset by peer
[2008/10/13 11:53:01, 0] lib/util_sock.c:write_socket(413)
  write_socket: Error writing 4 bytes to socket 19: ERRNO = Connection reset by 
peer
[2008/10/13 11:53:01, 0] lib/util_sock.c:send_smb(585)
  Error writing 4 bytes to client. -1. (Connection reset by peer)

On the Windows side if I try by name the user is presented with a Login Box.  
When the credentials are entered the map fails.
If I try with IP no login box is presented and the mapping succeeds.

Things I have tried:

I have tried adding the following to smb.conf (individually and in combination)

smb ports = 139
smb ports = 445
netbios name = admin1

The clients can ping the server by name and the server can ping the clients by 
name.
The clients use the Domain Controller as their DNS server and it can map to the 
server by name.

wbinfo -u and wbinfo -g come back with the correct group and user information.

Any help would be appreciated!

Thanks




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

Re: [Samba] netlogon script not running...(upgrade from 3.0.25b to 3.2.4)

[Ryan Novosielski]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Read the changelog. I think there was a change around 3.0.28 that may be
causing this problem. There are some tricks to variable expansion or
something like that.

Forgive me if I'm wrong, I just seem to remember it myself.

=R

Johan Landerholm wrote:
> Hi all,
> 
> I have been using samba for a very long time and have just upgraded my
> 3.0.25b servers to 3.2.4.
> 
> I have a bunch of BDC's located in different areas of the country and a
> PDC running at HQ.
> I'm using LDAP as the user directory and I replicate the tree to every
> site. Samba looks up users using the replicas.
> I also use netlogon scripts to mount drives and set the time when the
> clients log on.
> 
> But,
> The last machine upgraded (Novell SLES10 x86_64) refuses to "serve" the
> netlogon script anymore.
> I have another exactly the same machine and smb.conf that does work, but
> this one does not.
> I can see it the log.smbd that when the client logs on, the netlogon
> share is mapped and disconnected, but I can't understand why it refuses
> to run the netlogon script.
> 
> I have compared file permissions and configuration files, but I can't
> find any difference.
> 
> Can someone give me a hint on how to go on debugging this problem and
> perhaps find the reason ?
> 
> Best regards,
> Johan Landerholm

- --
  _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI839Mmb+gadEcsb4RAgn4AJ9gU9wfPF237u73tz7pL5CVBojMSACeKEXm
Wtl3UJSPe6Ccf4dvst3tJzg=
=FaUl
-END PGP SIGNATURE-
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Samba + LDAP PDC Vista SP1 logins stopped working

[Andrei Mikhailovsky]

Hi All,

After upgrade to Vista SP1 the logins to Samba + LDAP PDC stopped
working. Looking further at the problem I have identified that the
problem is with the usernames that we have, which are name@.com.
For some reason beyond my understanding, it seems that the if the
username contains a dot "." followed by one or more character, I get the
following error in Vista:

The local Session Manager service failed the logon.
The data area passed to a system call is too small

If the username has no dots "." or the dot is the last character in the
username (for example username. ) the authentication works fine.

Initially I have thought that the problem is is entirely the fault of
SP1, however, I have tried to replicate the same setup on MS Active
directory server 2003 and authentication of the users with exactly the
same name works flawlessly.

I tried to enable debugging mode in Samba, however was not able to see
any error or warning messages, nor do I have anything useful in the
Vista event viewer. I am a little lost and have no idea how to fix this
issue.

Did anyone experience similar problems? Any tips or ideas would be great.

My setup is:

Linux Gentoo
Samba 3.0.32
LDAP 2.3.43

Windows client:
Windows Vista SP1 Business Edition with latest updates.

Many thanks

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

[Samba] AD to authenticate users against Samba + LDAP

[Andrei Mikhailovsky]

Hi all,

I was wondering if it is possible to make MS Active Directory to
authenticate against Samba + LDAP? I have a working Samba + LDAP setup
in the data centre and need to have MS Active Directory to authenticate
against the userbase which has been already setup on Samba + LDAP.

I have seen user guides on how to make samba to authenticate against AD,
but not other way around. Is it possible at all? Are there any useful
guides?

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

Re: [Samba] Print server communications back to the client during printing

[Gerald (Jerry) Carter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Taylor, Marc wrote:
> Hello All,
> 
> I was wondering if anyone knows why a print server needs to talk back on
> the submitting client's ports 139 or 445?

It's Microsoft's async print change notification protocol.  Jeremy
had talked about adding a separate timetou for the back channel connect,
but I don't remember if this was ever done.





cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI82/4IR7qMdg1EfYRAg8tAKDI3xZ9+9ydqksP5kIJO6Te8TxnRwCdEiD2
3l/1K+Ebt95hBYZf0V6z7mk=
=XIcK
-END PGP SIGNATURE-
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Print server communications back to the client during printing

[Taylor, Marc]

Hello All,

I was wondering if anyone knows why a print server needs to talk back on
the submitting client's ports 139 or 445?
 
We are running Samba and we have pretty heavy firewall restrictions on
our clients and we have noticed that interacting with the print server
can seem to have lags in responses (job submission, print options, queue
config, etc).  Using the logging feature of the windows firewall we
noticed the print server trying to talk back to the client's ports
mentioned above.  We also noticed that our Win2k3 server does the same
thing and it isn't obvious as to why.

Besides punching holes in the firewall is there a feature that can be
turned off so that this doesn't happen, particularly in Samba (3.0.28)?

Sorry to show my ignorance of this sort of thing but I am not sure how
to phrase a Google query to get to the bottom of this.

Many thanks.

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

[Samba] heimdal/AD documentation

[Pascal Levy]

as i promise last week, a incomplete documentation about configuring a trust 
beetween a heimdal kdc and a windows AD domain

really sorry for non-french speakers

of course, i'm very interresting in any feedback...


Pascal



 configuration

- le realm Kerberos est DEMO.LOCAL
- le realm du domaine AD est ad.demo.local

La configuration du KDC lui même ne présente pas de difficulté particulière. 
Nous utilisons un KDC Heimdal sur un serveur FreeBSD 6.2. Le service de nom 
de domaine est utilisé pour localiser les services du KDC, rendant la 
configuration des postes clients minimale (utile surtout pour les postes non 
windows). Les enregistrements spécifiques créés pour Kerberos :

 kerberosIN  CNAME   ns0

_kerberos._udp  IN  SRV 01 00 88 kerberos
_kerberos._tcp  IN  SRV 01 00 88 kerberos
_kpasswd._udp   IN  SRV 01 00 464 kerberos
_kerberos-adm._tcp  IN  SRV 01 00 749 kerberos
_kerberos   IN  TXT DEMO.LOCAL

Attention : Kerberos est très sensible à deux choses : la synchronisation 
(nécessité d'utiliser ntp pour synchroniser les horloges des machines 
impliquéees) et la résolution de nom. l'utilisation d'un CNAME pour le 
serveur ne pose pas de problème, mais la résolution inverse (PTR) doit 
absolument être configurée de manière adéquate.

Pour le détail de l'installation du KDC, suivre l'excellent article du 
handbook FreeBSD.
Mise en place de la relation de confiance :

La confiance entre les deux realms Kerberos repose sur un principal partagé 
avec une clef commune.

- côté Windows :
dans Outils d'administrations > Domaines et approbations Active Directory

Sur le domaine AD (ici ad.demo.local) clic droit et propriété, puis onglet 
approbations, cliquer sur nouvelle approbation.

Suivre l'assistant, grosso modo, on peut tout laisser par défaut. Le mot de 
passe choisi est particulièrement important : la sécurité de la relation 
d'approbation repose sur lui... Par contre, il n'aura à être rentré que deux 
fois à la création des clefs et n'a même pas besoin d'être conservé.

- côté Unix :

se connecter à l'application d'administration du realm en faisant par 
exemple :

# kadmin -l

créer la clef de confiance :

kadmin> ank krbtgt/[EMAIL PROTECTED] 

... avec le même mot de passe utilisé sous Windows. Un prinicipal suffit ici, 
puisque l'approbation doit être unilatérale. Toute la difficulté consiste 
dans la gestion catastrophique des types de clefs par Windows. Le plus simple 
consiste à laisser Heimdal créer ses clefs avec les types par défaut et à 
supprimer ensuite celles qui sont en trop pour ne laisser que le minimum. Ce 
que supporte les différentes versions successives de Windows 2000 à 2003 
n'est pas très clair. La seule solution raisonnable, à moins d'être sur de 
son fait est de ne laisser que le type des-cbc-crc.

Pour voir le détail d'un principal et les types de clefs qu'il contient :

 kadmin> get krbtgt/AD.DEMO.LOCAL

regarder la dernière ligne :

 Keytypes(salttype[(salt-value)]): des3-cbc-sha1(pw-salt), des-cbc-md5
(pw-salt), des-cbc-md4(pw-salt), des-cbc-crc(pw-salt)

supprimer les types qui nous embêtent (enfin, qui embêtent l'AD...) avec par 
exemple :

  kadmin> del_enctype krbtgt/AD.DEMO.LOCAL des3-cbc-sha1

etc, jusqu'à ne garder plus que

 Keytypes(salttype[(salt-value)]): des-cbc-crc(pw-salt)

 La relation de confiance devrait maintenant être fonctionnelle.
configuration des postes Windows :

Windows devrait savoir (dans certaines versions seulement...) utiliser DNS 
pour retrouver le KDC (enregistrement SRV) mais de toute façon pas le realm 
(enregistrement TXT). Il faut donc intervenir sur chaque machine, à commencer 
par le pdc lui même avec un outil qui se trouve dans les supports tools de 
Windows 2003 serveur, à trouver sur le CD et installer séparément.  Ensuite :

ksetup /addkdc DEMO.LOCAL kerberos.bsg.local

mappage des utilisateurs

Pour que les utilisateurs puissent accéder aux ressources du domaine, l'AD 
doit pouvoir trouver un compte qui corresponde. Il faut réaliser un mappage 
entre les principals Kerberos et les comptes du domaine. Le mappage peut être 
réalisé globalement avec 

ksetup /mapuser * *

ou par utilisateur dans l'interface de gestion des comptes de l'AD. Activer 
les "fonctions avancées" et faire un clic droit sur l'utilisateur et "mappage 
des utilisateurs"

on devrait maintenant pouvoir se logger sur un poste du domaine en utilisant 
le domaine Kerberos...
quelques outils utiles...

sur unix :

acquérir un ticket initial sur un KDC

# kinit [EMAIL PROTECTED]

 lister les tickets kerberos avec le détails (notamment les fameux 
enctypes...)

# klist -v

 se connecter sur un partage en utilisant le ticket kerberos :

# smbclient -k //serveur/partage

on peut aussi accèder au ldap du contrôlleur de domaine :

ldapsearch -H ldap://dc.ad.bsg.local  -b "dc=ad,dc=bsg,dc=local" 

 sur Windows :

il faut installer le ressource Kit Windows (à télécharger sur microsoft.com) 
pour utiliser klist.exe et k

[Samba] Write/Modify issues

[Kristian Davies]

I'm having problems with one share.  It's mounting a directory on an
isilon over NFS.  I've re-created the setup on the same machine where
the data is and that works fine, it's just the existing share gives
trouble.

I can create a file, but not rename and sometimes not delete.  Also
saving file from say photoshop result in two empty files being created
one with the proper filename and another with a temp one, then error
with "the file is write protected/disk full".

Below is a log file snippet with "fill_share_mode_lock failed", could
that be an indicator?

I'm using 3.2.4, and I tried 3.0.32.  Our old/current setup works
fine 3.0.20.

Cheers,
Kristian

smb.conf

[global]
unix charset = LOCALE
workgroup = ABC
realm = AD.ABC.LOCAL
password server = *
netbios name = samba
server string = SAMBA
security = ADS
encrypt passwords = yes
preferred master = no
local master = no
os level = 33
log level = 10
syslog = 1
log file = /var/log/samba/%m
max log size = 5dap ssl = no
idmap uid = 950-2
idmap gid = 600-2
template shell = /bin/bash
winbind separator = +
winbind use default domain = Yes
socket options = TCP_NODELAY
logon home = \\samba\%U

[share]
read only = No
create mask = 0664
directory mask = 0775
blocking locks = No
locking = No
oplocks = No
level2 oplocks = No
posix locking = No
strict locking = No
case sensitive = yes


[2008/10/13 13:35:28,  5] smbd/filename.c:unix_convert(149)
  unix_convert called on file "art_dept/allRender/New Text Document.txt"
[2008/10/13 13:35:28,  5] smbd/filename.c:unix_convert(290)
  conversion finished art_dept/allRender/New Text Document.txt ->
art_dept/allRender/New Text Document.txt
[2008/10/13 13:35:28,  5] smbd/trans2.c:call_trans2findfirst(2007)
  dir=art_dept/allRender, mask = New Text Document.txt
[2008/10/13 13:35:28,  5] smbd/dir.c:dptr_create(402)
  dptr_create dir=art_dept/allRender
[2008/10/13 13:35:28,  3] smbd/dir.c:dptr_create(520)
  creating new dirptr 256 for path art_dept/allRender, expect_close = 1
[2008/10/13 13:35:28,  4] smbd/trans2.c:call_trans2findfirst(2074)
  dptr_num is 256, wcard = New Text Document.txt, attr = 22
[2008/10/13 13:35:28,  8] smbd/trans2.c:call_trans2findfirst(2079)
  dirpath= dontdescend=<>
[2008/10/13 13:35:28,  8] smbd/trans2.c:get_lanman2_dir_entry(1312)
  get_lanman2_dir_entry:readdir on dirptr 0x861cd10 now at offset -1
[2008/10/13 13:35:28,  8] smbd/dosmode.c:dos_mode(354)
  dos_mode: art_dept/allRender/New Text Document.txt
[2008/10/13 13:35:28,  8] smbd/dosmode.c:dos_mode_from_sbuf(170)
  dos_mode_from_sbuf returning
[2008/10/13 13:35:28,  8] smbd/dosmode.c:dos_mode(394)
  dos_mode returning
[2008/10/13 13:35:28,  3] locking/locking.c:fetch_share_mode_unlocked(857)
  fill_share_mode_lock failed
[2008/10/13 13:35:28,  5] smbd/trans2.c:get_lanman2_dir_entry(1443)
  get_lanman2_dir_entry: found art_dept/allRender/New Text
Document.txt fname=New Text Document.txt
[2008/10/13 13:35:28, 10] smbd/trans2.c:get_lanman2_dir_entry(1592)
  get_lanman2_dir_entry: SMB_FIND_FILE_BOTH_DIRECTORY_INFO
[2008/10/13 13:35:28, 10] smbd/mangle_hash2.c:hash2_name_to_8_3(609)
  hash2_name_to_8_3: New Text Document.txt -> 124541D5 -> N52HZ2~T.TXT (cache=1)
[2008/10/13 13:35:28,  5] smbd/trans2.c:call_trans2findfirst(2135)
  call_trans2findfirst - (2) closing dptr_num 256
[2008/10/13 13:35:28,  4] smbd/dir.c:dptr_close_internal(251)
  closing dptr key 256
[2008/10/13 13:35:28,  9] smbd/trans2.c:send_trans2_replies(833)
  t2_rep: params_sent_thistime = 10, data_sent_thistime = 136,
useable_space = 131010
[2008/10/13 13:35:28,  9] smbd/trans2.c:send_trans2_replies(835)
  t2_rep: params_to_send = 10, data_to_send = 136, paramsize = 10,
datasize = 136
[2008/10/13 13:35:28,  5] lib/util.c:show_msg(642)


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

Re: [Samba] samba+cups failure - no printers in the share list

[Martin Zielinski]

Hi!

Self compiled Samba?
Does "ldd smbd" has a link to libcups?
If you have a smbd that is linked to libcups and cups is running, it 
will work!


Only reason why it wouldn't could be access rights in your cups 
configuration.


After you verified, that libcups is used, it might be a good idea to 
increase the log level of samba and cups and examine the logfiles. They 
might contain the information you need.


Bye,

Martin


LÉVAI Dániel schrieb:

LÉVAI Dániel wrote:

Hi!

It seems my samba and cups won't communicate with each other. I've 
configured samba to load the printers from cups:

load printers = yes
printing = cups
printcap name = cups

[printers]
comment = All Printers
path = /var/spool/samba
printable = yes
public = no
read only = yes
create mode = 0700
valid users = @digiszfv
printer admin = daniell

# lpstat -t
scheduler is running
no system default destination
device for hp_lj_p2015n: socket://192.168.1.66
hp_lj_p2015n accepting requests since 2008. okt. 10., p?ek, 08.49.44 CEST
printer hp_lj_p2015n is idle.  enabled since 2008. okt. 10., p?ek, 
08.49.44 CEST


Despite all this, samba fails to advertise the printer:
# smbclient -U daniell -L FILESERVER
Enter daniell's password:
Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3]

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
ugyfelszolgalat Disk  Ugyfélszolgálat
adminisztrator  Disk  Adminisztrátorok
optikus Disk  Szemészet
IPC$IPC   IPC Service (Samba (fileserver))
daniell Disk  Home Directories
Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3]

What am I missing? Any help would be appreciated.

What this post is missing is some more info I think.
Samba is 3.2.3
Cups is 1.3.8
OS is a Debian testing
Kernel is linux kernel 2.6.24

The printers doesn't show on Linux nor on Win.
On the Cups www admin page, I can print out a test page, so the printer 
is usable.
The problem is with the link between cups and samba. Can't seem to 
figure or find out what is it, though.


Thanks in advance!
Daniel




--
Martin Zielinski[EMAIL PROTECTED]   
Softwareentwicklung T +49 (0)521 94226 76   

SEH Computertechnik GmbHwww.seh.de

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

[Samba] Cluster: node to node switching

[Aleksander Gudalo]

Hi *,

I use samba 3.2.3 actually and have problems to switch between two nodes 
in a cluster in an active directory environment. I know of CTDB but I 
want to keep it simple and so I use a shared folder for the .tdb files.
But it does not work since samba 3.2 anymore. After switching from one 
node to another I have to delete the .tdb files and join again to the 
domain to have access to samba.

What I'm doing wrong here?

Thanks and regards,
Aleksander

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

Re: [Samba] samba+cups failure - no printers in the share list

[LÉVAI Dániel]

LÉVAI Dániel wrote:

Hi!

It seems my samba and cups won't communicate with each other. I've 
configured samba to load the printers from cups:

load printers = yes
printing = cups
printcap name = cups

[printers]
comment = All Printers
path = /var/spool/samba
printable = yes
public = no
read only = yes
create mode = 0700
valid users = @digiszfv
printer admin = daniell

# lpstat -t
scheduler is running
no system default destination
device for hp_lj_p2015n: socket://192.168.1.66
hp_lj_p2015n accepting requests since 2008. okt. 10., p?ek, 08.49.44 CEST
printer hp_lj_p2015n is idle.  enabled since 2008. okt. 10., p?ek, 
08.49.44 CEST


Despite all this, samba fails to advertise the printer:
# smbclient -U daniell -L FILESERVER
Enter daniell's password:
Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3]

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
ugyfelszolgalat Disk  Ugyfélszolgálat
adminisztrator  Disk  Adminisztrátorok
optikus Disk  Szemészet
IPC$IPC   IPC Service (Samba (fileserver))
daniell Disk  Home Directories
Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3]

What am I missing? Any help would be appreciated.

What this post is missing is some more info I think.
Samba is 3.2.3
Cups is 1.3.8
OS is a Debian testing
Kernel is linux kernel 2.6.24

The printers doesn't show on Linux nor on Win.
On the Cups www admin page, I can print out a test page, so the printer 
is usable.
The problem is with the link between cups and samba. Can't seem to 
figure or find out what is it, though.


Thanks in advance!
Daniel

--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412  2D83 1373 917A 4AC0 A4B1
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] netlogon script not running...(upgrade from 3.0.25b to 3.2.4)

[Johan Landerholm]

Hi all,

I have been using samba for a very long time and have just upgraded my 
3.0.25b servers to 3.2.4.


I have a bunch of BDC's located in different areas of the country and a 
PDC running at HQ.
I'm using LDAP as the user directory and I replicate the tree to every 
site. Samba looks up users using the replicas.
I also use netlogon scripts to mount drives and set the time when the 
clients log on.


But,
The last machine upgraded (Novell SLES10 x86_64) refuses to "serve" the 
netlogon script anymore.
I have another exactly the same machine and smb.conf that does work, but 
this one does not.
I can see it the log.smbd that when the client logs on, the netlogon 
share is mapped and disconnected, but I can't understand why it refuses 
to run the netlogon script.


I have compared file permissions and configuration files, but I can't 
find any difference.


Can someone give me a hint on how to go on debugging this problem and 
perhaps find the reason ?


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

[Samba] samba member of workgroup

[Fernando]

Hello,

I want to setup a samba server as
a member of a workgroup, for example MYWORKGROUP. I want to share a folder,
for example /share.
This share should be available to example.com domain clients only.

Can someone give me a smb.conf for that?

Would that do it?

[global]
workgroup = MYWORKGROUP
server string = Samba Server Version %v
security = domain
hosts allow = .example.com

[share]
comment = Public Stuff
path = /share
public = no
writable = no
printable = no

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

Re: [Samba] Compile help for Solaris 10 x86, samba 3.0.28a deficient?

[Mike Gallamore]

Sin = Solaris I thought you knew :-)

I've been a Solaris user for 10 years and an admin for 3 and I can  
tell you I'm still clueless with some things. For example I had a  
system that I moved and plugged into a different fiber connect. Well  
Sun's BootProm (there version of POST) helpfully changed the  
configuration of the FC card from 1000 full to autonegotiate. Funny  
thing really autonegotiate doesn't work in Solaris unless the other  
side is set to auto too. Makes sense doesn't it :-) Man I was  
scratching my head for 3 hours with a Sun engineer on the phone  
because an identical workstation (just different software installed)  
was at the new location and working fine, all of a sudden both  
wouldn't work. Anyways Solaris is rock solid just don't touch it  
unless you have a day to spare.

On Oct 12, 2008, at 1:58 PM, Dennis Clarke wrote:




On Sunday 12 October 2008 07:55:01 Jake Carroll wrote:

I sort of hoped that somebody would release pre-built binaries for  
Sol

10 x86, unfortunately, all I can find on samba.org is a long way out
of date SPARC binary of 3.0.23.


There are Blastwave x86 packages out there. If you have searched  
the old

posts
on this list, you should have found that maintainer (Dennis Clarke)  
even

posted links here on the list.

Here you go:

Samba 3.0.31:
http://www.blastwave.org/testing/samba-3.0.31,REV=2008.08.22-SunOS5.8-i386-CSW.pkg.bz2

Samba 3.2.2:
http://www.blastwave.org/testing/samba-3.2.2,REV=2008.08.22-SunOS5.8-i386-CSW.pkg.gz

I don't know if the links are still functional.



They function .. always have .. always will .. until we release them  
to

all the mirrors.

The poor man should work with me .. sounds like we have both worked in
lonely miserable long nights and days and wondered why we were being
punished, what sins had we committed that we deserved this.

yes .. it is that bad.

Dennis


--
To unsubscribe from this list go to the following URL and read the
instructions:  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] samba+cups failure - no printers in the share list

[LÉVAI Dániel]

Hi!

It seems my samba and cups won't communicate with each other. I've 
configured samba to load the printers from cups:

load printers = yes
printing = cups
printcap name = cups

[printers]
comment = All Printers
path = /var/spool/samba
printable = yes
public = no
read only = yes
create mode = 0700
valid users = @digiszfv
printer admin = daniell

# lpstat -t
scheduler is running
no system default destination
device for hp_lj_p2015n: socket://192.168.1.66
hp_lj_p2015n accepting requests since 2008. okt. 10., p?ek, 08.49.44 CEST
printer hp_lj_p2015n is idle.  enabled since 2008. okt. 10., p?ek, 
08.49.44 CEST


Despite all this, samba fails to advertise the printer:
# smbclient -U daniell -L FILESERVER
Enter daniell's password:
Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3]

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
ugyfelszolgalat Disk  Ugyfélszolgálat
adminisztrator  Disk  Adminisztrátorok
optikus Disk  Szemészet
IPC$IPC   IPC Service (Samba (fileserver))
daniell Disk  Home Directories
Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3]

What am I missing? Any help would be appreciated.

Thanks!

Daniel

--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412  2D83 1373 917A 4AC0 A4B1
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba