Jaunty: Samba permission problems

Bug #374447 reported by Carroarmato0
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba4 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: samba4

When enabling a share for the first time it works.
But after a reboot it's as if the share disappear.

Issuing the command as a normal user: smbstatus

I get this output:
***********************************************************
christophe@lithium-flower:~$ smbstatus
ERROR: Failed to initialise messages database:Acces denied
messaging_tdb_init failed: NT_STATUS_ACCESS_DENIED
messaging_init failed
************************************************************

But running the command as root I get:

**************************************************
christophe@lithium-flower:~$ sudo smbstatus
Samba version 3.3.2
PID Username Group Machine
-------------------------------------------------------------------

Service pid machine Connected at
-------------------------------------------------------

No locked files
***************************************************

When looking at the shares on an XP machine, I can see the shares, but I cannot access them because they are either non-existent or I don't have the required permissions to access them.

Note: this worked fine in the previous release of Ubuntu.

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

I have created a share called "Pubblici"

The share appears when roaming through the network on my laptop.

Through the gui, the folder should be visible to the network (shareable), people are able to write to that folder, and external people also have access to that share.

When issuing the command 'ls -ls' it returnes these results:
---------------------------------------------------------------------------------------------------
 4 drwxrwxrwx 2 christophe christophe 4096 2009-05-09 12:25 Pubblici
---------------------------------------------------------------------------------------------------

This appears to be correct.

But trying to access this directory, this shows up in the logs:

----------------------------------------------------------------------------------------------------------
[2009/05/11 16:49:18, 0] smbd/service.c:make_connection_snum(1073)
  '/home/christophe/Pubblici' does not exist or permission denied when connecting to [pubblici] Error was Permission denied
-----------------------------------------------------------------------------------------------------------

smbstatus only shows this:

-----------------------------------------------------------------------------------------------------------
Samba version 3.3.2
PID Username Group Machine
-------------------------------------------------------------------

Service pid machine Connected at
-------------------------------------------------------
IPC$ 6464 lithium-flower Mon May 11 16:43:52 2009

No locked files
-----------------------------------------------------------------------------------------------------------

Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-client.

Changed in samba4 (Ubuntu):
status: New → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

I have upgraded to Karmic and I don't have this issue anymore.
I believe this report may be closed.

Revision history for this message
Chuck Short (zulcss) wrote :

Thanks, closing it then.

Regards
chuck

Changed in samba4 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.