Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235890 - 3.0.24-4 breaks network share access
Summary: 3.0.24-4 breaks network share access
Status: CLOSED DUPLICATE of bug 235821
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 5
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Samba Maint Team
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-10 17:25 UTC by Calvin Dodge
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-10 17:42:27 UTC

Attachments (Terms of Use)

Description Calvin Dodge 2007-04-10 17:25:17 UTC
Description of problem: After Samba was upgraded this morning (4/10/2007), the
Windows computers (primarily XP SP2) could not access most network shares
(common or home)

Version-Release number of selected component (if applicable): 3.0.24-4

How reproducible: Unknown - have only one system running Core 5, and can't waste
customer's time monkeying with reinstalls. Downgrading to 3.0.24-3 fixed the

Steps to Reproduce:
1. Update to 3.0.24-4
2. Try accessing network shares
Actual results: can't reach network shares

Expected results: should be able to reach network shares

Additional info: Strangely, 1 folder in 1 share _could_ be accessed, but files
inside folder not visible. Folder ownership and permissions are identical to
other folders in share. Selinux is disabled (and has been for some time due to
conflict with Samba), so is assumed to not be the problem.

Other updates this morning were popt, libattr and libacl

Comment 1 Simo Sorce 2007-04-10 17:42:27 UTC
Sorry but this is a known issue. We had to change a bad default set upstream in
The easy fix is to just restart your windows client.
Otherwise if you can't restart the clients you can set root msfds = yes in
smb.conf and restart samba.
But this may have other subtle consequences that's why we changed the default
back to root msdfs = no

*** This bug has been marked as a duplicate of 235821 ***

Note You need to log in before you can comment on or make changes to this bug.