similar to: smbfs / cifs mount error - "password too long"

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

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 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

Package: xcp-xapi Severity: important Version: 1.3.2-5 Tags: patch User: ubuntu-devel at lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch quantal Hello, the "smbfs" package has been deprecated for years, and finally removed last week: cifs-utils (2:5.4-1) unstable; urgency=low * New upstream release (Closes: #669327). - Version build dep on libwbclient-dev for

Hello While the mounting process is successful, the behavior of remote directories and files is different under CIFS than SMBFS. Here are some of the issues I have encountered: 1) When doing a "file" on a file mounted under SMBFS, it gives a standard output depending on the file type. For the same file under CIFS, it gives the same information with "setgid sticky" before

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

Hello - I just installed Fedora Core 2 the other day and have been trying to mount a share to some XP shares (domain members) without any luck. If I use the following line it works fine: mount -t smbfs -o username="mkipness",password=xxxx,domain=domain //10.0.100.74/c$ /mnt/max-laptop But if I use the the same statement substituting cifs, it doesn't: mount -t cifs -o

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

Greetings, I am working on getting mount.cifs version: 1.11-3.2.4 on debian to mount a share on a samba server Version 3.0.13-1.1-SUSE on SuSe. This was working on older debian systems, but upon upgrading some of the systems to Lenny I am now having trouble mounting shares. Again, this was working and I have smbfs installed on the systems (which is what I used before). The samba server is set

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 all, I'm just wondering why smbmount allows the same mount point to mount several times the same share while a normal mount operation (with a non-smbfs) returns a busy mount point error. [luca@fluca:~]$ mount ... //server/sys on /mnt/target type smbfs (rw) [luca@fluca:~]$ smbmount //server/sys /mnt/target/ -o ip=192.168.4.1,guest [luca@fluca:~]$ mount ... //server/sys on /mnt/target type

Hi - [problem] mount.smbfs is not working on 3.0.0beta3; it has been working thru 3.0.0beta2. When I re-install 3.0.0beta2, it works again. [configuration] *Linux host <hanako> Linux version 2.4.20-4GB-athlon (root@Athlon.suse.de) (SuSE Linux 8.2)) #1 Fri Jul 11 20:16:51 UTC 2003 *samba-3.0.0beta3 complied from source, with configuration option '--with-smbmount'. (same

Hi, I'm trying to mount a Windows folder from a Linux box with the command: # mount -t smbfs (...) but I get the error: "mount: unknown filesystem type 'smbfs'". Does this mean that CentOS mount doesn't support smbfs type ? If so, how can I enable it ? I'm using 5.1 Any help would be appreciated. Warm Regards, M?rio Gamito

Hello, context: Samba-3.0.2 on a i386 debian-sarge linux, 2.4 kernel. All the windows machine on our network switched today to NTLMv2, and mount.smbfs can't access anymore ressources which are available to smbclient. Exerpt from smb.conf: client NTLMv2 auth = Yes client lanman auth = No client plaintext auth = No The rest being default. Doing smbclient -L server

Hi - My messages may not be reaching this list. Would someone at least confirm receipt of this message even if you have no suggestions/ comments re its content? I have sent several messages concerning mount.smbfs and I guess no one is using smbfs to mount a Windows machine -or- no one has encountered my problem. To recap the problem and give a solution: [problem] mount.smbfs is not working on

Hi; Unable to mount NetApp volume via smbfs on CentOS 6.6 I have been able to mount the NetApp via smbfs from a Mac but cannot from CentOS 6.6 What I have in /etc/auto_smb on the Mac is: /Volumes/build_dir -fstype=smbfs ://domain_name;account_name:password at machine_name/partition_name What is the equivalent on CentOS 6.6? I would be modifying /etc/fstab? I don't see any examples (yet)

Hi, I am getting an I/O error while running fsstress on client samba mount point (only with smbfs) Can anyone, please look into this problem? Problem Description: x370 was configured for samba server & x206f as samba client. fsstress was running from two samba mount points from client i.e /SAMBA1 (type cifs) & /SAMBA2 (type smbfs). There was no load generating on /SAMBA2 & hence

This problem began a couple months ago with my new install of (you guessed it) XP sp2. Now, when i mount a share from the xp machine to my debian box, everyone, including rot, gets a permission denied trying to ls the dir. I've read posts about switching to cifs, but that has opened a whole new can of worms. I'd just like to see smbfs mount my shares properly the way they used to. My

I have a problem with smbmount. I have a linux server running E-Smith (or Mitel SME server as it is now) which is basically a cut down version of RedHat 7.0 (running Kernel 2.2.19-7.0.8smp). Samba version is 2.0.10. We are connecting to an NT server (service pack 3 - I must upgrade that sometime soon). We have quite a good tapedrive and backup software (3rd party) on the E-Smith server, whereas

Hello, I've got a FreeBSD 5.5 box running Samba 3.0.21 and every-time I try to do a "mount -t smbfs -o username=username,password=password // server/share /mnt/folder" I get the error "smbfs: -o username=: option not supported". I've google'd this with no luck... any help in the right direction is appreciated. --- Jason Zondor