Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-11-11 Thread Ayo Adeyeri 
I would like to thank everyone who assisted me with this problem.  It turns out 
that the problem was caused by the fact that we were running selinux on the 
server.  Once it was disabled the share was accessible.

Thanks
Ayo

-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On 
Behalf Of Ayo Adeyeri
Sent: Thursday, November 11, 2010 9:37 AM
To: John Drescher; samba
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Thanks John,

I just removed the "." , changed the workgroup name to covecapcom but I am 
still getting the same errors in the log file when I attempt to connect to 
either of the shares from a windows client.

Thanks,
Ayo Adeyeri


-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, November 11, 2010 9:30 AM
To: Ayo Adeyeri; samba
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Network names with a . in them are not supported. Well unless you are
talking about an ads realm.

John

This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer.  InfoHedge 
disclaims all responsibility from and accepts no liability  whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-11-11 Thread John Drescher 
On Thu, Nov 11, 2010 at 9:36 AM, Ayo Adeyeri  wrote:
> Thanks John,
>
> I just removed the "." , changed the workgroup name to covecapcom but I am 
> still getting the same errors in the log file when I attempt to connect to 
> either of the shares from a windows client.
>

Are the windows clients windows 7?

Also share level security is being discouraged for some time.

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

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-11-11 Thread Ayo Adeyeri 
Thanks John,

I just removed the "." , changed the workgroup name to covecapcom but I am 
still getting the same errors in the log file when I attempt to connect to 
either of the shares from a windows client.

Thanks,
Ayo Adeyeri


-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, November 11, 2010 9:30 AM
To: Ayo Adeyeri; samba
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Network names with a . in them are not supported. Well unless you are
talking about an ads realm.

John

This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer.  InfoHedge 
disclaims all responsibility from and accepts no liability  whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-11-11 Thread John Drescher 
Network names with a . in them are not supported. Well unless you are
talking about an ads realm.

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

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-11-11 Thread Ayo Adeyeri 
Bump

-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On 
Behalf Of Ayo Adeyeri
Sent: Wednesday, November 10, 2010 7:17 PM
To: samba@lists.samba.org
Subject: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Let me start off by apologizing for this rambling post.  I have been working on 
this problem all day and have not gotten anywhere.
This is my first time working with samba and I have been tasked to set up a 
share that does not require a password for access.  I have been tinkering with 
the configuration file but I cannot get it to work.  Here is my current 
smb.conf file that I have:

global]
security = share
workgroup = somedomain.com
guest account = murex
log file = /var/log/samba/%m.log


[Murex]
comment = Murex pickup
path = /apps/murex/pickup
writable = yes
read only = no
guest ok = yes


[testdir]
comment = Troubleshooting area
path = /sambatest
writable = yes
read only = no
guest ok = yes
guest only = yes

When I try to access it either of the shares (Murex or testdir) using 
smbclient, I get the following:
# smbclient //localhost/murex
Password:
Domain=[SOMEDOMAIN.COM] OS=[Unix] Server=[Samba 3.0.28-0.el5.8]
Server not using user level security and no password supplied.
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
#
Not sure why it is stating that no password was supplied because I entered a 
password.  I tried both the root password since that is what I was logged in as 
and the password for the user murex.  The murex user is a valid unix account.  
I also created a samba password for the murex user (I used smbpasswd -a murex). 
 This was done recently but it did not change anything.

I can see the shares from our windows clients but when I try and open up a 
share (by double clicking on it) or map a drive to the share I get the 
following errors in the log files:
[2010/11/10 18:49:35, 0] smbd/service.c:make_connection_snum(1003)
  '/apps/murex/pickup' does not exist or permission denied when connecting to 
[Murex] Error was Permission denied
[2010/11/10 18:49:36, 0] smbd/service.c:make_connection_snum(1003)
  '/sambatest' does not exist or permission denied when connecting to [testdir] 
Error was Permission denied

I also see these same errors in the log files when I run the smbclient command 
from above.  The unix permissions on these directories are set at 777.

This is driving me nuts because I think it has got be a pretty minor 
configuration error but I can't figure out what it is.  Does anyone have any 
ideas of what I am missing or doing wrong?

Thanks,
Ayo Adeyeri
InfoHedge Technologies LLC
747 Third Avenue, 4th Floor, New York, NY 10017
ayo.adey...@infohedge.net<mailto:ayo.adey...@infohedge.net>
Office: (212) 531-5835



This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer. InfoHedge 
disclaims all responsibility from and accepts no liability whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer.  InfoHedge 
disclaims all responsibility from and accepts no liability  whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-11-10 Thread Ayo Adeyeri 
Let me start off by apologizing for this rambling post.  I have been working on 
this problem all day and have not gotten anywhere.
This is my first time working with samba and I have been tasked to set up a 
share that does not require a password for access.  I have been tinkering with 
the configuration file but I cannot get it to work.  Here is my current 
smb.conf file that I have:

global]
security = share
workgroup = somedomain.com
guest account = murex
log file = /var/log/samba/%m.log


[Murex]
comment = Murex pickup
path = /apps/murex/pickup
writable = yes
read only = no
guest ok = yes


[testdir]
comment = Troubleshooting area
path = /sambatest
writable = yes
read only = no
guest ok = yes
guest only = yes

When I try to access it either of the shares (Murex or testdir) using 
smbclient, I get the following:
# smbclient //localhost/murex
Password:
Domain=[SOMEDOMAIN.COM] OS=[Unix] Server=[Samba 3.0.28-0.el5.8]
Server not using user level security and no password supplied.
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
#
Not sure why it is stating that no password was supplied because I entered a 
password.  I tried both the root password since that is what I was logged in as 
and the password for the user murex.  The murex user is a valid unix account.  
I also created a samba password for the murex user (I used smbpasswd -a murex). 
 This was done recently but it did not change anything.

I can see the shares from our windows clients but when I try and open up a 
share (by double clicking on it) or map a drive to the share I get the 
following errors in the log files:
[2010/11/10 18:49:35, 0] smbd/service.c:make_connection_snum(1003)
  '/apps/murex/pickup' does not exist or permission denied when connecting to 
[Murex] Error was Permission denied
[2010/11/10 18:49:36, 0] smbd/service.c:make_connection_snum(1003)
  '/sambatest' does not exist or permission denied when connecting to [testdir] 
Error was Permission denied

I also see these same errors in the log files when I run the smbclient command 
from above.  The unix permissions on these directories are set at 777.

This is driving me nuts because I think it has got be a pretty minor 
configuration error but I can't figure out what it is.  Does anyone have any 
ideas of what I am missing or doing wrong?

Thanks,
Ayo Adeyeri
InfoHedge Technologies LLC
747 Third Avenue, 4th Floor, New York, NY 10017
ayo.adey...@infohedge.net
Office: (212) 531-5835



This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer. InfoHedge 
disclaims all responsibility from and accepts no liability whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2010-07-12 Thread murat can tuna 


Hi all,

I have deleted and reinstalled samba 3.4.0 and then I got a failure at starting 
samba .I guess that was because of lacking of smb.conf ( I have deleted it 
manually and it didn't install it back)
And I have decided to install samba4 which gave me also the same failure so I 
have again installed samba 3.4.0 and I found out an smb.conf file from 
/usr/share/doc/samba-doc/examples/smb.conf.default.gz
then I copied it into /etc/samba afterwards I didn't get the same failure but 
whenever I try  smbclient -L localhost -U% I get the following error

Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.0.0alpha9-GIT-27087e6]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

I guess "Samba 4.0.0alpha9-GIT-27087e6" explains there are still some samba4 
files that effects the system but I have deleted it. Can you please help me?

Thanks in Advance

Murat Can Tuna
  
_
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2009-12-28 Thread Dominic Gamble 
Hi Rob,

After a reboot, everything works (both the /test share and the /tmp share,
and it now shows the files in them). It doesn't make any sense, but THANK
YOU!

I used chkconfig to ensure that both smb and ldap started at runlevels 3 and
5, and then rebooted.

I don't know how many times I restarted smb and slapd, and I don't quite
understand why a full reboot was required, but there you go!

Best regards,
Dominic.

-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org]
On Behalf Of Rob Townley
Sent: Tuesday, 29 December 2009 4:45 AM
To: samba@lists.samba.org
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

On Mon, Dec 28, 2009 at 4:03 AM, Michael Adam  wrote:
> Hi Dominic,
>
> Dominic Gamble wrote:
>> Hi,
>>
>> I can't get access to any shares when running "smbclient //DUCK/test -U
>> Dominic". I'm getting the message:
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> I'm pretty sure it's authenticating properly as it says "session setup
ok"
>> in the debug output. If I enter the wrong password I get:
>> "session setup failed: NT_STATUS_LOGON_FAILURE"
>
> This is correct.

Starting from a fresh boot up, try to use the /test share first, does it
work?
Does /tmp then fail?
If so, look under /var/cache/samba/

i don't remember exactly what i came across the
NT_STATUS_BAD_NETWORK_NAME error on CentOS 5.4 and what i did to fix
it, but do remember it wasn't what i expected.

>
>> I'm running CentOS 5.4 with the following samba packages
>>
>> samba-common-3.0.33-3.15.el5_4.1
>> samba-3.0.33-3.15.el5_4.1
>> samba-swat-3.0.33-3.15.el5_4.1
>> samba-client-3.0.33-3.15.el5_4.1
>>
>> My samba setup uses LDAP for authentication. All logging seems to
indicate
>> that authentication and LDAP is working well.
>>
>> My /etc/samba/smb.conf was generated with SWAT and has the following
shares:
>>
>> [tmp]
>>         comment = temporary files
>>         path = /tmp
>>         hosts allow =
>>         hosts deny =
>>
>> [test]
>>         comment = test files
>>         path = /test
>>         hosts allow =
>>         hosts deny =
>>
>>
>> Both shares contain a file called myfile.txt.
>>
>> When I connect to the "tmp" share, I don't get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:
>>
>> [r...@duck cache]# smbclient //DUCK/tmp -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> smb: \> ls
>>   .                                   D        0  Mon Dec 28 04:02:13
2009
>>   ..                                  D        0  Sun Dec 27 21:16:53
2009
>>
>>                 36224 blocks of size 8388608. 34082 blocks available
>> smb: \>
>>
>> When I connect to the "test" share I get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME":
>> [r...@duck cache]# smbclient //DUCK/test -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> The permissions on the /tmp and /test folders are the same:
>>
>> drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
>> drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp
>>
>> There are no complex acls on them either:
>>
>> [r...@duck /]# getfacl tmp
>> # file: tmp
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> [r...@duck /]# getfacl test
>> # file: test
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> I've tried getting more debug info by setting log levels to 10 in both
>> smb.conf and using the -d10 parameter on the command line, but it gives
me
>> nothing useful in the logs or in the output.
>>
>> I've been through 'The Samba Checklist'
>>
(http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
>> and had no other problems.
>>
>> Here is the rest of my smb.conf:
>>
>> [global]
>>         workgroup = ORANDA
>>         server string = Duck
>>         passdb backend = ldapsam:ldap://localhost/
>>         pam password change = Yes
>>         passwd program = /usr/sbin/smbldap-passwd %u
>>         passwd chat = *New*password* %n\n *Retype*new*password* %n\n
>> *all*authentication*tokens*updated*
>>         unix password sync = Yes
>&g

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2009-12-28 Thread Rob Townley 
On Mon, Dec 28, 2009 at 4:03 AM, Michael Adam  wrote:
> Hi Dominic,
>
> Dominic Gamble wrote:
>> Hi,
>>
>> I can't get access to any shares when running "smbclient //DUCK/test -U
>> Dominic". I'm getting the message:
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> I'm pretty sure it's authenticating properly as it says "session setup ok"
>> in the debug output. If I enter the wrong password I get:
>> "session setup failed: NT_STATUS_LOGON_FAILURE"
>
> This is correct.

Starting from a fresh boot up, try to use the /test share first, does it work?
Does /tmp then fail?
If so, look under /var/cache/samba/

i don't remember exactly what i came across the
NT_STATUS_BAD_NETWORK_NAME error on CentOS 5.4 and what i did to fix
it, but do remember it wasn't what i expected.

>
>> I'm running CentOS 5.4 with the following samba packages
>>
>> samba-common-3.0.33-3.15.el5_4.1
>> samba-3.0.33-3.15.el5_4.1
>> samba-swat-3.0.33-3.15.el5_4.1
>> samba-client-3.0.33-3.15.el5_4.1
>>
>> My samba setup uses LDAP for authentication. All logging seems to indicate
>> that authentication and LDAP is working well.
>>
>> My /etc/samba/smb.conf was generated with SWAT and has the following shares:
>>
>> [tmp]
>>         comment = temporary files
>>         path = /tmp
>>         hosts allow =
>>         hosts deny =
>>
>> [test]
>>         comment = test files
>>         path = /test
>>         hosts allow =
>>         hosts deny =
>>
>>
>> Both shares contain a file called myfile.txt.
>>
>> When I connect to the "tmp" share, I don't get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:
>>
>> [r...@duck cache]# smbclient //DUCK/tmp -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> smb: \> ls
>>   .                                   D        0  Mon Dec 28 04:02:13 2009
>>   ..                                  D        0  Sun Dec 27 21:16:53 2009
>>
>>                 36224 blocks of size 8388608. 34082 blocks available
>> smb: \>
>>
>> When I connect to the "test" share I get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME":
>> [r...@duck cache]# smbclient //DUCK/test -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> The permissions on the /tmp and /test folders are the same:
>>
>> drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
>> drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp
>>
>> There are no complex acls on them either:
>>
>> [r...@duck /]# getfacl tmp
>> # file: tmp
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> [r...@duck /]# getfacl test
>> # file: test
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> I've tried getting more debug info by setting log levels to 10 in both
>> smb.conf and using the -d10 parameter on the command line, but it gives me
>> nothing useful in the logs or in the output.
>>
>> I've been through 'The Samba Checklist'
>> (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
>> and had no other problems.
>>
>> Here is the rest of my smb.conf:
>>
>> [global]
>>         workgroup = ORANDA
>>         server string = Duck
>>         passdb backend = ldapsam:ldap://localhost/
>>         pam password change = Yes
>>         passwd program = /usr/sbin/smbldap-passwd %u
>>         passwd chat = *New*password* %n\n *Retype*new*password* %n\n
>> *all*authentication*tokens*updated*
>>         unix password sync = Yes
>>         log level = 10
>>         log file = /var/log/samba/log.%m
>>         load printers = No
>>         printcap name = /dev/null
>>         disable spoolss = Yes
>>         add user script = /usr/sbin/smbldap-useradd -m "%u"
>>         delete user script = /usr/sbin/smbldap-userdel "%u"
>>         add group script = /usr/sbin/smbldap-groupadd -p "%g"
>>         delete group script = /usr/sbin/smbldap-groupdel "%g"
>>         add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
>>         delete user from group script = /usr/sbin/smbldap-groupmod -x "%u"
>> "%g"
>>         set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
>>         add machine script = /usr/sbin/smbldap-useradd -w "%u"
>>         logon script = login.cmd
>>         logon path = \\%N\profiles\%U
>>         logon drive = H:
>>         domain logons = Yes
>>         os level = 127
>>         wins support = Yes
>>         ldap admin dn = cn=admin,dc=oranda,dc=internal
>>         ldap delete dn = Yes
>>         ldap group suffix = ou=Group
>>         ldap idmap suffix = ou=Idmap
>>         ldap machine suffix = ou=Computers
>>         ldap passwd sync = Yes
>>         ldap suffix = dc=oranda,dc=internal
>>         ldap user suffix = ou=People
>>         panic action = /usr/share/samba/panic-action %d
>>         admin users = dominic
>>         hosts allow = 192.168.10., 127.
>>         hosts deny = ALL
>>         printing = bsd
>>      

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2009-12-28 Thread Michael Adam 
Hi Dominic,

Dominic Gamble wrote:
> Hi,
> 
> I can't get access to any shares when running "smbclient //DUCK/test -U
> Dominic". I'm getting the message:
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> 
> I'm pretty sure it's authenticating properly as it says "session setup ok"
> in the debug output. If I enter the wrong password I get:
> "session setup failed: NT_STATUS_LOGON_FAILURE"

This is correct.

> I'm running CentOS 5.4 with the following samba packages
> 
> samba-common-3.0.33-3.15.el5_4.1
> samba-3.0.33-3.15.el5_4.1
> samba-swat-3.0.33-3.15.el5_4.1
> samba-client-3.0.33-3.15.el5_4.1
> 
> My samba setup uses LDAP for authentication. All logging seems to indicate
> that authentication and LDAP is working well.
> 
> My /etc/samba/smb.conf was generated with SWAT and has the following shares:
> 
> [tmp]
> comment = temporary files
> path = /tmp
> hosts allow =
> hosts deny =
> 
> [test]
> comment = test files
> path = /test
> hosts allow =
> hosts deny =
> 
> 
> Both shares contain a file called myfile.txt.
> 
> When I connect to the "tmp" share, I don't get the "tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:
> 
> [r...@duck cache]# smbclient //DUCK/tmp -U dominic
> Password:
> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
> smb: \> ls
>   .   D0  Mon Dec 28 04:02:13 2009
>   ..  D0  Sun Dec 27 21:16:53 2009
> 
> 36224 blocks of size 8388608. 34082 blocks available
> smb: \>
> 
> When I connect to the "test" share I get the "tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME":
> [r...@duck cache]# smbclient //DUCK/test -U dominic
> Password:
> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> 
> The permissions on the /tmp and /test folders are the same:
> 
> drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
> drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp
> 
> There are no complex acls on them either:
> 
> [r...@duck /]# getfacl tmp
> # file: tmp
> # owner: root
> # group: root
> user::rwx
> group::rwx
> other::rwx
> 
> [r...@duck /]# getfacl test
> # file: test
> # owner: root
> # group: root
> user::rwx
> group::rwx
> other::rwx
> 
> I've tried getting more debug info by setting log levels to 10 in both
> smb.conf and using the -d10 parameter on the command line, but it gives me
> nothing useful in the logs or in the output.
> 
> I've been through 'The Samba Checklist'
> (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
> and had no other problems.
> 
> Here is the rest of my smb.conf:
> 
> [global]
> workgroup = ORANDA
> server string = Duck
> passdb backend = ldapsam:ldap://localhost/
> pam password change = Yes
> passwd program = /usr/sbin/smbldap-passwd %u
> passwd chat = *New*password* %n\n *Retype*new*password* %n\n
> *all*authentication*tokens*updated*
> unix password sync = Yes
> log level = 10
> log file = /var/log/samba/log.%m
> load printers = No
> printcap name = /dev/null
> disable spoolss = Yes
> add user script = /usr/sbin/smbldap-useradd -m "%u"
> delete user script = /usr/sbin/smbldap-userdel "%u"
> add group script = /usr/sbin/smbldap-groupadd -p "%g"
> delete group script = /usr/sbin/smbldap-groupdel "%g"
> add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
> delete user from group script = /usr/sbin/smbldap-groupmod -x "%u"
> "%g"
> set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
> add machine script = /usr/sbin/smbldap-useradd -w "%u"
> logon script = login.cmd
> logon path = \\%N\profiles\%U
> logon drive = H:
> domain logons = Yes
> os level = 127
> wins support = Yes
> ldap admin dn = cn=admin,dc=oranda,dc=internal
> ldap delete dn = Yes
> ldap group suffix = ou=Group
> ldap idmap suffix = ou=Idmap
> ldap machine suffix = ou=Computers
> ldap passwd sync = Yes
> ldap suffix = dc=oranda,dc=internal
> ldap user suffix = ou=People
> panic action = /usr/share/samba/panic-action %d
> admin users = dominic
> hosts allow = 192.168.10., 127.
> hosts deny = ALL
> printing = bsd
> print command = lpr -r -P'%p' %s
> lpq command = lpq -P'%p'
> lprm command = lprm -P'%p' %j
> use client driver = Yes
> 
> This has had me stumped for 3 days straight now and I don't know what else I
> can try. Samba just isn't giving me any more clues.
> 
> I've found lots of other posts like mine through google with no replies to
> them. Does anyone have any ideas of what to do next?
> 
> I would greatly appreciate if someone could point me in

[Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2009-12-27 Thread Dominic Gamble 
Hi,

I can't get access to any shares when running "smbclient //DUCK/test -U
Dominic". I'm getting the message:
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

I'm pretty sure it's authenticating properly as it says "session setup ok"
in the debug output. If I enter the wrong password I get:
"session setup failed: NT_STATUS_LOGON_FAILURE"

I'm running CentOS 5.4 with the following samba packages

samba-common-3.0.33-3.15.el5_4.1
samba-3.0.33-3.15.el5_4.1
samba-swat-3.0.33-3.15.el5_4.1
samba-client-3.0.33-3.15.el5_4.1

My samba setup uses LDAP for authentication. All logging seems to indicate
that authentication and LDAP is working well.

My /etc/samba/smb.conf was generated with SWAT and has the following shares:

[tmp]
comment = temporary files
path = /tmp
hosts allow =
hosts deny =

[test]
comment = test files
path = /test
hosts allow =
hosts deny =


Both shares contain a file called myfile.txt.

When I connect to the "tmp" share, I don't get the "tree connect failed:
NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:

[r...@duck cache]# smbclient //DUCK/tmp -U dominic
Password:
Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
smb: \> ls
  .   D0  Mon Dec 28 04:02:13 2009
  ..  D0  Sun Dec 27 21:16:53 2009

36224 blocks of size 8388608. 34082 blocks available
smb: \>

When I connect to the "test" share I get the "tree connect failed:
NT_STATUS_BAD_NETWORK_NAME":
[r...@duck cache]# smbclient //DUCK/test -U dominic
Password:
Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

The permissions on the /tmp and /test folders are the same:

drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp

There are no complex acls on them either:

[r...@duck /]# getfacl tmp
# file: tmp
# owner: root
# group: root
user::rwx
group::rwx
other::rwx

[r...@duck /]# getfacl test
# file: test
# owner: root
# group: root
user::rwx
group::rwx
other::rwx

I've tried getting more debug info by setting log levels to 10 in both
smb.conf and using the -d10 parameter on the command line, but it gives me
nothing useful in the logs or in the output.

I've been through 'The Samba Checklist'
(http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
and had no other problems.

Here is the rest of my smb.conf:

[global]
workgroup = ORANDA
server string = Duck
passdb backend = ldapsam:ldap://localhost/
pam password change = Yes
passwd program = /usr/sbin/smbldap-passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*all*authentication*tokens*updated*
unix password sync = Yes
log level = 10
log file = /var/log/samba/log.%m
load printers = No
printcap name = /dev/null
disable spoolss = Yes
add user script = /usr/sbin/smbldap-useradd -m "%u"
delete user script = /usr/sbin/smbldap-userdel "%u"
add group script = /usr/sbin/smbldap-groupadd -p "%g"
delete group script = /usr/sbin/smbldap-groupdel "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
delete user from group script = /usr/sbin/smbldap-groupmod -x "%u"
"%g"
set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
add machine script = /usr/sbin/smbldap-useradd -w "%u"
logon script = login.cmd
logon path = \\%N\profiles\%U
logon drive = H:
domain logons = Yes
os level = 127
wins support = Yes
ldap admin dn = cn=admin,dc=oranda,dc=internal
ldap delete dn = Yes
ldap group suffix = ou=Group
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=Computers
ldap passwd sync = Yes
ldap suffix = dc=oranda,dc=internal
ldap user suffix = ou=People
panic action = /usr/share/samba/panic-action %d
admin users = dominic
hosts allow = 192.168.10., 127.
hosts deny = ALL
printing = bsd
print command = lpr -r -P'%p' %s
lpq command = lpq -P'%p'
lprm command = lprm -P'%p' %j
use client driver = Yes

This has had me stumped for 3 days straight now and I don't know what else I
can try. Samba just isn't giving me any more clues.

I've found lots of other posts like mine through google with no replies to
them. Does anyone have any ideas of what to do next?

I would greatly appreciate if someone could point me in the right direction.

Best regards,
Dominic.

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

[Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2007-01-15 Thread Philippe Andries 
Dear all,
 
Since this morning my samba server is acting weird.
I have searched on the web for response on how to resolve this, but could
not find any solution, and only little relevant information.
I need your help.
 
My samba server version is 3.0.9-1.3E.10 running on RedHat ES 3
(2.4.21-47.0.1.ELsmp)
I wanted to add a share to my smb.conf.  Made a copy of it, added the share
and restarted smb.
Since then I can see the share but I cannot access them in both windows and
Linux. (Network name cannot be found or unable to display content)
I went back to the copy of smb (without the new share and which was working,
but no change, it does not work anymore.
 
Here are some test command and their results:
 
[EMAIL PROTECTED] etc]# smbstatus
 
Samba version 3.0.9-1.3E.10
PID Username  Group Machine
---
 2878   administrator  Domain Users  ntmad(10.234.1.1)
 
Service  pid machine   Connected at
---
IPC$  2878   ntmad Mon Jan 15 14:22:24 2007
 
No locked files
 
 
 
[EMAIL PROTECTED] etc]# testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[capital]"
Processing section "[finanzas]"
Loaded services file OK.
'winbind separator = +' might cause problems with group membership.
Server role: ROLE_DOMAIN_MEMBER
Press enter to see a dump of your service definitions
 
# Global parameters
[global]
workgroup = DOMCAWMAD
server string = Madrid Samba Server
security = DOMAIN
log file = /var/log/samba/smbd.log
max log size = 50
printcap name = /etc/printcap
show add printer wizard = No
dns proxy = No
wins server = 10.234.1.1
idmap uid = 15000-2
idmap gid = 15000-2
winbind separator = +
winbind use default domain = Yes
use sendfile = Yes
 
[capital]
comment = Capital shared files
path = /home/capital
read only = No
create mask = 0777
directory mask = 0777
 
[finanzas]
comment = Old Finanzas shared files
path = /home/finanzas
read only = No
create mask = 0777
directory mask = 0777

[EMAIL PROTECTED] etc]# nmblookup madsamba
querying madsamba on 10.234.1.255
10.234.1.3 madsamba<00>

 
[EMAIL PROTECTED] etc]# smbclient -L MADSAMBA -U pandries
Password:
Domain=[DOMCAWMAD] OS=[Unix] Server=[Samba 3.0.9-1.3E.10]
 
Sharename   Type  Comment
-     ---
capital Disk  Capital shared files
finanzasDisk  Old Finanzas shared files
IPC$IPC   IPC Service (Madrid Samba Server)
ADMIN$  IPC   IPC Service (Madrid Samba Server)
Domain=[DOMCAWMAD] OS=[Unix] Server=[Samba 3.0.9-1.3E.10]
 
Server   Comment
----
MADSAMBA Madrid Samba Server
NTMAD
 
WorkgroupMaster
----
DOMCAWMADNTMAD

But this one failed
 
[EMAIL PROTECTED] etc]# smbclient //madsamba/capital -U pandries
Password:
Domain=[DOMCAWMAD] OS=[Unix] Server=[Samba 3.0.9-1.3E.10]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Winbind is working fine webinfo & getent give answers.
 
Thanks in advance for your help,
 
Philippe A
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

RE: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2006-04-05 Thread Robert Mortimer 
 
> Hi,
> 
> I am running samba 2.2.12 on Freebsd 4.3, on an
> internal network, with no firewall.  I have a very
> simple smb.conf.  Here are the relevant entries:
> 
> [global]
>workgroup = Workgroup
>socket options = TCP_NODELAY
>printing = bsd
>guest account = nobody
>hosts allow = 192.168.1.0/24
> 

Where in the section above is the host name for your 
SAMBA machine? Do you have a line like
  
netbios name = HOTSTUFF

If the machine has no name I guess that may be why you
can not find it.



>  [tmp]
>comment = Temporary file space
>browseable = yes
>writeable = yes
>path = /temp
>read only = no
>public = yes
>create mode = 0777
> 
> /temp is owned by nobody, and has read / write
> privileges for everyone.
> 
> My windows machines can see the samba server, but they
> cannot browse to it.
> 
> When I run 
> 
> [EMAIL PROTECTED] smbclient //machinename/
> 
> I get the following output:
> 
> added interface ip=192.168.1.151 bcast=192.168.1.255
> nmask=255.255.255.0
> Password:
> Anonymous login successful
> Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.12]
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> 
> Help appreciated.
> 
> Charlie
> -- 
> 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] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2006-04-05 Thread Charlie McElfresh 
Hi,

I am running samba 2.2.12 on Freebsd 4.3, on an
internal network, with no firewall.  I have a very
simple smb.conf.  Here are the relevant entries:

[global]
   workgroup = Workgroup
   socket options = TCP_NODELAY
   printing = bsd
   guest account = nobody
   hosts allow = 192.168.1.0/24

 [tmp]
   comment = Temporary file space
   browseable = yes
   writeable = yes
   path = /temp
   read only = no
   public = yes
   create mode = 0777

/temp is owned by nobody, and has read / write
privileges for everyone.

My windows machines can see the samba server, but they
cannot browse to it.

When I run 

[EMAIL PROTECTED] smbclient //machinename/

I get the following output:

added interface ip=192.168.1.151 bcast=192.168.1.255
nmask=255.255.255.0
Password:
Anonymous login successful
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.12]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Help appreciated.

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

Re: fwd: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2005-07-09 Thread Mike Soh 
Thanks steve for the reply.

FC4 has SELinux that locks down home directories.  The solution is on
LinuxQuestions:
 http://tinyurl.com/8agtd

Summary:
 [root]# setsebool -P samba_enable_home_dirs=1

 or add "samba_enable_home_dirs=1" to your
 /etc/selinux/targeted/booleans.local file


Steve Williams <[EMAIL PROTECTED]> wrote on Sat, Jul 09, 2005 at 12:43:07AM EDT:

> Hi,
> 
> I got this about 15 minutes ago when setting up a new server... I forgot 
> to create the directory for the share.  Weird error message, but I 
> created the directory & the problem went away.
> 
> Not sure if that helps
> 
> Cheers,
> Steve
> 
> Mike Soh wrote:
> 
> >I sent this out yesterday.  Can anyone offer any advice?  I'm really at a
> >loss on what to do.
> >
> >thanks!
> >
> >
> >- Forwarded message from Mike Soh <[EMAIL PROTECTED]> -
> >
> >From: Mike Soh <[EMAIL PROTECTED]>
> >To: samba@lists.samba.org
> >Subject: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> >Date: Thu, 7 Jul 2005 08:27:33 -0400
> >User-Agent: Mutt/1.4.1i
> >X-Spam-Status: No, score=-2.6 required=3.8 tests=BAYES_00 autolearn=ham 
> > version=3.0.2
> >
> >Hello everyone!
> >
> >I've searched the archives and seen this problem crop up a couple of 
> >different
> >times.  None of the solutions I've found seemed to have worked.
> >
> >Here's the synopsis:
> >I've recently installed FC4 and samba shares for home directories should 
> >work
> >right out of the box.  Default settings, etc...
> >
> >I get this error:
> >
> >[EMAIL PROTECTED]:~$ smbclient //127.0.0.1/sohmc
> >added interface ip=192.168.1.201 bcast=192.168.1.255 nmask=255.255.255.0
> >Client started (version 3.0.14a-2).
> >Connecting to 127.0.0.1 at port 445
> >Password: 
> >Doing spnego session setup (blob length=58)
> >got OID=1 3 6 1 4 1 311 2 2 10
> >got principal=NONE
> >Got challenge flags:
> >Got NTLMSSP neg_flags=0x608a0215
> >NTLMSSP: Set final flags:
> >Got NTLMSSP neg_flags=0x60080215
> >NTLMSSP Sign/Seal - Initialising with flags:
> >Got NTLMSSP neg_flags=0x60080215
> >Domain=[BART] OS=[Unix] Server=[Samba 3.0.14a-2]
> >tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> >
> >
> >I've checked permissions, and even made everything world readable, still
> >doesn't work.
> >
> >It gets weirder.  I've shared my tmp directory using the provided smb.conf:
> >
> ># This one is useful for people to share files
> >[tmp]
> >  comment = Temporary file space
> >  path = /tmp
> >  read only = no
> >  public = yes
> >
> >I can access this share just fine.  However, I ran some permissions test to
> >see if I could isolate the problem.  When I use samba to put a file into
> >temp, the file is copied correctly.  BUT when I create a file outside of
> >smbclient (e.g. vim) and save it into tmp, samba cannot see it.  It says
> >permission denied.
> >
> >I know what you're thinking...permissions are wrong.  After copying the 
> >file
> >using samba, I tried copying it again in the shell with another filename.
> >Keeping in mind that I copied with permissions and everything.  Still the 
> >same
> >problem.
> >
> >I get the feeling that I'm missing something really big here.  I've never
> >experienced this problem with FC2 or FC3.  I don't think architecturally 
> >there
> >is anything different between FC2/3 and FC4.  I could be mistaken though.
> >
> >Anyone have any other suggestions I could try?
> >
> >let me know!  thanks!
> >
> > 
> >

-- 

Mike Soh
[EMAIL PROTECTED]
http://twentyfifteen.tripod.com

"Courage is not simply one of the virtues, but the form of every virtue at the
testing point."
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

fwd: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2005-07-08 Thread Mike Soh 
I sent this out yesterday.  Can anyone offer any advice?  I'm really at a
loss on what to do.

thanks!


- Forwarded message from Mike Soh <[EMAIL PROTECTED]> -

From: Mike Soh <[EMAIL PROTECTED]>
To: samba@lists.samba.org
Subject: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Date: Thu, 7 Jul 2005 08:27:33 -0400
User-Agent: Mutt/1.4.1i
X-Spam-Status: No, score=-2.6 required=3.8 tests=BAYES_00 autolearn=ham 
version=3.0.2

Hello everyone!

I've searched the archives and seen this problem crop up a couple of different
times.  None of the solutions I've found seemed to have worked.

Here's the synopsis:
I've recently installed FC4 and samba shares for home directories should work
right out of the box.  Default settings, etc...

I get this error:

[EMAIL PROTECTED]:~$ smbclient //127.0.0.1/sohmc
added interface ip=192.168.1.201 bcast=192.168.1.255 nmask=255.255.255.0
Client started (version 3.0.14a-2).
Connecting to 127.0.0.1 at port 445
Password: 
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x608a0215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
Domain=[BART] OS=[Unix] Server=[Samba 3.0.14a-2]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME


I've checked permissions, and even made everything world readable, still
doesn't work.

It gets weirder.  I've shared my tmp directory using the provided smb.conf:

# This one is useful for people to share files
[tmp]
   comment = Temporary file space
   path = /tmp
   read only = no
   public = yes

I can access this share just fine.  However, I ran some permissions test to
see if I could isolate the problem.  When I use samba to put a file into
temp, the file is copied correctly.  BUT when I create a file outside of
smbclient (e.g. vim) and save it into tmp, samba cannot see it.  It says
permission denied.

I know what you're thinking...permissions are wrong.  After copying the file
using samba, I tried copying it again in the shell with another filename.
Keeping in mind that I copied with permissions and everything.  Still the same
problem.

I get the feeling that I'm missing something really big here.  I've never
experienced this problem with FC2 or FC3.  I don't think architecturally there
is anything different between FC2/3 and FC4.  I could be mistaken though.

Anyone have any other suggestions I could try?

let me know!  thanks!

-- 

Mike Soh
[EMAIL PROTECTED]
http://twentyfifteen.tripod.com

"Courage is not simply one of the virtues, but the form of every virtue at the
testing point."
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

- End forwarded message -

-- 

Mike Soh
[EMAIL PROTECTED]
http://twentyfifteen.tripod.com

"Courage is not simply one of the virtues, but the form of every virtue at the
testing point."
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

2005-07-07 Thread Mike Soh 
Hello everyone!

I've searched the archives and seen this problem crop up a couple of different
times.  None of the solutions I've found seemed to have worked.

Here's the synopsis:
I've recently installed FC4 and samba shares for home directories should work
right out of the box.  Default settings, etc...

I get this error:

[EMAIL PROTECTED]:~$ smbclient //127.0.0.1/sohmc
added interface ip=192.168.1.201 bcast=192.168.1.255 nmask=255.255.255.0
Client started (version 3.0.14a-2).
Connecting to 127.0.0.1 at port 445
Password: 
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x608a0215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
Domain=[BART] OS=[Unix] Server=[Samba 3.0.14a-2]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME


I've checked permissions, and even made everything world readable, still
doesn't work.

It gets weirder.  I've shared my tmp directory using the provided smb.conf:

# This one is useful for people to share files
[tmp]
   comment = Temporary file space
   path = /tmp
   read only = no
   public = yes

I can access this share just fine.  However, I ran some permissions test to
see if I could isolate the problem.  When I use samba to put a file into
temp, the file is copied correctly.  BUT when I create a file outside of
smbclient (e.g. vim) and save it into tmp, samba cannot see it.  It says
permission denied.

I know what you're thinking...permissions are wrong.  After copying the file
using samba, I tried copying it again in the shell with another filename.
Keeping in mind that I copied with permissions and everything.  Still the same
problem.

I get the feeling that I'm missing something really big here.  I've never
experienced this problem with FC2 or FC3.  I don't think architecturally there
is anything different between FC2/3 and FC4.  I could be mistaken though.

Anyone have any other suggestions I could try?

let me know!  thanks!

-- 

Mike Soh
[EMAIL PROTECTED]
http://twentyfifteen.tripod.com

"Courage is not simply one of the virtues, but the form of every virtue at the
testing point."
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba