[Samba] Suse 10.1 with samba servers 3.0.22 & 3.0.23rc3 only seen by Suse 10.1 samba client as cifs

Jeremy Allison jra at samba.org
Wed Jul 5 16:16:39 GMT 2006

On Tue, Jul 04, 2006 at 10:27:15PM -0700, Thomas Garson wrote:
> 4) The new Linux samba client fails to recognize file system of the
> shares as SMB, even though the shares can be mounted. But, if I mount
> them as cifs instead of smbfs they are usable.
> Questions:
> Has there been some kind of hidden parameter relatively recently added
> to samba 3 that identifies shares as cifs or smbfs? Is the Linux client
> programmed to react to this? Are these protocols becoming mutually
> exclusive? If any of this is true, where is the documentation? Why me?
> This has given me a headache!

Sorry for the headache. You really shouldn't use smbfs anymore. It's
essentially unsupported. You got bitten by Microsoft marketing, there's
no difference between smb and cifs. Cifs is just a renaming (re-branding?)
of smb. They're the same thing. Just always use cifsfs on linux.


More information about the samba mailing list