Bug 3950 - Can't access shares after upgrading to 3.023
Summary: Can't access shares after upgrading to 3.023
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: winbind (show other bugs)
Version: 3.0.23a
Hardware: x86 Linux
: P3 major
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-20 17:27 UTC by Richard Santiago
Modified: 2006-08-08 10:44 UTC (History)
1 user (show)

See Also:

Attachments
Requested smb.conf file (28.00 KB, application/msword)
2006-08-03 07:05 UTC, Richard Santiago 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Santiago 2006-07-20 17:27:02 UTC 
After upgraded Samba from version 3.021c to 3.023 I can't access my shares, just my home directory.

Now, the group name for the share is DOMAIN/share and, if I'm not mistaken, it was just share.
Comment 1 Richard Santiago 2006-07-26 09:44:53 UTC 
I tried fixing the problem upgrading to version 3.023a after reading the release notes but still have problemas.

Any hints on how to fix this issue?

Thanks.
Comment 2 Richard Santiago 2006-07-31 07:45:15 UTC 
Today I've upgraded to new version 3.023a through RPM for Fedora Core 4 and everything looks normal but still can't access my shares.

Please take a look at my smb.conf to see if I have to add some new commands.

Thanks.
Comment 3 Jeremy Allison 2006-08-02 19:11:44 UTC 
Please post your smb.conf for me to examine, and tell me what share you can't access.
Jeremy.
Comment 4 Richard Santiago 2006-08-03 07:05:50 UTC 
Created attachment 2080 [details]
Requested smb.conf file

Here is the smb.conf file.  

I can't access the "redes" share.  "redes" is a group name on the AD and I'm a member of this share.  This is happening to all users who were accessing the other shares (dti, adminosi, etc.) too.

Thanx.
Comment 5 Gerald (Jerry) Carter (dead mail address) 2006-08-08 10:44:12 UTC 
I expect this is fixed in 3.0.23b.  Please read the 
release notes.