Installing winbind makes samba shares inaccessible on the machine that the winbind is installed in.

Bug #111100 reported by sefs
2
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: winbind

Desktop is Feisty 7.04

I have Samba and winbind installed. I installed winbind so I don't have to remember IP's and can refer to machines on the network by their names.

The problem is when winbind is running ... the shares on the machine on which winbind is installed are not accessible. I get a "cannot display the contents of this folder" error message.

If I stop the winbind service, then everything is ok, but as soon as it is started back then the shares become inaccessible.

Revision history for this message
sefs (sefsinc) wrote :

It seems that there is a conflict between winbind and avahi-deamon running at the same time. If both are running at the same time, then samba shares are inaccessible.

Revision history for this message
Mathias Gug (mathiaz) wrote :

Is this still an issue with 8.04 ?

Changed in samba:
status: New → Incomplete
Revision history for this message
sefs (sefsinc) wrote :

I think avahi has superceded winbind so there is not reason to use winbind as far as i can see. Uninstalling winbind sorts solves the problem.

Revision history for this message
Mathias Gug (mathiaz) wrote :

Marking as invalid. winbind is not related to hostname resolution.

Changed in samba:
status: Incomplete → Invalid
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.