** Attachment added: smb.conf
http://launchpadlibrarian.net/25788807/smb.conf
--
[samba] tree connect failed
https://bugs.launchpad.net/bugs/363083
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
rem...@nkbp:~$ groups rems14
rems14 adm dialout cdrom audio video plugdev scanner lpadmin netdev admin
sambashare
Thanks
--
[samba] tree connect failed
https://bugs.launchpad.net/bugs/363083
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hi, my share public is in my home directory : /home/rems14/Public.
rem...@nkbp:~$ dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' |
grep samba
libsmbclient 2:3.2.3-1ubuntu3.4 samba install ok installed
libwbclient0 2:3.2.3-1ubuntu3.4 samba install ok installed
samba 2:3.2.3
Thanks
** Attachment added: public
http://launchpadlibrarian.net/25816223/public
--
[samba] tree connect failed
https://bugs.launchpad.net/bugs/363083
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
I set loglevel = 4 in the smb.conf file.
In the attached file, there is the log of this command :
rem...@nkbp:~$ smbclient //nkbp/public
Enter rems14's password:
Anonymous login successful
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.2.3]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Thanks
Sorry for multiposts !!!
I've tested to share in subdirectory but no change.
--
[samba] tree connect failed
https://bugs.launchpad.net/bugs/363083
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
Hi,
This is the command you request me :
rem...@nkbp:~$ testparm -v -s | grep usershare
Load smb config files from /etc/samba/smb.conf
Processing section [printers]
Processing section [print$]
Loaded services file OK.
Server role: ROLE_STANDALONE
usershare allow guests = Yes
Hi !
I solved my problem by changing my home folder permissions :
Before :
rem...@nkbp:~$ ls -l /home/
drwxr--r-- 99 rems14 rems14 12288 2009-04-24 19:50 rems14
Now :
rem...@nkbp:~$ ls -l /home/
drwxr-xr-x 99 rems14 rems14 12288 2009-04-24 19:50 rems14
The soluce is to allow execute for all
