[mythtv-users] [OT] CIFS/Samba problem in FC5

[Paul Bender]

jack snodgrass wrote:

> On 9/8/06, Paul Bender <pebender at san.rr.com> wrote:
> 
>>Phill Edwards wrote:
>>
>>>I've been moving my MythTV box from FC3 to FC5 with a clean disk
>>>install. I'm using Jarod's new FC5 guide which is excellent as usual.
>>>However, I've run into a problem mounting samba shares. All my music,
>>>photos etc live on another box which provides samba shares. It seems
>>>that FC5 has deprecated the smb file system so you can only mount
>>>these shares with the cifs filesystem. Unfortunately the version of
>>>samba that ships with FC5 has a bug which prevents you doing anything
>>>with the files - you can see them in a dir listing but can't cat them,
>>>open them or anything. BTW - it's not me saying there's a bug, I found
>>>this on a search.
>>>
>>>So, does anyone know if there's anything I can do at the non-MythTV
>>>end to make it share the files as cifs instead of samba? Or any other
>>>workarounds?
>>
>>The problem is with samba 3.0.23a, which is an update to the samba
>>3.0.21b that shipped with FC5. Therefore, you could get an earlier
>>version of the samba packages and install those instead of the updated
>>packages. If you cannot find anything newer, then you can always
>>download the original packages for FC5 from
> 
> I'm using:
> yum list | grep -i samba
> samba.x86_64                             3.0.23a-1.fc5.1        installed
> samba-client.x86_64                      3.0.23a-1.fc5.1        installed
> samba-common.x86_64                      3.0.23a-1.fc5.1        installed
> without any problems.

The problem requires a specific combination in order to occur. It occurs 
when connecting the Samba CIFS client to a Samba 3.0.23a server. The 
ironic thing is that the problem was introduced in a patch release that 
was designed to fix authentication problems with Windows, but it 
introduced this authentication related problem.

The problem has been acknowledged by the Samba developers and fixed in 
Samba 3.0.23b. However, the Fedora Project has not packaged an update yet.

When I encountered it, the previous FC4 packages for Samba 3.0.23 were 
still available for download, so I downloaded and installed them. After 
that, the problem went away. Unfortunately, the Samba 3.0.23 no longer 
appear in the Fedora Core updates directories.