similar to: Cifs client

I periodically see smbfs questions get asked on this list, and they usually get one of two responses: 1. smbfs is a kernel module; this list is not the appropriate place to be asking smbfs questions. 2. You should be using cifs instead. (Please let me know if either if these is incorrect.) I was surprised to see, however, that the smbmount / mount.smbfs manpage makes no mention of cifs as being

I am somewhat confused... I understand that the preferred method to mount a Samba share with a Linux client is to use "mount -t cifs" rather than "mount -t smbfs". I get the impression that smbfs is samba.org developed code where as cifs is from elsewhere. Thus the point of confusion. Why is samba.org not developing the preferred code in this case? A sub question to that

I'm using Fedora Core 6 which uses cifs.mount version 1.10. When mounting shares from a particular Windows 2003 R2 server, I cannot read certain directories. For example, when performing an 'ls' command as follows: [root@backup Admin]# ls /share/CORP-SERVER/C\$/Corp/User\ Files/xxx\ Finacial\ Shared/Admin/Freddie\ Mac/ ls: reading directory /share/CORP-SERVER/C$/Corp/User Files/xxx

Hi I need to mount a windows share on a CentOS 4.5 box running stock kernel etc - I have tried using cifs and also smbfs My fstab looks like //share/name /mount/point smbfs username=user,password=password,uid=useridhere 0 0 or the same using cifs When i try and mount that i get the following errors depending on the share type smbfs: mount_data version 1919251317 is not supported CIFS

Hello, I have the following Samba RPMs installed... samba-client-3.0.26a-0.5 samba-3.0.26a-0.5 samba-pdb-3.0.26a-0.5 yast2-samba-server-2.9.33-0.3 kdebase3-samba-3.2.1-68.62 samba-winbind-3.0.26a-0.5 yast2-samba-client-2.9.18-0.3 samba-python-3.0.26a-0.5 I used to be able to do a mount with -t smbfs, but not I get this message whenever I try it. Version

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Suse Linux 10.1 X86_64 server that is destined to work with a mixed bag of OS/2, Windows and Linux clients. For this reason, I have again chosen to use the SMB protocol, which mandates the use of samba. I started with samba 3.0.22, but ran into some glitches so migrated to 3.0.23rc3. My Linux client is running Suse 10.1 X86_32 with samba

My LAN includes a server machine running FC4, with several shares mounted with Samba. Yesterday, I upgraded the packages on the FC4 machine, and these included Samba, which is now at 3.0.23a. Unfortunately, this seems to have broken the mounted shares for my Ubuntu 6.06 installation on my Acer 1682WLMI laptop. The cifs module on Ubuntu reports as version 1.39. The symptoms are that I can

Hi Guys! Anyone know how can I do this trick? I guess there is a registry value for it. As I noticed winxp try to use smbfs first not cifs. In linux it's easier because you can choose when you mount your shares. Regards, Jax

Hi Samba team, I feel user will feel more confortable when they can mount folder (via mount.cifs or mount.smbfs) under particular shared folder. Example: I have a share folder call department, all department's folder arrange inside so I have a share folder call \\server\department if I have a linux client under purchasing, I 2 command to get the correct place, and I feel it is giving more

I am attempting to troubleshoot a rather perplexing problem. Whenever I attempt to transfer a non-trivial amount of amount to a share mounted via the new CIFS kernel mod, my system will experience a hard lock requiring reboot. The setup linux client, running 2.6.3 (gentoo-dev-sources) with the preemptible kernel option enabled. Samba version as reported by smdb --version is 3.0.1. Using

I recently discovered the 2GB file limitation using the smbfs filesystem and switched to the CIFS filesystem for my Samba mount. Since the switch I have not been able to get the permissions right for the mount. Specifically I am using the following commands in /etc/auto.mnt to mount the remote share using automount home2/ -fstype=cifs,uid=500,gid=100,credentials=/home/user/

After trying a couple of Linux forums & no help I'm hoping that somebody on the samba list knows how to solve this issue. I'm having a problem with CIFS. This is a fresh installation of Fedora Core 5. I have 3 XP machines that I mount by CIFS in my fstab. CIFS mounts the shares with no problem. I can view and read files on the shares. The problem I have is when I try to copy a file

I have a Samba 3.0.23a-1.fc5.1 configured on a Fedora 5 server. It's joined to an Active Directory 2003 domain controller using Winbind, etc. I'm able to connect from various workstations using active directory user accounts/credentials just fine to shares on this server, permissions work, and all is well. I'm guessing this is set up correctly. However, from another Fedora 5 server,

hello everyone, the old problem persists :X I'm currently running Novell Linux Desktop 9 (SP2) featuring a 2.6.5series kernel. Smbclient (3.0.14a-0.4-SUSE) seems to support signing negotiation.. at least the following command works just fine: smbclient -k -L //hostname turning signing off manually (-S off) ends up in the common error message cli_negprot: SMB signing is mandatory and we have

After mounting a windows share via cifs I have came across the same issue as described here: http://lists.samba.org/archive/samba/2006-April/119813.html "While using vim on files mounted under CIFS, when trying to write an existing file you will randomly be warned "The file has been changed since reading it!!!". Normally, this only occurs when another user accesses and saves the

First: this is my first post on this list so any suggestions, let me know. I recently had to make the move from SMBFS to CIFS when I upgraded from Fedora 4 to 5. Changing settings in my /etc/fstab was easy and no errors come up but now I'm having an issue very similar to post I found on your list that got no response back in April: http://lists.samba.org/archive/samba/2006-April/119813.html

I've seen a number of posts discussing NFS based storage and issues with Dovecot. When the term "NFS" is used - does this exclusively refer to the Linux NFS network file system, or is it a generic reference to any network file system? I don't recall seeing any posts referencing issues with CIFS or SMBFS - is this because no one is using it, or because it just works instead

Hi all; When I access the data hosted in that share using others mount ways (except the smbmount/mount.cifs/mount -t smbfs/mount -t cifs) all works fine, downhere a benchmark: 1) Transfer a 500 mb file: netcat - 27 seconds ftp - 31 seconds smbclient - 38 seconds mounted (cifs) - 2:58 minutes I'm having a big problem with delay mounting a share using smbmount or mount -t cifs. First

Hi, i'm probably not the first but i have found no concrete information about my problem... lots of information, nothing helped.. :S so, here's the thing.. i'm running a samba-3.0.22-13.16 server on SLES 9 kernel 2.6.16.21-0.8-default as an nt domain controller, there was a migration to Linux for the workstations so i had to implement WINBIND + PAM_MOUNT. after searching for the

Hello, Can someone tell me what the problem is here. I am doing an rsync on a sendmail spool directory to a folder that is a samba mount. Why is rsync trying to change owner? Does it have to? I tried manually changing owner (as root) on a file that is sitting on the samba mount and I got the same operation not permitted error. Does anybody know why this is? Or do I need to ask in a samba